Woodchuck wrote on Mon, Jul 02, 2007 at 03:31:04PM -0400: > On Mon, 2 Jul 2007, David B. wrote:
>> Hi, hate to bother. I'm working in 3.8 Hm, this is unrelated, but anyway: Release 3.8 is past its end of life and no more supported. You should upgrade to release 4.1 soon - you *do* want to have bugs and security holes fixed. >> and I've run across something new and can't figure out. >> For some reason, on this box a drive isn't mounting, and >> the boot blows and asks for shell. so, I go to shell and >> I've tried to edit the fstab file to remark out the >> mountpoint that's gone bad. Did you try to run fsck(8) manually? Perhaps that's all you need to do to fix the file system, and perhaps you do not even need to change your fstab? Of course, without any error message, it's hard to guess what's up... >> First off, VI isn't there, This sounds like /usr has its own partition on your box - which is really fine as far as it goes. But remeber that in single user mode, no file system except / is mounted automatically. >> so I've tried ,s/old/new/g using ed, but then it says that >> it's a read only file, and when I try to whoami, or to su, >> it doesn't see the programs. So, all I need to do is to >> be able to edit fstab and remark out the bad mount point >> and I can take it from there. thanks > Remount / with write access. I believe that would be: > # mount -u -w / > No need for "su", you're already root. Good advice. To expand a bit: When entering single user mode on i386, the first commands i type often look roughly like this: # kbd de # or whatever keyboard happens to be connected # export TERM=vt220 # or whatever terminal happens... # mount -uw / # mount /var # if that's seperate and available # mount /tmp # if that's seperate and available # mount /usr # unless it's /usr that's busted ;-( # vi /etc/fstab # or whatever work needs to be done
