Hi,
When I booted my PC this morning it would not start XWindows. Looking more closely at the boot messages I can see, the following errors mingled in amongst the normal messages:
/etc/init.d/rcS: line 9: /dev/null: Read-only filesystem /etc/init.d/rcS: line 28: /dev/null: Read-only filesystem ERROR: Could not open /dev/null (Read-Only file system) Setting up IP spoofing protection: FAILED Configuring network interfaces... modprobe: Can't locate module net-pf-11 modprobe: modprobe: Can't locate module net-pf-18 modprobe: modprobe: Can't locate module net-pf-9 modprobe: modprobe: Can't locate module net-pf-11 modprobe: modprobe: Can't locate module net-pf-18 modprobe: modprobe: Can't locate module net-pf-9 SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device SIOCSFBRDADDR: No such device Starting portmap daemon. portmapstart-stop-daemon: nothing in /proc - not mounted? grep: /proc/filesystems: No such file or directory. Starting system log daemon:syslogstart-stop-daemon: nothing in /proc - not mounted? Starting system log daemon:syslogstart-stop-daemon: nothing in /proc - not mounted? Starting mail transport agent: smailstart-stop-daemon:....
When I ran fsck it immediately came back saying the disks had been unmounted cleanly so no check was made.
I then tried running e2fsck with the "force check" option and have supposedly fixed all the errors it found but the above errors are still mingled in with the other boot messages when I reboot.
If I look in /dev I can see null as -rw-r--r-- If I look in / I can see /proc as dr-xr-xr-x
Question: Can the above errors be fixed manually or is it reinstall time?
I am running Knoppix 3.1 (installed on my hard disk rather than running off a CD)
Ian.
Ian Douglas wrote;
When I booted my PC this morning it would not start XWindows. Looking more closely at the boot messages I can see, the following errors mingled in amongst the normal messages:
/etc/init.d/rcS: line 9: /dev/null: Read-only filesystem /etc/init.d/rcS: line 28: /dev/null: Read-only filesystem ERROR: Could not open /dev/null (Read-Only file system)
...[snipo]...
If I look in /dev I can see null as -rw-r--r-- If I look in / I can see /proc as dr-xr-xr-x
...[snipo]...
I am running Knoppix 3.1 (installed on my hard disk rather than running off a CD)
Hmm... could it be a permissions problem? are all your groups set up correctly and is your user a member?
Or, because the CDROM filesystem is read only the read only permissions might have been transferred when copied on your disk. Similar to when you copy files from a CD in Windoze all the files have the read flag set. What command did you use to copy the CD files to the HD? With luck 'The Wise Ones' who frequent this list will let us know what you need to do to circumvent this ('cause I don't :o) ).
Keith ____________ A ship in the harbour is safe... but that's not what ships were made for.
On Wednesday, February 12, 2003 3:27 PM, Keith Watson wrote:
Ian Douglas wrote: ...[snipo]...
I am running Knoppix 3.1 (installed on my hard disk rather than running off a CD)
Hmm... could it be a permissions problem? are all your groups set up correctly and is your user a member?
Or, because the CDROM filesystem is read only the read only permissions might have been transferred when copied on your disk. Similar to when you copy files from a CD in Windoze all the files have the read flag set. What command did you use to copy the CD files to the HD? With luck 'The Wise Ones' who frequent this list will let us know what you need to do to circumvent this ('cause I don't :o) ).
Thanks for your suggestions Keith. I think though perhaps my last message wasn't very clear. My problem is not with installing Knoppix; I installed it onto my hard disk (using the knx-install command) a couple of months ago and have been using it happily every day since. My problem is rather that I noticed XWindows (or more correctly kdm?) would not start when I booted it as normal this morning, then, on checking /var/adm/messages I discovered all the error messages I mentioned in my last posting. It worked ok yesterday, these errors only appeared this morning. I am wondering if these errors are easy to fix, or whether it would be simplest to just reinstall.
Sorry for any confusion folks!
Ian.
On 12-Feb-2003 Ian Douglas wrote:
Hi,
When I booted my PC this morning it would not start XWindows. Looking more closely at the boot messages I can see, the following errors mingled in amongst the normal messages:
/etc/init.d/rcS: line 9: /dev/null: Read-only filesystem /etc/init.d/rcS: line 28: /dev/null: Read-only filesystem ERROR: Could not open /dev/null (Read-Only file system)
The 3 lines, above, indicate that something went wrong with your disk at boot time. It may have been a temporary glitch or something more serious. All the other errors are cosnequences of that one original one.
So ,check the seating of all your cables; run badblocks; run fsck. And lastly ensure you have good backups - and don't forget to say your prayers.
Setting up IP spoofing protection: FAILED Configuring network interfaces... modprobe: Can't locate module net-pf-11 modprobe: modprobe: Can't locate module net-pf-18 modprobe: modprobe: Can't locate module net-pf-9 modprobe: modprobe: Can't locate module net-pf-11 modprobe: modprobe: Can't locate module net-pf-18 modprobe: modprobe: Can't locate module net-pf-9 SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device SIOCSFBRDADDR: No such device Starting portmap daemon. portmapstart-stop-daemon: nothing in /proc - not mounted? grep: /proc/filesystems: No such file or directory. Starting system log daemon:syslogstart-stop-daemon: nothing in /proc - not mounted? Starting system log daemon:syslogstart-stop-daemon: nothing in /proc - not mounted? Starting mail transport agent: smailstart-stop-daemon:....
When I ran fsck it immediately came back saying the disks had been unmounted cleanly so no check was made.
I then tried running e2fsck with the "force check" option and have supposedly fixed all the errors it found but the above errors are still mingled in with the other boot messages when I reboot.
If I look in /dev I can see null as -rw-r--r-- If I look in / I can see /proc as dr-xr-xr-x
Question: Can the above errors be fixed manually or is it reinstall time?
I am running Knoppix 3.1 (installed on my hard disk rather than running off a CD)
Ian.
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
-
Ian Douglas -
Keith Watson -
raph＠panache.demon.co.uk