You are not logged in.

#1 2007-01-23 18:53:57

2eleven
Member
Registered: 2007-01-23
Posts: 6

Revert back to mkinitrd? [SOLVED]

Hi Folks,

I decided last night to do a pacman -Syu on my 0.7.1 system since I felt like I was falling behind. I did my homework and I think I have properly set up mkinitcpio and grub for my raid (which I boot from). I set up the boot-from-raid system per the howto here:

http://wiki.archlinux.org/index.php/Ins … AID_or_LVM

And have run into the problems that these people are having here:

http://bbs.archlinux.org/viewtopic.php?t=28367

My system boots properly about once every 5 times. Every other time, it produces this:

:: Running Hook [raid]
md: Will configumd: bind<sda2>
re md1 (super-blmd: bind<sdb2>
ock) from /dev/smd: bind<sdc2>
da2,/dev/sdb2,/dmd: bind<sdd2>
ev/sdc2,/dev/sdd2, below.
md: Loading md1: /dev/sda2
raid5: device sdd2 operational as raid disk 3
raid5: device sdc2 operational as raid disk 1
raid5: device sdb2 operational as raid disk 2
raid5: device sda2 operational as raid disk 0
raid5: allocated 4205kB for md1
raid5: raid level 5 set md1 active with 4 out of 4 devices, algorithm 2
RAID5 conf printout:
--- rd:4 wd:4
disk 0, o:1, dev:sda2
disk 1, o:1, dev:sdc2
disk 2, o:1, dev:sdb2
disk 3, o:1, dev:sdd2
:: Running Hook [filesystems]
:: Loading root filesystem module...stdin: error 0

:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
md: Will configure md1 (super-block) from /dev/sda2,/dev/sdb2,/dev/sdc2,/dev/sdd
2, below.
kinit: Unable to mount root fs on device md1(9,1)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!


Since I depend on this system heavily, I really need to get it up and running again. My question is: Can I back out mkinitcpio and reinstall mkinitrd and live happily ever after, or should I revert back to a 0.7.1 installation? I would prefer to stay more current, but mkinitcpio is killing me.

Any recommendations are greatly appreciated! Thanks!

John

Offline

#2 2007-01-24 07:03:21

2eleven
Member
Registered: 2007-01-23
Posts: 6

Re: Revert back to mkinitrd? [SOLVED]

Well, I tried going back to mkinitrd with no luck. It would appear that it no longer works out of the box on the current system (not sure why). Does anyone know what tweaks I would need to use to get it working again? Do I need to downgrade my kernel?

Thanks again for any help.

John

Offline

#3 2007-01-24 08:08:22

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: Revert back to mkinitrd? [SOLVED]

It's odd that you get all the messages about raid working, but it just fails to actually work.

Can you append "break" to your kernel params?

This will drop you into ash... it's a nasty shell, because it's not made for interactivity.  But could you... hmmm...

echo /dev/md*
parseblock /dev/md1
fstype < /dev/md1

Things like that... I can only really help so much as I don't currently have any sort of fun raid setup.

Let me know what sort of output you get.

Offline

#4 2007-01-24 10:26:27

Asaru
Member
Registered: 2006-05-06
Posts: 14

Re: Revert back to mkinitrd? [SOLVED]

did you downgrade your kernel too?

Offline

#5 2007-01-24 17:04:59

2eleven
Member
Registered: 2007-01-23
Posts: 6

Re: Revert back to mkinitrd? [SOLVED]

Hi,

Thanks for any help you can provide. Here's the output you wanted. I also gave you /proc/mdstat:

:: Break requested, type 'exit' to resume operation
   NOTE: klibc contains no 'ls' binary, used 'echo *' instead
ramfs$ echo /dev/md*
/dev/md0 /dev/md1
ramfs$ parseblock /dev/md1
BLOCKNAME="/dev/md1"
BLOCKDEVICE="9 1"
ramfs$ fstype < /dev/md1
FSTYPE=ext3
FSSIZE=1484991627264
ramfs$ cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md1 : active raid5 sdd2[3] sdc2[1] sdb2[2] sda2[0]
      1450187136 blocks level 5, 128k chunk, algorithm 2 [4/4] [UUUU]

unused devices: <none>
ramfs$ exit
:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
Waiting 1 s before mounting root device...
md: Will configure md1 (super-block) from /dev/sda2,/dev/sdb2,/dev/sdc2,/dev/sdd
2, below.
kinit: Unable to mount root fs on device md1(9,1)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!


OK, so that time it didn't boot (as usual), but every once in a while it does, so I did this a few times to see if it was any different the time that it did. Well, there was one difference this time - I fat fingered the <and> instead on the fstype input (I was a little scared that I might have screwed the filesystem up by outputing stdout to it, but it seemed fine and it booted this time). I'm not sure if there's any correlation, but I wanted to provide as much data as I could:

:: Break requested, type 'exit' to resume operation
   NOTE: klibc contains no 'ls' binary, used 'echo *' instead
ramfs$ parseblock /dev/md1
BLOCKNAME="/dev/md1"
BLOCKDEVICE="9 1"
ramfs$ fstype >/dev/md1
stdin: Illegal seek
ramfs$ fstype < /dev/md1
FSTYPE=ext3
FSSIZE=1484991627264
ramfs$ exit
:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
Waiting 1 s before mounting root device...
md: Will configure md1 (super-block) from /dev/sda2,/dev/sdb2,/dev/sdc2,/dev/sdd
2, below.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
kinit: Mounted root (ext3 filesystem) readonly.
INIT: version 2.86 booting

> Arch Linux v0.8 (Voodoo)

> http://www.archlinux.org
> Copyright 2002-2007 Judd Vinet
> Distributed under the GNU General Public License (GPL)

   ------------------------------

:: Starting UDev Daemon    [BUSY]    [DONE]
.
.
.


Any ideas?

With regards to going back to mkinitrd, I am guessing that mkinitrd is not compatible for some reason with the current kernel? If I need to downgrade my kernel, what is the last version that worked with mkinitrd? Is there a way to downgrade with pacman? I've never used it for that and can't seem to find a way in the man page.

Thanks again everyone.

John

Offline

#6 2007-01-24 21:24:35

2eleven
Member
Registered: 2007-01-23
Posts: 6

Re: Revert back to mkinitrd? [SOLVED]

OK - I think I've solved it (at least I've rebooted about 10 times with no problems). Out of desperation, I just started experimenting with mkinitcpio.conf and I added ext3 to the MODULES list. I'm not sure why it works, but it seems to do the trick.

Hopefully this will be helpful to others with this problem. Thanks again for the help.

John

Offline

#7 2007-01-24 21:29:18

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: Revert back to mkinitrd? [SOLVED]

Errm.... odd.  Now that I look back, I should have suggested that first:

:: Running Hook [filesystems]
:: Loading root filesystem module...stdin: error 0 

Looks like 'fstype' failed to detect your filesystem type.  As a side note, a rootfstype=ext3 may do the same thing.

Offline

#8 2007-01-24 22:16:46

perg
Member
Registered: 2007-01-22
Posts: 3

Re: Revert back to mkinitrd? [SOLVED]

Putting reiserfs in the MODULE list didn't help, but rootfstype=reiserfs did it for me.
Thanks

Offline

Board footer

Powered by FluxBB