On Fri, 2005-01-07 at 06:08, Qian Qiao wrote: > > > > > >That machine was running OK for the past few weeks. He then realized > > >his error, and hence changed the CHOST, CCFLAG, and done a bootstrap > > >(using that actual machine, not a livecd). > > > > > >Now the machine is completely screwed. Any chance we can rescue? And How? > > > > > >The hosting company has told us that the machine reports /dev/BOOT > > >/dev/ROOT missing during a fsck, even with a correct fstab file. What > > >could cause that? > > > > > > > > Thats only going to show up if you have an incorrect /etc/fstab. > > When he bootstrapped chances are portage told him to run etc-update and > > he did, probably merging a new /etc/fstab over the old one. > > This would happen if he just used -5 to merge all changes. > > Regardless, you will need a liveCD to fix it. > > The strange thing is, the /etc/fstab file was untouched. and was the > correctly one that's been used for the past few weeks, which is quite > puzzling.
I always refer to the physical partition rather than the name. eg: /dev/hda1 rather than /dev/ROOT This way, I don't get any naming convention errors. -- Ow Mun Heng Gentoo/Linux on DELL D600 1.4Ghz 98% Microsoft(tm) Free!! Neuromancer 10:56:45 up 1:58, 5 users, load average: 0.61, 0.50, 0.44 -- gentoo-user@gentoo.org mailing list
