Skip to Content.
Sympa Menu

sm-discuss - [SM-Discuss] [sm-discuss] unable to remount root on boot (DEV run level) after yesterday's "sorcery -s".

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Javier Vasquez <j.e.vasquez.v AT gmail.com>
  • To: "sm, discuss" <sm-discuss AT lists.ibiblio.org>
  • Subject: [SM-Discuss] [sm-discuss] unable to remount root on boot (DEV run level) after yesterday's "sorcery -s".
  • Date: Mon, 20 May 2013 07:45:29 -0600

sorcery -s brought new perl between several other things.

On a x86-64 (not sure about i686 yet given it's still running), the
machine no longer boots. It gets stuck at attempting to remount root
on the corresponding runlevel...

The only message I could get at the very end (there's an additional
*sync* stuff I have no time to read and write by hand) is:

rc: Entered run level DEV...
Ext4-fs (sda7): remounted opts: (null)

Well, null because I removed the option from /etc/fstab
errors=remount-ro. If I keep it, the message would say instead (if I
recall correctly):

rc: Entered run level DEV...
Ext4-fs (sda7): remounted opts: (ro)

I've already "cfdisk -f" sda7 (root), and all other partitions for that
matter.

Using "single" as kernel parameter (called by grub menu "recovery
mode") doesn't help either...

I performed also cleanse by chrooting in the machine through live CD.

I've re-casted some spells (through chroot from live CD) like "gettext
glibc readline util-linux e2fsprogs texinfo", and that doesn't seem to
help. Notice wget wasn't able to compile given some pod2man message
complaining about expecting text and not a number at some point...

Any hint?

--
Javier.




Archive powered by MHonArc 2.6.24.

Top of Page