Can't boot machine after upgrade
Hi all, I just updated my server from 6.3-RELEASE to 6.4-RELEASE and I now can't boot my machine - a rather crappy HP desktop. The boot seems to go along nicely without any errors that I can see but when it comes to mounting the root filesystem it bails out: Trying to mount root from ufs:/dev/ad0s2 Manual root filesystem specification: fstype:device snip ? List valid disk boot devices snip mountroot I've tried entering the root fs (it's the same as above) but it's no go. If I list the valid boot disk devices, it gives me this: list of GEOM managed disk devices: da3 da2 da1 da0 which are all the crappy flash card readers etc. Anybody got any idea on what's going on how to fix it? TIA. BTW, just reply to the list, I can't receive mail ATM so I'll have to read replies in the archive. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't boot machine after upgrade
On Fri, 9 Jan 2009 12:27:20 +, Frank Shute fr...@shute.org.uk wrote: Anybody got any idea on what's going on how to fix it? The messages you presented seem to indicate that ad0 is not found. It's not listed in the available devices, and boot fails. Could you check its presence using a FreeBSD / FreeSBIE boot CD? I'm surprised the hard disk isn't detected at all... are you using the GENERIC kernel? -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't boot machine after upgrade
On Fri, 9 Jan 2009 14:54:55 +, Frank Shute fr...@shute.org.uk wrote: I tried booting a FreeBSD CD going into sysinstall then fdisk but it said it couldn't find any disks. Ah! This means something like the disk *really* can't be accessed. You can easily conclude from % dmesg | grep ^ad if any disk is present, or use % atacontrol list to see what's on the HDD controller. freesbie.org is unfortunately down :( The diagnostic means of a bootable FreeBSD installation CD should be sufficient at first - to eleminate or confirm the idea that the disk is not present. Now, check settings in CMOS setup, check wires, eventually check hard disk in another system, and / or put another disk into the system you want to boot (cross-checking) - the latter one not to install anything, but to see if the disk is recognized correctly. I'm not using GENERIC but IIRC I've only stripped out NIC's etc. Then I think the only thing missing could be the ad driver or something it depends on, but that's nearly impossible to miss. :-) I booted with booting verbose and it's showing this before it jumps to the mountroot prompt: ata1: SATA connect time=0ms ata1: SIGNATURE: eb140101 ata1: ahci_reset devices=0x4ATAPI_MASTER ata1: reinit done .. ata2: reiniting channel .. ata2: SATA connect time=0ms ata2: SIGNATURE: 0101 ata1: ahci_reset devices=0x1ATA_MASTER ata2: reinit done .. ata2: reiniting channel .. *repeats* I see you're using a SATA disk. I don't have such ones, so I'm not sure if they maybe require something in the kernel? ATA PseudoRAID loaded PseudoRAID, only one disk? Hmmm... eventually check BIOS again. Finally, I think the problem occurs this way: The ad0 disk can't be recognized, so the access to ad0s1a won't work. You should try to get access to ad0. Maybe some cross-checking will help, just in case you're having a damaged hard disk... -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't boot machine after upgrade
On Fri, Jan 09, 2009 at 01:43:42PM +0100, Polytropon wrote: On Fri, 9 Jan 2009 12:27:20 +, Frank Shute fr...@shute.org.uk wrote: Anybody got any idea on what's going on how to fix it? The messages you presented seem to indicate that ad0 is not found. It's not listed in the available devices, and boot fails. Could you check its presence using a FreeBSD / FreeSBIE boot CD? I tried booting a FreeBSD CD going into sysinstall then fdisk but it said it couldn't find any disks. freesbie.org is unfortunately down :( I'm surprised the hard disk isn't detected at all... are you using the GENERIC kernel? I'm not using GENERIC but IIRC I've only stripped out NIC's etc. I booted with booting verbose and it's showing this before it jumps to the mountroot prompt: ata1: SATA connect time=0ms ata1: SIGNATURE: eb140101 ata1: ahci_reset devices=0x4ATAPI_MASTER ata1: reinit done .. ata2: reiniting channel .. ata2: SATA connect time=0ms ata2: SIGNATURE: 0101 ata1: ahci_reset devices=0x1ATA_MASTER ata2: reinit done .. ata2: reiniting channel .. *repeats* ATA PseudoRAID loaded Trying to mount root from ufs:/dev/ad0s2 mountroot -- Polytropon Hope that helps some more. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't boot machine after upgrade
On Fri, Jan 09, 2009 at 04:05:57PM +0100, Polytropon wrote: On Fri, 9 Jan 2009 14:54:55 +, Frank Shute fr...@shute.org.uk wrote: I tried booting a FreeBSD CD going into sysinstall then fdisk but it said it couldn't find any disks. Ah! This means something like the disk *really* can't be accessed. You can easily conclude from % dmesg | grep ^ad if any disk is present, or use % atacontrol list to see what's on the HDD controller. freesbie.org is unfortunately down :( The diagnostic means of a bootable FreeBSD installation CD should be sufficient at first - to eleminate or confirm the idea that the disk is not present. Now, check settings in CMOS setup, check wires, eventually check hard disk in another system, and / or put another disk into the system you want to boot (cross-checking) - the latter one not to install anything, but to see if the disk is recognized correctly. I'm not using GENERIC but IIRC I've only stripped out NIC's etc. Then I think the only thing missing could be the ad driver or something it depends on, but that's nearly impossible to miss. :-) I booted with booting verbose and it's showing this before it jumps to the mountroot prompt: ata1: SATA connect time=0ms ata1: SIGNATURE: eb140101 ata1: ahci_reset devices=0x4ATAPI_MASTER ata1: reinit done .. ata2: reiniting channel .. ata2: SATA connect time=0ms ata2: SIGNATURE: 0101 ata1: ahci_reset devices=0x1ATA_MASTER ata2: reinit done .. ata2: reiniting channel .. *repeats* I see you're using a SATA disk. I don't have such ones, so I'm not sure if they maybe require something in the kernel? ATA PseudoRAID loaded PseudoRAID, only one disk? Hmmm... eventually check BIOS again. Finally, I think the problem occurs this way: The ad0 disk can't be recognized, so the access to ad0s1a won't work. You should try to get access to ad0. Maybe some cross-checking will help, just in case you're having a damaged hard disk... Hi Polytropon, Many thanks for all your help. You gave me enough to go on to eventually get it to boot. I changed something in the BIOS: Use legacy IDE or something like that and on boot-up the disk controller fired up and my CD 2 HDs were detected. (Un)fortunately, my boot partition had gone from ad0s2a to ad4s2a, in fact all FreeBSD partitions had migrated to ad4(?) and on the Windows disk from ad2 to ad8. I mounted the root partition and vi'd /etc/fstab. It then rebooted ok. I hadn't rebooted the machine for 200days but I must have changed something, somewhere. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
