Re: 4.7-STABLE upgrade boot failure. - Semi-solved.
>
> No, I just meant that I copied MAKEDEV from /usr/src into /dev, and
> then ran ./MAKEDEV std from /dev, as per the UPDATING instructions.
hmm, does UPDATING say you should do that? all I know is
>>mergemaster
asks whether I want to have /dev/* rebuilt, and I let it do so.
UPDATING notwithstanding, you did *not* rebuild ad{4,5}*. take a
look in /dev/MAKEDEV: calling it with "std" does not touch ad* at
all. what you want is:
cd /dev && ./MAKEDEV all ad4 ad5
yeah, this updated my ad* entries just fine, which was actually the
conclusion i'd come to a little while ago, i just didn't know how to do
>it.
Silly me thinking that "all" == everything.
all of this aside, the base problem remains. Even with the updated >ad*
entries sitting in /dev, I still get a root mount failed error message >on
boot with no way I can see to load the 4.7 kernel.
Okay, just to update.. after much searching and reading, I discovered that
the way FreeBSD past a certain point is *supposed* to handle RAID hardware
arrays is to designate them as arX, and then you can use atacontrol to
attach/detach/whatever.
So basically, when I updated to 4.7-STABLE from 4.5-RC1, I was changing
the way it was looking at my current mirror setup. It now wanted to see the
array as ar0, except it wouldn't boot off of ar0s1a or anything.
I broke the mirror and promptly tried to boot with ad4 and ad5 being
individual drives instead of a mirror, and suddenly /dev/ad4s1a would boot
just fine.
Why it recognized the HPT370 as ar0 on 4.5 and worked fine while booting a
hardware mirrored drive from /dev/ad4s1a, and would not do the same under
4.7, I couldn't tell you.
So now my question is, how can I recreate the mirror? I don't want to take
down my whole system and resynch those two drives only to have it fail to
boot again. Should I just do it in software?
Anyways, thanks for all the helpful suggestions.
Aaron Lewis.
_
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
From: Roman Neuhauser <[EMAIL PROTECTED]>
> >
> >did you let mergemaster run MAKEDEV for you, or did you run
> >
> >/dev/MAKEDEV std
> >
> >while being in /usr/src? If the latter, you didn't rebuild the
> >devices in /dev/, you created them in /usr/src instead! That would
> >indeed explain your problems.
>
> No, I just meant that I copied MAKEDEV from /usr/src into /dev, and
> then ran ./MAKEDEV std from /dev, as per the UPDATING instructions.
hmm, does UPDATING say you should do that? all I know is >mergemaster
asks whether I want to have /dev/* rebuilt, and I let it do so.
UPDATING notwithstanding, you did *not* rebuild ad{4,5}*. take a
look in /dev/MAKEDEV: calling it with "std" does not touch ad* at
all. what you want is:
cd /dev && ./MAKEDEV all ad4 ad5
yeah, this updated my ad* entries just fine, which was actually the
conclusion i'd come to a little while ago, i just didn't know how to do it.
Silly me thinking that "all" == everything.
all of this aside, the base problem remains. Even with the updated ad*
entries sitting in /dev, I still get a root mount failed error message on
boot with no way I can see to load the 4.7 kernel.
the 4.5RC1 kernel still loads. scratching my head..
Thanks for the help.
Aaron Lewis.
_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*
http://join.msn.com/?page=features/virus
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
# [EMAIL PROTECTED] / 2003-01-21 09:42:23 -0800:
> ># [EMAIL PROTECTED] / 2003-01-21 08:36:33 -0800:
> >> >Or maybe, are you really sure you have the proper devices in /dev?
> >>
> >> No, I'm not. At this point I'm not sure of anything, seems like. All
> >I've
> >> done in /dev is a MAKEDEV std with the MAKEDEV directly from /usr/src,
> >> without removing the devices currently in there. It was my understanding
> >> that that would rebuild everything.
> >
> >did you let mergemaster run MAKEDEV for you, or did you run
> >
> >/dev/MAKEDEV std
> >
> >while being in /usr/src? If the latter, you didn't rebuild the
> >devices in /dev/, you created them in /usr/src instead! That would
> >indeed explain your problems.
>
> No, I just meant that I copied MAKEDEV from /usr/src into /dev, and
> then ran ./MAKEDEV std from /dev, as per the UPDATING instructions.
hmm, does UPDATING say you should do that? all I know is mergemaster
asks whether I want to have /dev/* rebuilt, and I let it do so.
UPDATING notwithstanding, you did *not* rebuild ad{4,5}*. take a
look in /dev/MAKEDEV: calling it with "std" does not touch ad* at
all. what you want is:
cd /dev && ./MAKEDEV all ad4 ad5
> Sorry for replying privately, this account isn't on the list. I'll be
> sure to CC it in from now on.
thanks; I *really* prefer to not receive personal copies, though.
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message.see http://www.eyrie.org./~eagle/faqs/questions.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
did you let mergemaster run MAKEDEV for you, or did you run /dev/MAKEDEV std while being in /usr/src? If the latter, you didn't rebuild the devices in /dev/, you created them in /usr/src instead! That >>would indeed explain your problems. No, I just meant that I copied MAKEDEV from /usr/src into /dev, and >then ran ./MAKEDEV std from /dev, as per the UPDATING instructions. I do suspect this as being related, as I just noted that as of the 20020318 entry notes an ATA change. I'm just not sure what else to try. After inspecting /dev a bit more thoroughly, I also found that after a ./MAKEDEV all, everything is updated to the current date except for all of the ad4 entries, and the ad5 entry. These remain dated May 8 2001. The MAKEDEV has been run normally, and from single-user. Seeing as how there was apparently an ATA update in March of 2002.. Is there a way I can safely remove and rebuild those entries? Or is this even related at all? I'm grasping at straws, I know. Thanks for your help. Aaron Lewis. _ The new MSN 8 is here: Try it free* for 2 months http://join.msn.com/?page=dept/dialup To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
# [EMAIL PROTECTED] / 2003-01-21 08:36:33 -0800: > >Or maybe, are you really sure you have the proper devices in /dev? > > No, I'm not. At this point I'm not sure of anything, seems like. All I've > done in /dev is a MAKEDEV std with the MAKEDEV directly from /usr/src, > without removing the devices currently in there. It was my understanding > that that would rebuild everything. did you let mergemaster run MAKEDEV for you, or did you run /dev/MAKEDEV std while being in /usr/src? If the latter, you didn't rebuild the devices in /dev/, you created them in /usr/src instead! That would indeed explain your problems. No, I just meant that I copied MAKEDEV from /usr/src into /dev, and then ran ./MAKEDEV std from /dev, as per the UPDATING instructions. I do suspect this as being related, as I just noted that as of the 20020318 entry notes an ATA change. I'm just not sure what else to try. Sorry for replying privately, this account isn't on the list. I'll be sure to CC it in from now on. I appreciate the suggestions. Aaron Lewis. _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
please at least keep the mailing list among recipients: see my signature. # [EMAIL PROTECTED] / 2003-01-21 08:36:33 -0800: > >Or maybe, are you really sure you have the proper devices in /dev? > > No, I'm not. At this point I'm not sure of anything, seems like. All I've > done in /dev is a MAKEDEV std with the MAKEDEV directly from /usr/src, > without removing the devices currently in there. It was my understanding > that that would rebuild everything. did you let mergemaster run MAKEDEV for you, or did you run /dev/MAKEDEV std while being in /usr/src? If the latter, you didn't rebuild the devices in /dev/, you created them in /usr/src instead! That would indeed explain your problems. do: cd /dev && ./MAKEDEV all and let us know about the results. -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
# [EMAIL PROTECTED] / 2003-01-16 12:52:23 -0800: > Did a clean buildworld, installworld, etc. etc. on a 4.5-RC1 system up to > 4.7-STABLE release. Everything went through fine, no problems. > > Rebuilt kernel and installed the new 4.7 GENERIC kernel, no problems. > > Ran mergemaster, did a MAKEDEV, no problems. > > Rebooted.. and problems. Upon boot, it tries to load up the root partition > off of /dev/ad4s1a (which is correct), but brings up a "Mount boot failure: > 16" error, and asks for a good ufs root location. Typing in > ufs:/dev/ad4s1a does no good. > > IDE controller = Highpoint HPT370 onboard = ar0. > IDE drives = 2x IBM 60gig mirrored = ad4, ad5. > > Eventually, had to boot to 4.5-RC1 kernel which came up fine on > /dev/ad4s1a. The problem is, everything else is 4.7 now, so there's lots of > weirdness. I'm not sure what your problem is. I just recently installed 4.7-RELEASE on a HPT370A-based HighPoint card (RAID1), and the only problems I had was that for some reason disklabel put the / partition beyond the bootable area at the beggining of the disk, and I didn't notice it, and disk numbering. ATA_STATIC_ID seems to be used in 4.7's GENERIC... I'm out of ideas. Or maybe, are you really sure you have the proper devices in /dev? -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
4.7-STABLE upgrade boot failure.
First, let me profusely apologize if this is a dual post, as I tried to post two days ago and never saw it come up on the list. Trying now with a free webmail account. Did a clean buildworld, installworld, etc. etc. on a 4.5-RC1 system up to 4.7-STABLE release. Everything went through fine, no problems. Rebuilt kernel and installed the new 4.7 GENERIC kernel, no problems. Ran mergemaster, did a MAKEDEV, no problems. Rebooted.. and problems. Upon boot, it tries to load up the root partition off of /dev/ad4s1a (which is correct), but brings up a "Mount boot failure: 16" error, and asks for a good ufs root location. Typing in ufs:/dev/ad4s1a does no good. IDE controller = Highpoint HPT370 onboard = ar0. IDE drives = 2x IBM 60gig mirrored = ad4, ad5. Eventually, had to boot to 4.5-RC1 kernel which came up fine on /dev/ad4s1a. The problem is, everything else is 4.7 now, so there's lots of weirdness. The problem is in the kernel? No more support for Highpoint controllers? Is there something else I should be doing in /dev besides a MAKEDEV std? Help? Aaron Lewis [EMAIL PROTECTED] _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
