RE: cannot boot after updating to 5.3 stable
Thanks for the answer, But i have no luck, it still won't boot : mountroot? ad0 fd0 mountrootufs:ad0s1a Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot Thanks for the answer. DL vG. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cannot boot after updating to 5.3 stable
You can boot off a live file system (the fixit CD/floppy) and examine the mountpoints which are already available on the hard disk. I have the feeling that the reason why it is not booting is, you are not setting the proper mount point. Regards, S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India -Original Message- From: Della Virgina [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 6:51 To: Subhro Cc: freebsd-questions@freebsd.org Subject: RE: cannot boot after updating to 5.3 stable Thanks for the answer, But i have no luck, it still won't boot : mountroot? ad0 fd0 mountrootufs:ad0s1a Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot Thanks for the answer. DL vG. smime.p7s Description: S/MIME cryptographic signature
cannot boot after updating to 5.3 stable
Dear all, I've been updating to 5.3 stable. but after make installkernel, my box won't boot and error says : boot:boot -s ... Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot my device.hints : hint.fdc.0.at=isa hint.fdc.0.port=0x3F0 hint.fdc.0.irq=6 hint.fdc.0.drq=2 hint.fd.0.at=fdc0 hint.fd.0.drive=0 hint.fd.1.at=fdc0 hint.fd.1.drive=1 hint.ata.0.at=isa hint.ata.0.port=0x1F0 hint.ata.0.irq=14 hint.ata.1.at=isa hint.ata.1.port=0x170 hint.ata.1.irq=15 #hint.adv.0.at=isa #hint.adv.0.disabled=1 #hint.bt.0.at=isa #hint.bt.0.disabled=1 #hint.aha.0.at=isa #hint.aha.0.disabled=1 hint.aic.0.at=isa hint.aic.0.disabled=1 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.atkbd.0.at=atkbdc hint.atkbd.0.irq=1 hint.psm.0.at=atkbdc hint.psm.0.irq=12 hint.vga.0.at=isa hint.sc.0.at=isa hint.sc.0.flags=0x100 hint.vt.0.at=isa hint.vt.0.disabled=1 hint.apm.0.disabled=1 hint.apm.0.flags=0x20 hint.pcic.0.at=isa # hint.pcic.0.irq=10 # Default to polling # hint.pcic.0.irq=10 # Default to polling hint.pcic.0.port=0x3e0 hint.pcic.0.maddr=0xd hint.pcic.1.at=isa hint.pcic.1.irq=11 hint.pcic.1.port=0x3e2 hint.pcic.1.maddr=0xd4000 hint.pcic.1.disabled=1 hint.sio.0.at=isa hint.sio.0.port=0x3F8 hint.sio.0.flags=0x10 hint.sio.0.irq=4 hint.sio.1.at=isa hint.sio.1.port=0x2F8 hint.sio.1.irq=3 hint.sio.2.at=isa hint.sio.2.disabled=1 hint.sio.2.port=0x3E8 hint.sio.2.irq=5 hint.sio.3.at=isa hint.sio.3.disabled=1 hint.sio.3.port=0x2E8 hint.sio.3.irq=9 hint.ppc.0.at=isa hint.ppc.0.irq=7 hint.ed.0.at=isa hint.ed.0.disabled=1 hint.ed.0.port=0x280 hint.ed.0.irq=10 hint.ed.0.maddr=0xd8000 hint.cs.0.at=isa hint.cs.0.disabled=1 hint.cs.0.port=0x300 hint.sn.0.at=isa hint.sn.0.disabled=1 hint.sn.0.port=0x300 hint.sn.0.irq=10 hint.ie.0.at=isa hint.ie.0.disabled=1 hint.ie.0.port=0x300 hint.ie.0.irq=10 hint.ie.0.maddr=0xd hint.fe.0.at=isa hint.fe.0.disabled=1 hint.fe.0.port=0x300 hint.lnc.0.at=isa hint.lnc.0.disabled=1 hint.lnc.0.port=0x280 hint.lnc.0.irq=10 hint.lnc.0.drq=0 my /etc/fstab : # of network filesystems before modifying this file. # # DeviceMountpoint FStype Options Dump Pass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1g /cache ufs rw 2 2 /dev/ad0s1f /home ufs rw 2 2 /dev/ad0s1e /usrufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 anyone can help me ? Dl. Vg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cannot boot after updating to 5.3 stable
Your problem is, somehow the mountpoint entries in /etc/fstab have messed up. As a result the system cant find the root file system. At the Mount Prompt type ? to get a list of all the valid mountpoints. Then manually mount all the mount points. Once you point the system the root it will straight go into the single user mode. You can then go into /dev and see what partitions are there. Mount the partitions manually and then open up /etc/fstab in your favorite text editor and make the necessary changes. The nnext boot onwards the box won't complain. BTW, you wont be able to open any text editor until and unless /usr is mounted. Because all the binaries (including the text editor, vi in my case) resides in /usr. Regards, S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Rino M Nur Sent: Saturday, January 29, 2005 8:03 To: freebsd-questions@freebsd.org Subject: cannot boot after updating to 5.3 stable Dear all, I've been updating to 5.3 stable. but after make installkernel, my box won't boot and error says : boot:boot -s ... Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot my device.hints : hint.fdc.0.at=isa hint.fdc.0.port=0x3F0 hint.fdc.0.irq=6 hint.fdc.0.drq=2 hint.fd.0.at=fdc0 hint.fd.0.drive=0 hint.fd.1.at=fdc0 hint.fd.1.drive=1 hint.ata.0.at=isa hint.ata.0.port=0x1F0 hint.ata.0.irq=14 hint.ata.1.at=isa hint.ata.1.port=0x170 hint.ata.1.irq=15 #hint.adv.0.at=isa #hint.adv.0.disabled=1 #hint.bt.0.at=isa #hint.bt.0.disabled=1 #hint.aha.0.at=isa #hint.aha.0.disabled=1 hint.aic.0.at=isa hint.aic.0.disabled=1 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.atkbd.0.at=atkbdc hint.atkbd.0.irq=1 hint.psm.0.at=atkbdc hint.psm.0.irq=12 hint.vga.0.at=isa hint.sc.0.at=isa hint.sc.0.flags=0x100 hint.vt.0.at=isa hint.vt.0.disabled=1 hint.apm.0.disabled=1 hint.apm.0.flags=0x20 hint.pcic.0.at=isa # hint.pcic.0.irq=10 # Default to polling # hint.pcic.0.irq=10 # Default to polling hint.pcic.0.port=0x3e0 hint.pcic.0.maddr=0xd hint.pcic.1.at=isa hint.pcic.1.irq=11 hint.pcic.1.port=0x3e2 hint.pcic.1.maddr=0xd4000 hint.pcic.1.disabled=1 hint.sio.0.at=isa hint.sio.0.port=0x3F8 hint.sio.0.flags=0x10 hint.sio.0.irq=4 hint.sio.1.at=isa hint.sio.1.port=0x2F8 hint.sio.1.irq=3 hint.sio.2.at=isa hint.sio.2.disabled=1 hint.sio.2.port=0x3E8 hint.sio.2.irq=5 hint.sio.3.at=isa hint.sio.3.disabled=1 hint.sio.3.port=0x2E8 hint.sio.3.irq=9 hint.ppc.0.at=isa hint.ppc.0.irq=7 hint.ed.0.at=isa hint.ed.0.disabled=1 hint.ed.0.port=0x280 hint.ed.0.irq=10 hint.ed.0.maddr=0xd8000 hint.cs.0.at=isa hint.cs.0.disabled=1 hint.cs.0.port=0x300 hint.sn.0.at=isa hint.sn.0.disabled=1 hint.sn.0.port=0x300 hint.sn.0.irq=10 hint.ie.0.at=isa hint.ie.0.disabled=1 hint.ie.0.port=0x300 hint.ie.0.irq=10 hint.ie.0.maddr=0xd hint.fe.0.at=isa hint.fe.0.disabled=1 hint.fe.0.port=0x300 hint.lnc.0.at=isa hint.lnc.0.disabled=1 hint.lnc.0.port=0x280 hint.lnc.0.irq=10 hint.lnc.0.drq=0 my /etc/fstab : # of network filesystems before modifying this file. # # DeviceMountpoint FStype Options Dump Pass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1g /cache ufs rw 2 2 /dev/ad0s1f /home ufs rw 2 2 /dev/ad0s1e /usrufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 anyone can help me ? Dl. Vg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
RE: cannot boot after updating to 5.3 stable
On Fri, 2005-01-28 at 22:35, Subhro wrote: Your problem is, somehow the mountpoint entries in /etc/fstab have messed up. As a result the system cant find the root file system. At the Mount Prompt type ? to get a list of all the valid mountpoints. Then manually mount all the mount points. Once you point the system the root it will straight go into the single user mode. You can then go into /dev and see what partitions are there. Mount the partitions manually and then open up /etc/fstab in your favorite text editor and make the necessary changes. The nnext boot onwards the box won't complain. BTW, you wont be able to open any text editor until and unless /usr is mounted. Because all the binaries (including the text editor, vi in my case) resides in /usr. There is a primitive but usable editor called ed in /bin. It dates back to the stone age of computing, and you will do better if you can practise with it (or at least print out the manual on paper) before you really need it. It is there for emergencies like fixing up /etc/fstab. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cannot boot after updating to 5.3 stable
Thanks Mike :-) Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India -Original Message- From: Mike Jeays [mailto:[EMAIL PROTECTED] Sent: Saturday, January 29, 2005 9:28 To: Subhro Cc: 'Rino M Nur'; freebsd-questions@freebsd.org Subject: RE: cannot boot after updating to 5.3 stable On Fri, 2005-01-28 at 22:35, Subhro wrote: Your problem is, somehow the mountpoint entries in /etc/fstab have messed up. As a result the system cant find the root file system. At the Mount Prompt type ? to get a list of all the valid mountpoints. Then manually mount all the mount points. Once you point the system the root it will straight go into the single user mode. You can then go into /dev and see what partitions are there. Mount the partitions manually and then open up /etc/fstab in your favorite text editor and make the necessary changes. The nnext boot onwards the box won't complain. BTW, you wont be able to open any text editor until and unless /usr is mounted. Because all the binaries (including the text editor, vi in my case) resides in /usr. There is a primitive but usable editor called ed in /bin. It dates back to the stone age of computing, and you will do better if you can practise with it (or at least print out the manual on paper) before you really need it. It is there for emergencies like fixing up /etc/fstab. smime.p7s Description: S/MIME cryptographic signature
