Hosed file system read only!! NEED ADVISE!!
Well I finally hosed my machine. In an effort to sync up my clock I rebooted the Linux server (after uptime of 40 days) When it boots I get an error to the effect the file system is read only. This is probably due to the fact that I made an entry in /etc/passwd for a samba user like WIN2KMACHINENAME$:*1000:900:WIN2KUSERNAME:/dev/null:dev/null I would occasionally get errors about the /dev/null but thought I would fix it later. Unfortunately, I rebooted and now cannot make changes to the system. I can log on and telnet in but... cannot change the /etc/passwd could someone be kind enough to walk me through this? I know Ill have to boot into rescue mode (cd rom is not bootable) but don't have any experience as what to "fix" the boot message file in its entirety is at http://www.connix.com/~dizzy73/badboot.html many thanks in advance ( I gotta get this fixed asap) rob
If you can log in to the system, you could do a mount -o remount,rw / Then you can edit the files that cause this mayhem It would also be interesting to see what you've done with /etc/fstab to get this way Regards Anders On Monday 25 June 2001 02:55, dizzy wrote:
Well I finally hosed my machine. In an effort to sync up my clock I rebooted the Linux server (after uptime of 40 days) When it boots I get an error to the effect the file system is read only.
This is probably due to the fact that I made an entry in /etc/passwd for a samba user like
WIN2KMACHINENAME$:*1000:900:WIN2KUSERNAME:/dev/null:dev/null
I would occasionally get errors about the /dev/null but thought I would fix it later. Unfortunately, I rebooted and now cannot make changes to the system.
I can log on and telnet in but... cannot change the /etc/passwd
could someone be kind enough to walk me through this?
I know Ill have to boot into rescue mode (cd rom is not bootable) but don't have any experience as what to "fix"
the boot message file in its entirety is at http://www.connix.com/~dizzy73/badboot.html
many thanks in advance ( I gotta get this fixed asap)
rob
IM not exactly sure of the command you gave mount -o remount,rw / If I do mount I get /dev/hda2 on / type ext3 (rw) proc on /proc type proc (rw) What exactly do I need to do???? my fstab ########### /etc/fstab################# /dev/hda5 swap swap defaults 0 0 /dev/hda2 / ext2 defaults 1 1 /dev/hda7 /var ext2 defaults 1 2 /dev/hda8 /usr ext2 defaults 1 2 /dev/hda9 /opt ext2 defaults 1 2 /dev/hda6 /home ext2 defaults 1 2 /dev/hda3 /boot ext2 defaults 1 2 /dev/scd0 /cdrom auto ro,noauto,user,exec 0 0 /dev/scd1 /cdrom1 auto ro,noauto,user,exec 0 0 /dev/fd0 /floppy auto noauto,user 0 0 proc /proc proc defaults 0 0 Anders Johansson wrote:
If you can log in to the system, you could do a mount -o remount,rw / Then you can edit the files that cause this mayhem
It would also be interesting to see what you've done with /etc/fstab to get this way
Regards Anders
On Monday 25 June 2001 02:55, dizzy wrote:
Well I finally hosed my machine. In an effort to sync up my clock I rebooted the Linux server (after uptime of 40 days) When it boots I get an error to the effect the file system is read only.
This is probably due to the fact that I made an entry in /etc/passwd for a samba user like
WIN2KMACHINENAME$:*1000:900:WIN2KUSERNAME:/dev/null:dev/null
I would occasionally get errors about the /dev/null but thought I would fix it later. Unfortunately, I rebooted and now cannot make changes to the system.
I can log on and telnet in but... cannot change the /etc/passwd
could someone be kind enough to walk me through this?
I know Ill have to boot into rescue mode (cd rom is not bootable) but don't have any experience as what to "fix"
the boot message file in its entirety is at http://www.connix.com/~dizzy73/badboot.html
many thanks in advance ( I gotta get this fixed asap)
rob
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- Linux Off Topic Discussion Send a blank email to mailto:lx-talk-subscribe@big7.net
OK, so your system is already rw. Then why couldn't you edit /etc/passwd (and I don't think this is the source of your problems, btw). Looking at the boot messages, your system starts by mounting your root system read-only, which is normal. Then when it tries to fsck it, it doesn't for some reason. I honestly can't tell the difference between your system and mine. I was certain you had done something with fstab, like setting the last parameter on / to 0 or something. The only thing I can think of is a manual fsck fsck /dev/hda2 followed by a reboot. Try it, and report the results Regards Anders On Monday 25 June 2001 03:18, dizzy wrote:
IM not exactly sure of the command you gave mount -o remount,rw /
If I do mount I get
/dev/hda2 on / type ext3 (rw) proc on /proc type proc (rw)
What exactly do I need to do????
my fstab ########### /etc/fstab################# /dev/hda5 swap swap defaults 0 0 /dev/hda2 / ext2 defaults 1 1 /dev/hda7 /var ext2 defaults 1 2 /dev/hda8 /usr ext2 defaults 1 2 /dev/hda9 /opt ext2 defaults 1 2 /dev/hda6 /home ext2 defaults 1 2 /dev/hda3 /boot ext2 defaults 1 2
/dev/scd0 /cdrom auto ro,noauto,user,exec 0 0 /dev/scd1 /cdrom1 auto ro,noauto,user,exec 0 0 /dev/fd0 /floppy auto noauto,user 0 0
proc /proc proc defaults 0 0
Anders Johansson wrote:
If you can log in to the system, you could do a mount -o remount,rw / Then you can edit the files that cause this mayhem
It would also be interesting to see what you've done with /etc/fstab to get this way
Regards Anders
On Monday 25 June 2001 02:55, dizzy wrote:
Well I finally hosed my machine. In an effort to sync up my clock I rebooted the Linux server (after uptime of 40 days) When it boots I get an error to the effect the file system is read only.
This is probably due to the fact that I made an entry in /etc/passwd for a samba user like
WIN2KMACHINENAME$:*1000:900:WIN2KUSERNAME:/dev/null:dev/null
I would occasionally get errors about the /dev/null but thought I would fix it later. Unfortunately, I rebooted and now cannot make changes to the system.
I can log on and telnet in but... cannot change the /etc/passwd
could someone be kind enough to walk me through this?
I know Ill have to boot into rescue mode (cd rom is not bootable) but don't have any experience as what to "fix"
the boot message file in its entirety is at http://www.connix.com/~dizzy73/badboot.html
many thanks in advance ( I gotta get this fixed asap)
rob
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Anders Johansson wrote:
OK, so your system is already rw. Then why couldn't you edit /etc/passwd (and I don't think this is the source of your problems, btw).
rite... but *somehow* the /dev/null got passed to the bash profile...(or users logon) The only way I think this could have happened is when I made the entry in /etc/passwd for the samba user....
Looking at the boot messages, your system starts by mounting your root system read-only, which is normal. Then when it tries to fsck it, it doesn't for some reason.
I honestly can't tell the difference between your system and mine. I was certain you had done something with fstab, like setting the last parameter on / to 0 or something.
The only thing I can think of is a manual fsck
fsck /dev/hda2
followed by a reboot. Try it, and report the results
Ok fsck wont run if in the current ro state ERROR couldnt open /dev/null If I mount the fs then try to rn fsck I get the stern warning of WARNING!!! running fsck on a mounted filesystem can cause serious damage do u want to continue y/n not sure if this is safe?? rob
The safest thing would be to boot the rescue system, and run fsck from there. But if you telinit S, and make sure no processes are running, it should be fine. Anders On Monday 25 June 2001 03:44, dizzy wrote:
Anders Johansson wrote:
OK, so your system is already rw. Then why couldn't you edit /etc/passwd (and I don't think this is the source of your problems, btw).
rite... but *somehow* the /dev/null got passed to the bash profile...(or users logon) The only way I think this could have happened is when I made the entry in /etc/passwd for the samba user....
Looking at the boot messages, your system starts by mounting your root system read-only, which is normal. Then when it tries to fsck it, it doesn't for some reason.
I honestly can't tell the difference between your system and mine. I was certain you had done something with fstab, like setting the last parameter on / to 0 or something.
The only thing I can think of is a manual fsck
fsck /dev/hda2
followed by a reboot. Try it, and report the results
Ok fsck wont run if in the current ro state ERROR couldnt open /dev/null
If I mount the fs then try to rn fsck I get the stern warning of
WARNING!!! running fsck on a mounted filesystem can cause serious damage do u want to continue y/n
not sure if this is safe??
rob
On Monday 25 June 2001 03:44, dizzy wrote:
rite... but *somehow* the /dev/null got passed to the bash profile...(or users logon) The only way I think this could have happened is when I made the entry in /etc/passwd for the samba user....
btw, I think the reason for all those errors is that a lot of scripts does redirection to /dev/null, to throw away their output. Anders
Well, Im still hosed Ive lent out my 7.1 disks this weekend I donated my 6.4 I only have 5.3 I have a boot disk for 7.1 but not sure how to use it. It seenms to be looking for a cd... I tried to use the 5.3 cd but the install says "cant find the image" If I point it to the floppy it says remove the floppy ... then hangs with just a blinking cursor How exactly should I use the boot floppy from 7.1 The manual is lent out to a freind as well so he could try SuSe Ive tried typing rescu at the prompt... "cant find rescue image" I can telnet to the machine and get any file.... Will fsck *fix* the filesystem?? any ideas?? rob Anders Johansson wrote:
On Monday 25 June 2001 03:44, dizzy wrote:
rite... but *somehow* the /dev/null got passed to the bash profile...(or users logon) The only way I think this could have happened is when I made the entry in /etc/passwd for the samba user....
btw, I think the reason for all those errors is that a lot of scripts does redirection to /dev/null, to throw away their output.
Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Ok I made the rescue disk from the 5.3 cd booted into Yomama:> ran fsck -y /dev/hda2 it ran in just a few seconds. said the filesystem was clean This has no effect. It seems that the system cant write to /dev/null if I echo hello > /dev/null bash: /dev/null: readonly filesystem ls -lag /dev/null|grep null -rw-rw-rw- 1 root root 0 Jun24 2001 null Is this correct? what should it be?? this seems to be where the problem starts <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices <4> Vendor: CD-ROM Model: Drive/F5A Rev: B1.4 <4> Type: CD-ROM ANSI SCSI revision: 02 <4>Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 <4>sr0: scsi3-mmc drive: 0x/48x cd/rw xa/form2 cdda tray <6>Uniform CD-ROM driver Revision: 3.12 Kernel logging (ksyslog) stopped. Kernel log daemon terminating. Boot logging started at Sun Jun 24 23:27:04 2001 Activating swap-devices in /etc/fstab... /etc/init.d/boot: /dev/null: Read-only file system failed /etc/init.d/boot: /dev/null: Read-only file system *** ERROR! Cannot fsck because root is not read-only! also the full boot.msg file is at http://www.connix.com/~dizzy73/badboot.html I really need some suggestions.... eeeeeeeeehhhhhhh rob
On Monday 25 June 2001 06:25, dizzy wrote:
Ok I made the rescue disk from the 5.3 cd booted into Yomama:> ran fsck -y /dev/hda2 it ran in just a few seconds. said the filesystem was clean
This has no effect. It seems that the system cant write to /dev/null
if I echo hello > /dev/null bash: /dev/null: readonly filesystem
ls -lag /dev/null|grep null -rw-rw-rw- 1 root root 0 Jun24 2001 null
Is this correct?
No it is not correct. /dev/null should be a character special device with major number 1 and minor number 3 rm /dev/null mknod /dev/null c 1 3
what should it be??
this seems to be where the problem starts
<4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices <4> Vendor: CD-ROM Model: Drive/F5A Rev: B1.4 <4> Type: CD-ROM ANSI SCSI revision: 02 <4>Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 <4>sr0: scsi3-mmc drive: 0x/48x cd/rw xa/form2 cdda tray <6>Uniform CD-ROM driver Revision: 3.12 Kernel logging (ksyslog) stopped. Kernel log daemon terminating. Boot logging started at Sun Jun 24 23:27:04 2001 Activating swap-devices in /etc/fstab... /etc/init.d/boot: /dev/null: Read-only file system failed /etc/init.d/boot: /dev/null: Read-only file system
*** ERROR! Cannot fsck because root is not read-only!
also the full boot.msg file is at http://www.connix.com/~dizzy73/badboot.html
I really need some suggestions....
eeeeeeeeehhhhhhh
rob
Is this correct?
No it is not correct. /dev/null should be a character special device with major number 1 and minor number 3
rm /dev/null mknod /dev/null c 1 3
BINGO!!!! that was the problem. Thank you very much. How my /dev/null got out of line I dont know, but that fixed it. System booted, performed fscks along the way. No errors! thank you kind sir! rob
continuing weirdness here When the machine booted I logged in as root and diddnt have any special message. But if I telnet to it (as a non root user) I get bash: /dev/null: permission denied bash: /dev/null: permission denied This however dosnt cause a problem. Ill su to root then echo hello > /dev/null no problem but this is the same behaviour I was seeing before I rebooted and the /dev/null got corrupt I administer this machine via telnet because its in the basement in a utility room. Sometime Ill leave a telnet session open for days. Does anyone see a problem with that? any ideas where or why /dev/null is getting passed to a normal logon and what I can do to fix it? after running the mknod /dev/null c 1 3 ls -lag /dev/null crw-r--r-- 1 root root 1, 3 jun 24 2001 /dev/null any help to fix this is greatly appreciated! rob dizzy wrote:
Is this correct?
No it is not correct. /dev/null should be a character special device with major number 1 and minor number 3
rm /dev/null mknod /dev/null c 1 3
BINGO!!!!
that was the problem. Thank you very much. How my /dev/null got out of line I dont know, but that fixed it. System booted, performed fscks along the way. No errors!
thank you kind sir!
From dizzy to suse about Re: [SLE] Hosed file system read only!! NEED ADVISE!!:
continuing weirdness here
When the machine booted I logged in as root and diddnt have any special message.
But if I telnet to it (as a non root user) I get
bash: /dev/null: permission denied bash: /dev/null: permission denied
This however dosnt cause a problem. Ill su to root then echo hello > /dev/null no problem but this is the same behaviour I was seeing before I rebooted and the /dev/null got corrupt
I administer this machine via telnet because its in the basement in a utility room. Sometime Ill leave a telnet session open for days. Does anyone see a problem with that? You better use ssh instead of telnet. That way, your passwords don't go in clear text over the network. Of course it depends on how trusted your network is.
any ideas where or why /dev/null is getting passed to a normal logon and what I can do to fix it?
after running the mknod /dev/null c 1 3
ls -lag /dev/null
crw-r--r-- 1 root root 1, 3 jun 24 2001 /dev/null
/dev/null should be writable for everybody. chmod go+w mlehr #is the command you want
any help to fix this is greatly appreciated!
rob
dizzy wrote:
Is this correct?
No it is not correct. /dev/null should be a character special device with major number 1 and minor number 3
rm /dev/null mknod /dev/null c 1 3
BINGO!!!!
that was the problem. Thank you very much. How my /dev/null got out of line I dont know, but that fixed it. System booted, performed fscks along the way. No errors!
thank you kind sir!
-- dieter
Great! that did it! ls -lag /dev/null crw-rw-rw- 1 root root 1, 3 Jun 24 21:09 /dev/null logout and back in... no message! How /dev/null got changed.. I have no idea my network is private (behind a nat firewall) so I just use telnet also i diddnt get this chmod go+w mlehr #is the command you want so I took the simpler way of chmod 666 /dev/null thanks to everyone for the help! rob
# fsck -y / # mount -o remount,rw / -tosi Þann mánudagur 25 júní 2001 00:55 skrifaðir þú:
Well I finally hosed my machine. In an effort to sync up my clock I rebooted the Linux server (after uptime of 40 days) When it boots I get an error to the effect the file system is read only.
This is probably due to the fact that I made an entry in /etc/passwd for a samba user like
WIN2KMACHINENAME$:*1000:900:WIN2KUSERNAME:/dev/null:dev/null
I would occasionally get errors about the /dev/null but thought I would fix it later. Unfortunately, I rebooted and now cannot make changes to the system.
I can log on and telnet in but... cannot change the /etc/passwd
could someone be kind enough to walk me through this?
I know Ill have to boot into rescue mode (cd rom is not bootable) but don't have any experience as what to "fix"
the boot message file in its entirety is at http://www.connix.com/~dizzy73/badboot.html
many thanks in advance ( I gotta get this fixed asap)
rob
Tor Sigurdsson wrote:
# fsck -y /
I get ERROR could not open /dev/null (read only file system) /dev/hda2: clean bla/bla file bla/bla blocks
# mount -o remount,rw /
Ok that worked I removed the offending line in /etc/passwd somehow the /dev/null got passed on the the /init.d/SXX scripts!!! when I log into the system I get /dev/null :read only file system The system still boots to ro as far as passing the ro to the kernel that has to do with the cdrom drives and is not causing the problem. eeehhhhhhhhhh rob
-tosi
Þann mánudagur 25 júní 2001 00:55 skrifaðir þú:
Well I finally hosed my machine. In an effort to sync up my clock I rebooted the Linux server (after uptime of 40 days) When it boots I get an error to the effect the file system is read only.
This is probably due to the fact that I made an entry in /etc/passwd for a samba user like
WIN2KMACHINENAME$:*1000:900:WIN2KUSERNAME:/dev/null:dev/null
I would occasionally get errors about the /dev/null but thought I would fix it later. Unfortunately, I rebooted and now cannot make changes to the system.
I can log on and telnet in but... cannot change the /etc/passwd
could someone be kind enough to walk me through this?
I know Ill have to boot into rescue mode (cd rom is not bootable) but don't have any experience as what to "fix"
the boot message file in its entirety is at http://www.connix.com/~dizzy73/badboot.html
many thanks in advance ( I gotta get this fixed asap)
rob
-- Linux Off Topic Discussion Send a blank email to mailto:lx-talk-subscribe@big7.net
dizzy wrote:
Well I finally hosed my machine. In an effort to sync up my clock I rebooted the Linux server (after uptime of 40 days) When it boots I get an error to the effect the file system is read only.
This is probably due to the fact that I made an entry in /etc/passwd for a samba user like
WIN2KMACHINENAME$:*1000:900:WIN2KUSERNAME:/dev/null:dev/null
I don't believe that has anything to do with it.
I can log on and telnet in but... cannot change the /etc/passwd
Try telneting in and taking out the ro on your kernal command line (I would assume in /etc/lilo.conf. Then, rerun lilo and reboot.
the boot message file in its entirety is at http://www.connix.com/~dizzy73/badboot.html
I don't believe the ro should be in the kernel command line. Try it and let us know. ;) -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris "All I have seen teaches me to trust the Creator for all I have not seen." --Ralph Waldo Emerson
participants (5)
-
Anders Johansson -
dieter -
dizzy -
Joe & Sesil Morris -
Tor Sigurdsson