Prev: xterm vs. [m]rxvt (WAS: Re: Corporate creep in Linux?(mini-rantette))
Next: hugesmp.s and initrd.img
From: emmel on 16 Sep 2009 10:56
OK, I've managed to shoot myself in the foot. I /accidentally/ run
mkinitrd with the wrong (read: none) parameters. Problem is that I'm
running with encrypted file systems, including root.
So I though I'd boot the system with some rescue system (tried
an old Knoppix, then used a Slack 12.2 DVD lying around), and rerun
mkinitrd with the right parameters. Except that it doesn't seem to work.
The kernel panics, telling me that the VFS couldn't access the root file
system...
Call it a hunch, but that might have something to do with the
error messages mkinitrd threw at me. Something about cp not knowing the
--parents parameter, which it should according to the man page.
Any suggestions welcome. I don't really want to have to
reinstall the system or anything, but at the moment I'm fresh out of
ideas. Help?

TIA
From: gabriel on 16 Sep 2009 12:34
On Wed, 16 Sep 2009 14:56:12 +0000, emmel wrote:

> OK, I've managed to shoot myself in the foot. I /accidentally/ run
> mkinitrd with the wrong (read: none) parameters. Problem is that I'm
> running with encrypted file systems, including root.
> So I though I'd boot the system with some rescue system (tried
> an old Knoppix, then used a Slack 12.2 DVD lying around), and rerun
> mkinitrd with the right parameters. Except that it doesn't seem to work.
> The kernel panics, telling me that the VFS couldn't access the root file
> system...
> Call it a hunch, but that might have something to do with the
> error messages mkinitrd threw at me. Something about cp not knowing the
> --parents parameter, which it should according to the man page.
> Any suggestions welcome. I don't really want to have to
> reinstall the system or anything, but at the moment I'm fresh out of
> ideas. Help?
>
> TIA

I know that busybox's cp don't know the --parents option

$ cd /boot/initrd-tree/bin/
$ file cp
cp: symbolic link to `busybox'
$ ./cp --parents ~/todo ~/todo2
../cp: unrecognized option '--parents'
[...]

Can't help more than that.
From: emmel on 16 Sep 2009 13:35
Thus gabriel spoke:

> On Wed, 16 Sep 2009 14:56:12 +0000, emmel wrote:
>
>> OK, I've managed to shoot myself in the foot. I /accidentally/ run
>> mkinitrd with the wrong (read: none) parameters. Problem is that I'm
>> running with encrypted file systems, including root.
>> So I though I'd boot the system with some rescue system (tried
>> an old Knoppix, then used a Slack 12.2 DVD lying around), and rerun
>> mkinitrd with the right parameters. Except that it doesn't seem to work.
>> The kernel panics, telling me that the VFS couldn't access the root file
>> system...
>> Call it a hunch, but that might have something to do with the
>> error messages mkinitrd threw at me. Something about cp not knowing the
>> --parents parameter, which it should according to the man page.
>> Any suggestions welcome. I don't really want to have to
>> reinstall the system or anything, but at the moment I'm fresh out of
>> ideas. Help?
>>
>> TIA
>
> I know that busybox's cp don't know the --parents option
>
> $ cd /boot/initrd-tree/bin/
> $ file cp
> cp: symbolic link to `busybox'
> $ ./cp --parents ~/todo ~/todo2
> ./cp: unrecognized option '--parents'
> [...]
>
> Can't help more than that.

Yeah... I got a bit suspicious after posting and checked the cp -
busybox. Which was rather disturbing, considering that I *had* done a
chroot before. Turns out mkinitrd got the idea and built its tree in my
root, messing up a good deal of my binaries. Trying to recover since
(deleting what shouldn't be there, judging from my other slack box and
reinstalling a lot of packages). At this point I at least get into
single user mode... Something's gone wrong with the device mapper...
Hm... By the looks of it mount it missing...
From: emmel on 16 Sep 2009 13:54
Thus emmel spoke:

> Thus gabriel spoke:
>
>> On Wed, 16 Sep 2009 14:56:12 +0000, emmel wrote:
>>
>>> OK, I've managed to shoot myself in the foot. I /accidentally/ run
>>> mkinitrd with the wrong (read: none) parameters. Problem is that I'm
>>> running with encrypted file systems, including root.
>>> So I though I'd boot the system with some rescue system (tried
>>> an old Knoppix, then used a Slack 12.2 DVD lying around), and rerun
>>> mkinitrd with the right parameters. Except that it doesn't seem to work.
>>> The kernel panics, telling me that the VFS couldn't access the root file
>>> system...
>>> Call it a hunch, but that might have something to do with the
>>> error messages mkinitrd threw at me. Something about cp not knowing the
>>> --parents parameter, which it should according to the man page.
>>> Any suggestions welcome. I don't really want to have to
>>> reinstall the system or anything, but at the moment I'm fresh out of
>>> ideas. Help?
>>>
>>> TIA
>>
>> I know that busybox's cp don't know the --parents option
>>
>> $ cd /boot/initrd-tree/bin/
>> $ file cp
>> cp: symbolic link to `busybox'
>> $ ./cp --parents ~/todo ~/todo2
>> ./cp: unrecognized option '--parents'
>> [...]
>>
>> Can't help more than that.
>
> Yeah... I got a bit suspicious after posting and checked the cp -
> busybox. Which was rather disturbing, considering that I *had* done a
> chroot before. Turns out mkinitrd got the idea and built its tree in my
> root, messing up a good deal of my binaries. Trying to recover since
> (deleting what shouldn't be there, judging from my other slack box and
> reinstalling a lot of packages). At this point I at least get into
> single user mode... Something's gone wrong with the device mapper...
> Hm... By the looks of it mount it missing...

And installpkg and two reboots later (Can't that stupid mkinitrd call
lilo for me?) it works. Seriously, that script could do some work. A
failsafe for operating in the wrong directory and automatic executing of
lilo (if used) would be no end of good. BTW, does anyone know why
cryptsetup is a link to cryptsetup.static? Wasn't there some problem
with the static version?
From: gabriel on 16 Sep 2009 15:54
> And installpkg and two reboots later (Can't that stupid mkinitrd call
> lilo for me?) it works. Seriously, that script could do some work. A
> failsafe for operating in the wrong directory and automatic executing of
> lilo (if used) would be no end of good. BTW, does anyone know why
> cryptsetup is a link to cryptsetup.static? Wasn't there some problem
> with the static version?

cryptsetup is a link to cryptsetup.dynamic here. Seems that mkinitrd
screwed that too.
I suggest you to take a big look at the mkinitrd script ...
 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: xterm vs. [m]rxvt (WAS: Re: Corporate creep in Linux?(mini-rantette))
Next: hugesmp.s and initrd.img