Re: fubar'ed it good this time...
On Mon, Jul 4, 2011 at 15:30, Dr. A. Haakh bugrepor...@haakh.de wrote: Kurt Buff schrieb: On Thu, Jun 30, 2011 at 17:31, Kurt Buffkurt.b...@gmail.com wrote: On Tue, Jun 28, 2011 at 06:50, Dr. A. Haakhbugrepor...@haakh.de wrote: Polytropon schrieb: On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Check if you can download FreeSBIE somewhere. It's a live system using the 5.x and 6.x kernel which should be fine. Next to two GUI modes (light, heavy) it also has a versatile maintenance mode for such operations. I have already successfully used this system for solving similar situations, for diagnostics, and for data recovery preparation. The loader obviously knows how to deal with the filesystem because he loads the failing new kernel. So the easiest solution would be to boot an older kernel if available. I don't know how freebsd-update deals with older kernels, he should still be around. First guess is /boot/kernel.old/kernel. So get the loader-prompt, unload kernel and try load /boot/kernel.old/kernel. Andreas OK - to continue, while I have a few free minutes. I have been able to load the old kernel by going to the loader prompt from the boot menu, and doing unload kernel load /boot/kernel.old/kernel That barked about linproc in fstab, so I edited that out. Then, the next go-round: It complained about mismatches on daemon_saver.ko - a version mismatch, so I've commented that out of /etc/rc.conf. It also complained about linux.ko, so that's been commented out in /etc/rc.conf as well. I'm now able to reboot cleanly with the old kernel. After doing 'freebsd-update install' for the second time, I still can't get 8.2 to boot - same issue, only acd0 is recognized. However, I'm logged in as root under the old kernel, though I haven't start XFCE4, and don't have wireless running. This one is getting to be fun... Kurt So, I tried booting from the old kernel again, and then did a 'freebsd-update rollback', and that worked just fine. I thought I'd try again, but first did a 'freebsd-update fetch' and 'freebsd-update install' to get the latest 8.1 updates. That worked just fine, so I did a 'freebsd-update -r 8.2-RELEASE fetch' again, then a 'freebsd-update install', which went just fine, and after that rebooted as directed to attempt the second 'freebsd-update install'. That's when the same thing happened - i got dumped into the mountroot prompt again. And, again, rebooting and escaping to the loader prompt allows me to unload the kernel, load /boot/kernel.old/kernel then autoboot, and boot up. Same as before. Any thoughts? Redo the rollback to 8.1 and install the 8.2-STABLE source-tree. You can install the 8.1-sources from cd and update them to 8.2-STABLE using csup. Put the following lines in /etc/make.conf SUP_UPDATE= YES SUP= /usr/bin/csup SUPHOST= cvsup2.de.freebsd.org SUPFILE= /usr/share/examples/cvsup/stable-supfile Make sure that stable-supfile contains the right tag *default release=cvs tag=RELENG_8 Then goto /usr/src and make update |tee _Update.log Once the source-tree is up-to-date: Have a look at the FreeBSD Handbook: Chapter 8 - Configuring the FreeBSD Kernel. Copy GENERIC to e.g. MYKERNEL, edit MYKERNEL and add some debug-flags. See /sys/conf/NOTES for additional debug-options. You may as well try GENERIC - maybe your problem is gone... Then go to /usr/src and do s.th. like make buildkernel KERNCONF=MYKERNEL and if the kernel built fine install it: make KERNCONF=YOURKERNEL installkernel. You can also add KERNCONF=MYKERNEL to /etc/make.conf instead of adding it to the make command. Installing the new kernels moves /boot/kernel to /boot/kernel.old and installs the new one in /boot/kernel. If the new kernel fails again, you can delete it: rm -rf /boot/kernel mv /boot/kernel.old /boot/kernel thus putting the previous kernel in the right place. If the new kernel fails again, then press the Scroll-key and navigate to the disk-probe usind page-up-key. Write down the messages or take a photo and post it to this list. If the STABLE kernel boots fine you will probably want to remove all the debugging stuff and rebuild it. If you intend to keep the 8.1-kernel move it to e.g /boot/kernel-8.1 so it will not be deleted, when you install new ones and you can always load /boot/kernel-8.1/kernel from the loader Once the new kernel boots fine, cd /usr/src and follow the instructions in Makefile how to build and install a new kernel and a new world. At this point there is no more need for kernel-8.1: delete it. Andreas That is roughly the direction I was thinking of heading next. I'll try this out, and get back to the list with results. Thanks! Kurt ___
Re: fubar'ed it good this time...
Kurt Buff schrieb: On Thu, Jun 30, 2011 at 17:31, Kurt Buffkurt.b...@gmail.com wrote: On Tue, Jun 28, 2011 at 06:50, Dr. A. Haakhbugrepor...@haakh.de wrote: Polytropon schrieb: On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Check if you can download FreeSBIE somewhere. It's a live system using the 5.x and 6.x kernel which should be fine. Next to two GUI modes (light, heavy) it also has a versatile maintenance mode for such operations. I have already successfully used this system for solving similar situations, for diagnostics, and for data recovery preparation. The loader obviously knows how to deal with the filesystem because he loads the failing new kernel. So the easiest solution would be to boot an older kernel if available. I don't know how freebsd-update deals with older kernels, he should still be around. First guess is /boot/kernel.old/kernel. So get the loader-prompt, unload kernel and try load /boot/kernel.old/kernel. Andreas OK - to continue, while I have a few free minutes. I have been able to load the old kernel by going to the loader prompt from the boot menu, and doing unload kernel load /boot/kernel.old/kernel That barked about linproc in fstab, so I edited that out. Then, the next go-round: It complained about mismatches on daemon_saver.ko - a version mismatch, so I've commented that out of /etc/rc.conf. It also complained about linux.ko, so that's been commented out in /etc/rc.conf as well. I'm now able to reboot cleanly with the old kernel. After doing 'freebsd-update install' for the second time, I still can't get 8.2 to boot - same issue, only acd0 is recognized. However, I'm logged in as root under the old kernel, though I haven't start XFCE4, and don't have wireless running. This one is getting to be fun... Kurt So, I tried booting from the old kernel again, and then did a 'freebsd-update rollback', and that worked just fine. I thought I'd try again, but first did a 'freebsd-update fetch' and 'freebsd-update install' to get the latest 8.1 updates. That worked just fine, so I did a 'freebsd-update -r 8.2-RELEASE fetch' again, then a 'freebsd-update install', which went just fine, and after that rebooted as directed to attempt the second 'freebsd-update install'. That's when the same thing happened - i got dumped into the mountroot prompt again. And, again, rebooting and escaping to the loader prompt allows me to unload the kernel, load /boot/kernel.old/kernel then autoboot, and boot up. Same as before. Any thoughts? Redo the rollback to 8.1 and install the 8.2-STABLE source-tree. You can install the 8.1-sources from cd and update them to 8.2-STABLE using csup. Put the following lines in /etc/make.conf SUP_UPDATE= YES SUP=/usr/bin/csup SUPHOST=cvsup2.de.freebsd.org SUPFILE=/usr/share/examples/cvsup/stable-supfile Make sure that stable-supfile contains the right tag *default release=cvs tag=RELENG_8 Then goto /usr/src and make update |tee _Update.log Once the source-tree is up-to-date: Have a look at the FreeBSD Handbook: Chapter 8 - Configuring the FreeBSD Kernel. Copy GENERIC to e.g. MYKERNEL, edit MYKERNEL and add some debug-flags. See /sys/conf/NOTES for additional debug-options. You may as well try GENERIC - maybe your problem is gone... Then go to /usr/src and do s.th. like make buildkernel KERNCONF=MYKERNEL and if the kernel built fine install it: make KERNCONF=YOURKERNEL installkernel. You can also add KERNCONF=MYKERNEL to /etc/make.conf instead of adding it to the make command. Installing the new kernels moves /boot/kernel to /boot/kernel.old and installs the new one in /boot/kernel. If the new kernel fails again, you can delete it: rm -rf /boot/kernel mv /boot/kernel.old /boot/kernel thus putting the previous kernel in the right place. If the new kernel fails again, then press the Scroll-key and navigate to the disk-probe usind page-up-key. Write down the messages or take a photo and post it to this list. If the STABLE kernel boots fine you will probably want to remove all the debugging stuff and rebuild it. If you intend to keep the 8.1-kernel move it to e.g /boot/kernel-8.1 so it will not be deleted, when you install new ones and you can always load /boot/kernel-8.1/kernel from the loader Once the new kernel boots fine, cd /usr/src and follow the instructions in Makefile how to build and install a new kernel and a new world. At this point there is no more need for kernel-8.1: delete it. Andreas ___ 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: fubar'ed it good this time...
On Thu, Jun 30, 2011 at 17:31, Kurt Buff kurt.b...@gmail.com wrote: On Tue, Jun 28, 2011 at 06:50, Dr. A. Haakh bugrepor...@haakh.de wrote: Polytropon schrieb: On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Check if you can download FreeSBIE somewhere. It's a live system using the 5.x and 6.x kernel which should be fine. Next to two GUI modes (light, heavy) it also has a versatile maintenance mode for such operations. I have already successfully used this system for solving similar situations, for diagnostics, and for data recovery preparation. The loader obviously knows how to deal with the filesystem because he loads the failing new kernel. So the easiest solution would be to boot an older kernel if available. I don't know how freebsd-update deals with older kernels, he should still be around. First guess is /boot/kernel.old/kernel. So get the loader-prompt, unload kernel and try load /boot/kernel.old/kernel. Andreas OK - to continue, while I have a few free minutes. I have been able to load the old kernel by going to the loader prompt from the boot menu, and doing unload kernel load /boot/kernel.old/kernel That barked about linproc in fstab, so I edited that out. Then, the next go-round: It complained about mismatches on daemon_saver.ko - a version mismatch, so I've commented that out of /etc/rc.conf. It also complained about linux.ko, so that's been commented out in /etc/rc.conf as well. I'm now able to reboot cleanly with the old kernel. After doing 'freebsd-update install' for the second time, I still can't get 8.2 to boot - same issue, only acd0 is recognized. However, I'm logged in as root under the old kernel, though I haven't start XFCE4, and don't have wireless running. This one is getting to be fun... Kurt So, I tried booting from the old kernel again, and then did a 'freebsd-update rollback', and that worked just fine. I thought I'd try again, but first did a 'freebsd-update fetch' and 'freebsd-update install' to get the latest 8.1 updates. That worked just fine, so I did a 'freebsd-update -r 8.2-RELEASE fetch' again, then a 'freebsd-update install', which went just fine, and after that rebooted as directed to attempt the second 'freebsd-update install'. That's when the same thing happened - i got dumped into the mountroot prompt again. And, again, rebooting and escaping to the loader prompt allows me to unload the kernel, load /boot/kernel.old/kernel then autoboot, and boot up. Same as before. Any thoughts? ___ 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: fubar'ed it good this time...
On Tue, Jun 28, 2011 at 06:50, Dr. A. Haakh bugrepor...@haakh.de wrote: Polytropon schrieb: On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Check if you can download FreeSBIE somewhere. It's a live system using the 5.x and 6.x kernel which should be fine. Next to two GUI modes (light, heavy) it also has a versatile maintenance mode for such operations. I have already successfully used this system for solving similar situations, for diagnostics, and for data recovery preparation. The loader obviously knows how to deal with the filesystem because he loads the failing new kernel. So the easiest solution would be to boot an older kernel if available. I don't know how freebsd-update deals with older kernels, he should still be around. First guess is /boot/kernel.old/kernel. So get the loader-prompt, unload kernel and try load /boot/kernel.old/kernel. Andreas OK - to continue, while I have a few free minutes. I have been able to load the old kernel by going to the loader prompt from the boot menu, and doing unload kernel load /boot/kernel.old/kernel That barked about linproc in fstab, so I edited that out. Then, the next go-round: It complained about mismatches on daemon_saver.ko - a version mismatch, so I've commented that out of /etc/rc.conf. It also complained about linux.ko, so that's been commented out in /etc/rc.conf as well. I'm now able to reboot cleanly with the old kernel. After doing 'freebsd-update install' for the second time, I still can't get 8.2 to boot - same issue, only acd0 is recognized. However, I'm logged in as root under the old kernel, though I haven't start XFCE4, and don't have wireless running. This one is getting to be fun... Kurt ___ 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: fubar'ed it good this time...
On Mon, Jun 27, 2011 at 20:24, Polytropon free...@edvax.de wrote: On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Check if you can download FreeSBIE somewhere. It's a live system using the 5.x and 6.x kernel which should be fine. Next to two GUI modes (light, heavy) it also has a versatile maintenance mode for such operations. I have already successfully used this system for solving similar situations, for diagnostics, and for data recovery preparation. The 7.4 livefs CD finds the hardware, and there was much rejoicing! I mounted the hard drive under /mnt, and I looked at /mnt/etc/fstab, and it's clean, and I also looked at /mnt/boot/loader.conf, and it's clean as well. So is /mnt/boot/loader.rc. However, during the boot process from the hard drive, I still saw scrolling by a reference to a syntax error, but it went too fast and I can't see what file was referenced. So, I started looking at the handbook to see if I could figure out which file might have been updated incorrectly. One was boot/device.hints - there was a string of equal signs as the first line of that file. How they got there I don't know, but I deleted that line, and that seems to have helped, because now I don't see the syntax error - but I'm still getting the mountroot prompt, and it's very possible that some other error is occuring in the quick boot process before the user-selectable menu is displayed. It's late, so I'm going to bed now, but I'll keep working it tomorrow. Kurt ___ 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: fubar'ed it good this time...
On Tue, Jun 28, 2011 at 06:50, Dr. A. Haakh bugrepor...@haakh.de wrote: Polytropon schrieb: On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Check if you can download FreeSBIE somewhere. It's a live system using the 5.x and 6.x kernel which should be fine. Next to two GUI modes (light, heavy) it also has a versatile maintenance mode for such operations. I have already successfully used this system for solving similar situations, for diagnostics, and for data recovery preparation. The loader obviously knows how to deal with the filesystem because he loads the failing new kernel. So the easiest solution would be to boot an older kernel if available. I don't know how freebsd-update deals with older kernels, he should still be around. First guess is /boot/kernel.old/kernel. So get the loader-prompt, unload kernel and try load /boot/kernel.old/kernel. Andreas That seems like a worthy thing to try. I'll do that tomorrow. Thanks, Kurt ___ 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: fubar'ed it good this time...
Polytropon schrieb: On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Check if you can download FreeSBIE somewhere. It's a live system using the 5.x and 6.x kernel which should be fine. Next to two GUI modes (light, heavy) it also has a versatile maintenance mode for such operations. I have already successfully used this system for solving similar situations, for diagnostics, and for data recovery preparation. The loader obviously knows how to deal with the filesystem because he loads the failing new kernel. So the easiest solution would be to boot an older kernel if available. I don't know how freebsd-update deals with older kernels, he should still be around. First guess is /boot/kernel.old/kernel. So get the loader-prompt, unload kernel and try load /boot/kernel.old/kernel. Andreas ___ 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: fubar'ed it good this time...
On Mon, Jun 27, 2011 at 10:21, Warren Block wbl...@wonkity.com wrote: On Mon, 27 Jun 2011, Kurt Buff wrote: On Mon, Jun 27, 2011 at 06:40, Warren Block wbl...@wonkity.com wrote: On Sun, 26 Jun 2011, Kurt Buff wrote: Sitrep: Lenovo T61, dual booting WinXP and FreeBSD (amd64 8.1-RELEASE) on a 500gb drive. Just did a freebsd-update from 8.1 to 8.2, just doing the second boot to do 'freebsd-update install' for the second time, and got dumped into the mountroot prompt. AFAICT, I managed somehow to write something strange into /etc/fstab. Can't tell what it is, because during boot it passes by too quickly for me to read, and the boot process dumps me into the mountroot prompt. Scroll Lock and Page Up/Down should work there to scroll back to see the disk device numbers. Scroll lok and page up work, and what I see is the following, copied by hand: atapci0: Intel ICH8M SATA300 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1c30-0x1c3f,0x1c20,0x1x2f at decive 31.2 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] SATA... are there any ad or ada devices shown? Something else worth trying is breaking into the loader and loading the ahci driver. XP isn't normally found using AHCI, but Lenovo might have set that up. Check the BIOS for disk mode settings. No ad or ada devices. Disk mode is set for compatibility, not AHCI. Still, I don't know what would be different from 8.1 to 8.2. Did you have a custom kernel? Stone stock kernel, no mods. Kurt ___ 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: fubar'ed it good this time...
On Mon, Jun 27, 2011 at 20:24, Polytropon free...@edvax.de wrote: On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Check if you can download FreeSBIE somewhere. It's a live system using the 5.x and 6.x kernel which should be fine. Next to two GUI modes (light, heavy) it also has a versatile maintenance mode for such operations. I have already successfully used this system for solving similar situations, for diagnostics, and for data recovery preparation. I'll google for that later - I like that suggestion. I'm pressed for time this morning, so I'm downloading the 7.4 livefs iso, and will see if that will do the trick this evening. Thanks, Kurt ___ 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: fubar'ed it good this time...
On 6/27/11 8:17 AM, Kurt Buff wrote: Sitrep: Lenovo T61, dual booting WinXP and FreeBSD (amd64 8.1-RELEASE) on a 500gb drive. Just did a freebsd-update from 8.1 to 8.2, just doing the second boot to do 'freebsd-update install' for the second time, and got dumped into the mountroot prompt. AFAICT, I managed somehow to write something strange into /etc/fstab. Can't tell what it is, because during boot it passes by too quickly for me to read, and the boot process dumps me into the mountroot prompt. WinXP still boots just fine, and the FreeBSD boot manager is in place, and was working before the update. FreeBSD was booting just fine from /dev/ad0s2a, prior to running freebsd-update. Now, however, when I select f1 to boot FreeBSD, I get the boot menu, output from the boot process, and (as I've mentioned) then I get the mountroot prompt. I've even downloaded and burned the 8.2 live boot iso, but it says it can't find a hard drive from sysinstall - both the Fdisk and Label options say No disks found! Please verify that your disk controller is being properly probed at boot time. See the Hardware guide on the Documentation menu for clues on diagnosing this type of problem. I get no love from the Fixit shell, either, with /dev being void of any reference to the hard drive - just acd0. I'm pretty sure that if I can mount the disk that I can just edit the cruft out of /etc/fstab, and it will all be fine, but I can't get there... Anyone have a thought on how to get this running? I've googled myself silly on this, and am getting nowhere. Kurt ___ 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 You'll want to download a live CD with UFS support :) MFSBSD comes to mind: http://mfsbsd.vx.sk/ ___ 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: fubar'ed it good this time...
On Sun, 26 Jun 2011, Kurt Buff wrote: Sitrep: Lenovo T61, dual booting WinXP and FreeBSD (amd64 8.1-RELEASE) on a 500gb drive. Just did a freebsd-update from 8.1 to 8.2, just doing the second boot to do 'freebsd-update install' for the second time, and got dumped into the mountroot prompt. AFAICT, I managed somehow to write something strange into /etc/fstab. Can't tell what it is, because during boot it passes by too quickly for me to read, and the boot process dumps me into the mountroot prompt. Scroll Lock and Page Up/Down should work there to scroll back to see the disk device numbers. WinXP still boots just fine, and the FreeBSD boot manager is in place, and was working before the update. FreeBSD was booting just fine from /dev/ad0s2a, prior to running freebsd-update. Don't know what would cause that. Custom kernels could have the ATA_STATIC_ID option removed, which might give the disk a different number, ad2 or ad4 usually. The BIOS could have AHCI mode set, but that should not change with 8.2. That would make the disk ada0. I second the suggestion of mfsBSD. ___ 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: fubar'ed it good this time...
On Mon, Jun 27, 2011 at 03:03, Damien Fleuriot m...@my.gd wrote: On 6/27/11 8:17 AM, Kurt Buff wrote: snip I've even downloaded and burned the 8.2 live boot iso, but it says it can't find a hard drive from sysinstall - both the Fdisk and Label options say No disks found! Please verify that your disk controller is being properly probed at boot time. See the Hardware guide on the Documentation menu for clues on diagnosing this type of problem. I get no love from the Fixit shell, either, with /dev being void of any reference to the hard drive - just acd0. I'm pretty sure that if I can mount the disk that I can just edit the cruft out of /etc/fstab, and it will all be fine, but I can't get there... snip You'll want to download a live CD with UFS support :) MFSBSD comes to mind: http://mfsbsd.vx.sk/ Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Kurt ___ 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: fubar'ed it good this time...
On 6/27/11 3:40 PM, Kurt Buff wrote: On Mon, Jun 27, 2011 at 03:03, Damien Fleuriot m...@my.gd wrote: On 6/27/11 8:17 AM, Kurt Buff wrote: snip I've even downloaded and burned the 8.2 live boot iso, but it says it can't find a hard drive from sysinstall - both the Fdisk and Label options say No disks found! Please verify that your disk controller is being properly probed at boot time. See the Hardware guide on the Documentation menu for clues on diagnosing this type of problem. I get no love from the Fixit shell, either, with /dev being void of any reference to the hard drive - just acd0. I'm pretty sure that if I can mount the disk that I can just edit the cruft out of /etc/fstab, and it will all be fine, but I can't get there... snip You'll want to download a live CD with UFS support :) MFSBSD comes to mind: http://mfsbsd.vx.sk/ Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Kurt Works just fine for non ZFS stuff, we actually use it here with PXE to install new firewalls. Really, it'll do what you want, it has ee which is all you need. ___ 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: fubar'ed it good this time...
On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: Your advice sounds reasonable, but that site seems devoted to zfs bootables. I wonder if an 8.1 livefs iso will do the trick... Check if you can download FreeSBIE somewhere. It's a live system using the 5.x and 6.x kernel which should be fine. Next to two GUI modes (light, heavy) it also has a versatile maintenance mode for such operations. I have already successfully used this system for solving similar situations, for diagnostics, and for data recovery preparation. -- Polytropon 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
