Install of 8-3-RELEASE renders hard drive unusable

Code: 
root@maxwell:/root # gpart show ada0
=>       63  976773105  ada0  MBR  (465G)
         63   42154497     1  freebsd  [active]  (20G)
   42154560  398669040     2  freebsd  (190G)
  440823600   84084210     3  freebsd  (40G)
  524907810  451860255     4  ebr  (215G)
  976768065       5103        - free -  (2.5M)

root@maxwell:/root # uname -a
FreeBSD maxwell 9.1-RELEASE FreeBSD 
9.1-RELEASE #0: Tue Jan  8 16:39:24 EST 2013
root@maxwell.system1.com:/usr/src/sys/amd64/compile/GENERIC  amd64
root@maxwell:/root

I did uname to show the end but what is my machine name doing in GENERIC? The last thing I did was the gpart show ada0s1a yesterday. I never notice nothing like this before, but I never had a reason to pay attention either.

Anyway, the way technology has been advancing, I'm betting on an 250-500GB Flash Drive to come about by next year or sooner so I can put this hard drive on. I meant no harm. I just have no need to break the 2TB barrier that GPT offers. That's all it's all about other than I think gpt might have some flaws, but what do I know. Once I learn how to, I just want my backup server, jails galore, FreeBSD Desktop, Virtualbox, and a little bit of homework all on one key chain.

You were asked to provide the output of:

# gpart show ada0.
Click to expand...

#gpart show ada0

Well, that's all she wrote. It don't look like much to me. White spaces and everything included.
 
Wait--so FreeBSD 9.1 worked fine until you built a custom kernel which had not been updated? That sounds like a self-inflicted problem.
Click to expand...

wblock, just because google read LINUX, I was wondering if "relatime" (relaxed atime) would work, if not, back to single-user. I just got the vfs error again! Now I realize I have (habit) three versions of FreeBSD on one hard. Most users never play with fstabs, but I usually get previous made fstab and paste it after an new install, so more than likely that's what I did. According to the link I posted, the reason why it's so hard to debug is because the debugger never got mounted. can't find SOLVE! button.

... That sounds like a self-inflicted problem.
Click to expand...
I hear you, but I don't think I'm the only one who replace fstab before upgrading the kernel :)

Thanks wblock
 
"Solved" can be set by editing the first message in Advanced mode. OP claimed that their problem was solved, but never bothered to share that particular solution.
 
You must log in or register to reply here.
Back
Top