Can't rescue, read-only filesystem
Morgan Fletcher
let apt-get remove the 102 packages it recently wants to remove.
I believe I saw lilo get updated this weekend, during 'apt-get update
&& apt-get upgrade'. This morning I rebooted and got "LI". (Lilo
normally let's me boot into win2k or debian "testing".)
I pulled out an old potato-era rescue disk, entered "rescue
root=/dev/hda3" at the "rescue:" prompt and everything went okay until
it got stuck in an endless loop, repeating the same messages over and
over:
insmod: /lib/modules/2.2.17/misc/unix.o: insmod net-pf-1 failed
insmod: /lib/modules/2.2.17/misc/unix.o: cannot create /var/log/ksymoops/200010319 Read-only file system
I don't know what's going on. Advice?
morgan
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
kms...@ix.netcom.com
--jL2BoiuKMElzg3CS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
on Mon, Mar 19, 2001 at 10:33:21AM -0800, Morgan Fletcher (mor...@hahaha.or=
g) wrote:
> I am running "testing", my system is up-to-date, except that I haven't
> let apt-get remove the 102 packages it recently wants to remove.
>=20
> I believe I saw lilo get updated this weekend, during 'apt-get update
> && apt-get upgrade'. This morning I rebooted and got "LI". (Lilo
> normally let's me boot into win2k or debian "testing".)
>=20
> I pulled out an old potato-era rescue disk, entered "rescue
> root=3D/dev/hda3" at the "rescue:" prompt and everything went okay until
> it got stuck in an endless loop, repeating the same messages over and
> over:
>=20
> insmod: /lib/modules/2.2.17/misc/unix.o: insmod net-pf-1 failed
> insmod: /lib/modules/2.2.17/misc/unix.o: cannot create /var/log/ksymoop=
s/200010319 Read-only file system
>=20
> I don't know what's going on. Advice?
Boot a standalone floppy or CDR GNU/Linux system and examine your HD.
I'd recommend Tom's Root Boot if you're running a 2.1.x kernel (TRB
doesn't handle some instances of 2.2.x ext2 filesystems), or the
LinuxCare Bootable Business Card (BBC), which uses a 2.2.x kernel.
I suspect HD damage, which may prevent you from accessing your HD and/or
a Linux kernel located on it.
--=20
Karsten M. Self <kms...@ix.netcom.com> http://kmself.home.netcom.com/
What part of "Gestalt" don't you understand? There is no K5 cabal
http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org
--jL2BoiuKMElzg3CS
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6tnqTOEeIn1XyubARAuylAJ9Uva3ANvy4y6h+UW0jzPFWBUGKLgCfewA7
6Q7BsfDLrMpgJIZKOyD/bQ8=
=wsAL
-----END PGP SIGNATURE-----
--jL2BoiuKMElzg3CS--
Morgan Fletcher
> Boot a standalone floppy or CDR GNU/Linux system and examine your HD.
> I'd recommend Tom's Root Boot if you're running a 2.1.x kernel (TRB
> doesn't handle some instances of 2.2.x ext2 filesystems), or the
> LinuxCare Bootable Business Card (BBC), which uses a 2.2.x kernel.
>
> I suspect HD damage, which may prevent you from accessing your HD and/or
> a Linux kernel located on it.
Wouldn't HD damage affect execution before the reboot? System has been
up all through the weekend, and I had rebooted and gone through LILO
four days ago.
I think it has something to do with the way the rescue disk is
starting the system. Not sure, however.
The boot sequence goes quite a way, until it gets to loading this
module. I'm inclined to think the disk is OK.
morgan
Oliver Elphick
>I am running "testing", my system is up-to-date, except that I haven't
>let apt-get remove the 102 packages it recently wants to remove.
>
>&& apt-get upgrade'. This morning I rebooted and got "LI". (Lilo
>normally let's me boot into win2k or debian "testing".)
>
>it got stuck in an endless loop, repeating the same messages over and
>over:
>
>00010319 Read-only file system
>
>I don't know what's going on. Advice?
The root partition is mounted read-only to start with. You need to
load a kernel module to finish booting, but it looks as though the rescue kernel
doesn't match the modules on your hard disk.
It looks as if you may have overwritten your kernel-image package. The
LI message means that lilo couldn't find the kernel where it is configured
to look for it.
If that is correct, the simplest way to deal with it is:
Boot from the floppy:
boot: rescue root=/dev/hda3 init=/bin/sh
This will put you straight into a shell, with no other utilities running.
# /sbin/lilo
This should reinstall lilo so that you can boot from the hard disk.
Then:
# sync
# reboot
--
Oliver Elphick Oliver....@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
" And God shall wipe away all tears from their eyes;
and there shall be no more death, neither sorrow, nor
crying, neither shall there be any more pain: for the
former things are passed away."
Revelations 21:4
kms...@ix.netcom.com
--juZjCTNxrMaZdGZC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
on Mon, Mar 19, 2001 at 01:47:55PM -0800, Morgan Fletcher (mor...@hahaha.or=
g) wrote:
> kms...@ix.netcom.com writes:
> > Boot a standalone floppy or CDR GNU/Linux system and examine your HD.
> > I'd recommend Tom's Root Boot if you're running a 2.1.x kernel (TRB
> > doesn't handle some instances of 2.2.x ext2 filesystems), or the
> > LinuxCare Bootable Business Card (BBC), which uses a 2.2.x kernel.
> >=20
> > I suspect HD damage, which may prevent you from accessing your HD and/or
> > a Linux kernel located on it.
>=20
> Wouldn't HD damage affect execution before the reboot? System has been
> up all through the weekend, and I had rebooted and gone through LILO
> four days ago.=20
>=20
> I think it has something to do with the way the rescue disk is
> starting the system. Not sure, however.
>=20
> The boot sequence goes quite a way, until it gets to loading this
> module. I'm inclined to think the disk is OK.
If you're unable to boot the system from onboard images, booting from an
external image is recommended. Simple fact is that if you cannot boot
the system you have no way of determining whether or not the HD is
trashed or not.
Boot a rescue disk (again, BBS, TRB, or similar), and sniff around.
--=20
Karsten M. Self <kms...@ix.netcom.com> http://kmself.home.netcom.com/
What part of "Gestalt" don't you understand? There is no K5 cabal
http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org
--juZjCTNxrMaZdGZC
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6tpF7OEeIn1XyubARAoSPAJ9YAj1s4DQb/B79mAJWq8vKjXx4+gCeI/ly
C+qSUmvFxHc5xYI7Aj/eDiY=
=fkwI
-----END PGP SIGNATURE-----
--juZjCTNxrMaZdGZC--
Morgan Fletcher
> The root partition is mounted read-only to start with. You need to
> load a kernel module to finish booting, but it looks as though the
> rescue kernel doesn't match the modules on your hard disk.
>
> It looks as if you may have overwritten your kernel-image package. The
> LI message means that lilo couldn't find the kernel where it is configured
> to look for it.
>
> If that is correct, the simplest way to deal with it is:
>
> Boot from the floppy:
>
> boot: rescue root=/dev/hda3 init=/bin/sh
>
> This will put you straight into a shell, with no other utilities running.
Unfortunately, the same thing happens. It is as if the init=/bin/sh
argument is ignored. The rescue disk is from potato. My wife's laptop
doesn't have a floppy drive, so I can't even create a new one! Worse
still, I can't even use windows 2000's CD to "rescue" the MB, so I am
stuck with "LI" and can't boot either OS on the machine.
Argh.
I used the rescue->root disks from 2.2 to mount my partitions. I tried
using ae to uncomment the "alias net-pf-1 off" line, then touch
modules.dep to be newer than modules.conf, but I still can't get past
the basic problem of an endlessly-cycling error message on boot, right
when init is launched it looks like:
modprobe: modprobe: cannot create /var/log/ksymoops/20010320.log Read-only file system
Over and over.
The disk is fine, as I can mount its partitions from the instllation
screen, traverse its structure, manipulate files. I just can't get
linux (or LILO) to boot. I don't know what to do next. Any advice?
morgan
David Wright
> I used the rescue->root disks from 2.2 to mount my partitions. I tried
> using ae to uncomment the "alias net-pf-1 off" line, then touch
> modules.dep to be newer than modules.conf, but I still can't get past
> the basic problem of an endlessly-cycling error message on boot, right
> when init is launched it looks like:
>
> modprobe: modprobe: cannot create /var/log/ksymoops/20010320.log Read-only file system
>
> Over and over.
>
> The disk is fine, as I can mount its partitions from the instllation
> screen, traverse its structure, manipulate files. I just can't get
> linux (or LILO) to boot. I don't know what to do next. Any advice?
I'm not sure why this problem is a show-stopper. Several installation
kernels were built without the unix.o module which is kind of
unfortunate. But this normally is just a hiccup, e.g.
Linux version 2.2.15 (herbert@gondor) (gcc version 2.95.2 20000313 (Debian GNU/Linux)) #1 Tue Apr 25 17:13:48 EST 2000
...
INIT: version 2.78 booting
NET4: Unix domain sockets 1.0 for Linux NET4.0.
insmod: /lib/modules/2.2.15/misc/unix.o: cannot create /var/log/ksymoops/2000072
3232449.ksyms Read-only file system
Loading /etc/console-tools/default.kmap.gz
Activating swap...
Adding Swap: 32220k swap-space (priority -1)
Checking root file system...
Parallelizing fsck version 1.18 (11-Nov-1999)
/dev/hda7: clean, 29337/106400 files, 86748/212680 blocks
This one was just the same:
Linux version 2.2.14 (herbert@gondor) (gcc version 2.95.2 19991103 (Debian GNU/Linux)) #1 Sun Jan 16 13:48:57 EST 2000
Perhaps the problem is that unix.o is found above, whereas it isn't
found in your /dev/hda3 because you built it in.
I guess you just need to copy a kernel like your hard disk one (which
contains unix.o as built-in) onto a (copy of a) rescue disk. It should
easily fit as installation kernels are so bloated. Then you can work
on fixing lilo.
Cheers,
--
Email: d.wr...@open.ac.uk Tel: +44 1908 653 739 Fax: +44 1908 655 151
Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA
Disclaimer: These addresses are only for reaching me, and do not signify
official stationery. Views expressed here are either my own or plagiarised.
Oliver Elphick
># sbin/lilo -r /target
>sbin/lilo: /sbin/lilo.real: not found
># sbin/lilo.real -r /target
>sbin/lilo.real: error in loading shared libraries: sbin/lilo.real: symbol fs
>tatfs, version GLIBC_2.0 not defined in file libc.so.6 with link time re
>ference
Next step
# LD_LIBRARY_PATH=/target/lib sbin/lilo.real -r /target
>Today at work I will get new rescue/root disks. Is there a
>woody/testing set, or should I use the stable set?
All you need is a kernel that will boot long enough to let you run lilo, if
the above doesn't work.
--
Oliver Elphick Oliver....@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"I am crucified with Christ; nevertheless I live; yet
not I, but Christ liveth in me; and the life which I
now live in the flesh I live by the faith of the Son
of God, who loved me, and gave himself for me."
Galatians 2:20