Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

lilsirecho · 2011-10-05 18:55:57

Pacman _Syu today into my archlinux system caused boot error: not able to find root disk by uuid......

I suspect mkinitcpio caused the problem...possibly by looking for the grub data in MBR whereas it is located in /boot partition of the uuid.

The system has been booting well for weeks with the linux kernel versions including other updates.

Any help with this problem is welcome!!!

EDIT: GRUB 2 in use!

Last edited by lilsirecho (2011-10-29 03:22:24)

klerik · 2011-10-05 19:15:42

I have same problem

graysky · 2011-10-05 19:24:22

Using 3.0.6 of linux-ck here and no issues. True for 6 systems.

Last edited by graysky (2011-10-05 19:24:33)

idjut · 2011-10-05 23:27:14

I have similar problem, or it might just be the same one. While booting the screen goes black as if some X is starting, but then it freezes so I`m not sure what is the last error message. The last thing I read is ioremap error..

the sad clown · 2011-10-05 23:58:52

http://www.archlinux.org/news/changes-t … filenames/

Have you updated your bootloader configuration?

lilsirecho · 2011-10-06 01:03:08

Mounted the system and find no entries in /boot and no entries in /dev/.....

System has booted for weeks in linux kernel................and upgrades...........

Last edited by lilsirecho (2011-10-06 01:03:32)

the sad clown · 2011-10-06 01:29:25

There is nothing in /boot? Maybe you could try this:

https://wiki.archlinux.org/index.php/GR … onfig_file

khsurati · 2011-10-06 01:41:16

My system is also having a issue after an attempted linux-3.0.6-1 update. Earlier today, I ran 'pacman -Syu' but it failed telling me some linux kernel upgrade file was corrupted so 'nothing was installed'. I did a restart a little while ago, and now I can't boot into Arch. I am stuck in an infinite loop. Boot up makes it up to where you select Arch in grub menu, but as soon as I make a selection it restarts the PC. Fallback option also produces the same result.

I tried changing the boot option at grub menu to "kernel26-fallback.img" as I still have that in the /boot directory. Unfortunately, that made no difference. Any suggestions?

Thanks.

the sad clown · 2011-10-06 01:57:27

Have you tried to chroot with a live arch cd and use pacman to repair your system?

https://wiki.archlinux.org/index.php/Change_Root

lilsirecho · 2011-10-06 02:20:03

The Sad Clown;

Read the posted reference and find it to be complete chaos for arch KISS since grub normally is a breeze!

My system was installed via FTP as a raid0 with 5 CF cards as /md0. /Md0 is 79MB and has performed for weeks in Linux.

I installed grub2 during the FTP install and have /boot and /root partitions. Boot is on partition (100MB) one of one of the five CF cards and all 5 cards are partitioned the same each partition#2 being the rest of the CF card (16MB) as /root ....(md0).

I will post the boot option window data shortly....

khsurati · 2011-10-06 02:38:37

the sad clown wrote:

Have you tried to chroot with a live arch cd and use pacman to repair your system?
https://wiki.archlinux.org/index.php/Change_Root

No I haven't, but I will when I get a chance (away from home until next week). Thanks for the suggestion.

lilsirecho · 2011-10-06 02:43:49

The following has been in force for linux kernel versions since the first appearance on archlinux upgrades..........

set params "Arch Linux"
set root=(hd0,1)
linux /vmlinuz26 root=/dev/disk/by_uuid/6a4f98=666-9f07-4792-b4cb-94033b21526f9 rootfstype= ext3 ro
initrd /kernel26.img

Uname -a during the boots prior to todays upgrade show linux as the kernel installed.

What format is required for RAID 0 systems and can this grub be corrected without chroot?

Trying to make sense of the grub2 wiki is a minefield!!!

the sad clown · 2011-10-06 02:45:01

lilsirecho wrote:

The Sad Clown;
Read the posted reference and find it to be complete chaos for arch KISS since grub normally is a breeze!

Is there an easy way to fix a borked grub config? I looked over the Grub 2 entry I linked, it didn't seem that challenging to me. Probably the hardest part is just chrooting, and that's only if you aren't familiar with it. Arch can't make chroot simpler.

Last edited by the sad clown (2011-10-06 02:47:53)

the sad clown · 2011-10-06 02:46:29

lilsirecho wrote:

The following has been in force for linux kernel versions since the first appearance on archlinux upgrades..........
set params "Arch Linux"
set root=(hd0,1)
linux /vmlinuz26 root=/dev/disk/by_uuid/6a4f98=666-9f07-4792-b4cb-94033b21526f9 rootfstype= ext3 ro
initrd /kernel26.img 
Uname -a during the boots prior to todays upgrade show linux as the kernel installed.
What format is required for RAID 0 systems and can this grub be corrected without chroot?
Trying to make sense of the grub2 wiki is a minefield!!!

Not anymore. First link I posted:

http://www.archlinux.org/news/changes-t … filenames/

lilsirecho · 2011-10-06 03:05:51

The Sad Clown:

The initial changes in grub were provide by archlinux news item as you reference.

Note that these were for grub...not grub2.

To be exact, I never touched my grub2 because I had no idea on how it should be handled since it does not resemble the exact detail provided by the archlinux news data.

What do I do now? With a raid array, grub is handled differently in the grub2 wiki....

What do I do to establish it correctly in RAID0?

Each mode of operation . btrfs, dual-boot, raid, lvm, normal arch....all have different requirements.

Most instructions given in archlinux news items are abbreviated too much. Grub2 is very different from grub (old).

EDIT: Example....my present boot-up is in grub0.97. It has the required entries in menu.lst to utilize the linux kernel and initramfs. It boots correctly into linux and reports uname-a as linux kernel-3.0.

I cannot utilize the same entries in grub2 because they are not the same arrangement as grub(old).....

Further, RAID0 requires elements I may not have...dm_mod...required modules...different entries in the grub display.

What is the correct display and modules needed for RAID0 in grub2?

EDIT 2:Why wasn't grub2 requirements listed in archlinux news?

Last edited by lilsirecho (2011-10-06 03:18:57)

the sad clown · 2011-10-06 03:20:26

Those changes were not grub specific, but were name changes to the packages and should be the same (old.name -> new.name) across bootloaders.

As for what to do, you already have the wiki, and I don't think I am going to be able to do better than it. I don't use GRUB 2, nor do I have a RAID setup.

lilsirecho · 2011-10-06 04:09:27

Thanks for listening and commenting..

For an additional nail into the coffin, I find in grub2 wiki the nomenclature for the term setroot...

In a RAID system this is changed to (md0,1) from the normal (hd0,1).

As was shown in previous posting, my set root is (hd0.1) and had been working fine until Linux3.0.6-1 upgrade. Also, the kernel26 references were working and linux kernel appeared in /usr/src, uname-a was linux kernel.

What do I do now to get RAID0 recognized in grub2?

Entering (md0,1) did not work!

What should my grub2 look like in RAID and what is needed to get it to run with uuid?

lilsirecho · 2011-10-06 17:25:29

Modified the grub as follows:

 set root=(md0,1)
linux /vmlinuz-linux root=/dev/disk/by-uuid/xxxxxxxxxxxxxxxxxxxxxxxxx(ignored)
initrd /initramfs-linux.img
boot

Pressed F10 and displayed:

 booting a command list
error:no such disk
error: You need to load the kernel first
error: no loaded kernel
Press any key to continue

The display reverted to the grub entries after a few seconds.

Still no boot into archlinux

sudemon · 2011-10-07 11:40:01

I usе mdadm and have same problem.
Now load the ArchLinux with edited menu item (grub-0.97 bootloader):

 kernel /vmlinuz-linux root=/dev/disk/by-uuid/50112d31-92f1-402d-be8b-d826356454e9 rootfstype=ext4 ro nouveau.modeset=0 vga=794

to

kernel /vmlinuz-linux root=/dev/md0 rootfstype=ext4 ro nouveau.modeset=0 vga=794

Grizzly` · 2011-10-07 13:40:19

Hi,
It seems that I have the same problem as well.
I have reinstalled my system on raid10f about a month ago, _after_ the change in file naming was made. I make a pacman -Syu about once a week, and that's also the only times I reboot my system (otherwise I just suspend). Last update was yesterday evening. This morning the system won't boot: "not able to find root disk by uuid......".
I already chroot'ed into my system after booting the installation medium. The raid10 array, from this perspective, looks healthy and grub2 setup works fine. I also rebuilt the initramfs and checked for the mdadm hook (present). No help, though.
What I notice when it drops me into the ramfs recovery shell is that there seems to be no /etc/mdadm.conf in the ramdisk. I'm not entirely sure but I think it should be there. When I use vi to create one from scratch in the ramfs recovery shell I can then use mdassemble and the device file for the raid array (but not its partitions) is created and /proc/mdstat says the array is alright.
Can it be that when mkinitcpio (or whatever is responsible for the initramfs hooks) got upgraded the mdadm hook got broken somehow? The /etc/mdadm.conf is missing? Or anything else I can't come up with right now?
Has anybody made any progress solving this? There are a couple of other open threads related to this as well, so it seems to be an urgent question.
How do I revert to an older version of mkinitcpio from chroot/pacman?

Chris

zenlord · 2011-10-07 14:05:32

Maybe I have misread something in this thread, but have any of you already tried to update the bootloader config (as The Sad Clown already suggested in his first post)?

Chroot into your system and run grub-update (or the equivalent for grub2). That should automatically find the boot images - The only thing I have ever had to update manually to grub was the number of the disk: hd(0,1) instead of hd(0,0) (and that was on a Ubuntu system).

Last edited by zenlord (2011-10-07 14:06:04)

lilsirecho · 2011-10-07 15:31:21

Grizzly:

You speak like a true grizzly bear!

I aggree that it seems to be a mkinitcpio problem affecting the /etc/mdadm.conf on boot up.

In my boot sequence the failed uuid notice follows the mdadm activity which made me suspect that was affected by the new upgrade,

Perhaps renewing the mdadm.conf file will solve the difficulty.

Otherwise it has me buffaloed.....

Grizzly` · 2011-10-07 16:13:49

zenlord,
I'm not sure if you refer to my post. As I said, I installed my system from the 08/2011 installation media after the filenames of the kernel image and the initramdisk image changed. My bootloader configuration therefore already reflects the current naming scheme that The Sad Clown was poiting out in his first post.

lilsirecho,
The mdadm.conf in the actual root partition as accessible from chroot is correct. My suspicion is that the mdadm.conf in the initramdisk image is missing...
I never really messed about with the whole initramdisk system before, so I'm not even sure if my assumption is correct that what I see in the "rescue shell" that I get thrown in when the boot procedure fails is the actual initramdisk...

I'm still fiddling with it

Last edited by Grizzly` (2011-10-07 16:45:23)

Grizzly` · 2011-10-07 16:27:01

Okay, it really seems like the custom mdadm.conf I created back when I was installing archlinux somehow got overwritten when updating my system lately.
From a chroot into my system I fixed (maybe) the mdadm.conf and rebuilt the initramdisk image:

mdadm --detail --scan >> /etc/mdadm/mdadm.conf
mkinitcpio -g /boot/initramfs-linux.img

After rebooting I still get the "not able to find root disk by uuid" error
But in the rescue shell I can now indeed find a /etc/mdadm.conf (was not there before), and there is now a device file (/dev/md127) for the raid array itself (wasn't there before either). There are no device files for the 4 partitions on the raid array, however, and I assume that might be the reason why it still can't find the root device (it's on /dev/md127p4)

Correction:

That seems to have fixed it, indeed. I had just messed up my grub.cfg while hunting for a solution earlier this afternoon. After I reverted my grub.cfg to the backup I made in the morning before I started messing around the system boots fine now

I hope this helps anybody else.

Chris.

Last edited by Grizzly` (2011-10-07 16:37:19)

lilsirecho · 2011-10-08 15:36:07

Tried the mdadm approach with no luck....

However, I feel it may still result in a solution because I have looked over the mdadm.conf file and found it lists a different ID than the boot grub ID.

The following indicates the problem:

 h-4.2# blkid
/dev/md0: UUID="6a4f9666-9f07-4792-b4cb-94033b2526f9" TYPE="ext3" SEC_TYPE="ext2" 
/dev/sdd2: UUID="f72d161a-5ae1-e852-d6b2-0ecf8399b027" UUID_SUB="6811e367-aa82-8e8e-ae21-95f8b6cab0b7" LABEL="(none):0" TYPE="linux_raid_member" 
/dev/sdc1: UUID="909993fb-bc95-4b3b-999e-15e6953a564a" TYPE="ext2" 
/dev/sda2: UUID="f72d161a-5ae1-e852-d6b2-0ecf8399b027" UUID_SUB="3c7d48c9-e8d2-26a1-c5ea-0fe2437a8413" LABEL="(none):0" TYPE="linux_raid_member" 
/dev/sde2: UUID="f72d161a-5ae1-e852-d6b2-0ecf8399b027" UUID_SUB="3a214c95-e3ac-20e3-78ca-16916f66a0a8" LABEL="(none):0" TYPE="linux_raid_member" 
/dev/sdg1: UUID="7bd63c08-a9d6-414e-b612-3c0590ac79fa" TYPE="swap" 
/dev/sdg2: UUID="f72d161a-5ae1-e852-d6b2-0ecf8399b027" UUID_SUB="1ef49e97-93ca-108d-3a06-7dbe6b036b74" LABEL="(none):0" TYPE="linux_raid_member" 
/dev/sdf1: UUID="71ebdefd-5418-4d1c-a508-758bb1dcd7a3" TYPE="ext2" 
/dev/sdh1: UUID="909993fb-bc95-4b3b-999e-15e6953a564a" TYPE="ext2" 
/dev/sdh2: UUID="4a16e80d-1cdf-4461-aed4-689350c2c0b4" TYPE="swap" 
/dev/sdd1: UUID="C4B8-1FAD" TYPE="vfat" 
/dev/sdf2: UUID="f72d161a-5ae1-e852-d6b2-0ecf8399b027" UUID_SUB="342e0f07-de13-6456-f66c-dd640d483f63" LABEL="(none):0" TYPE="linux_raid_member" 
/dev/sdh3: UUID="0e55cd32-ad2e-44a9-92d2-6f089176bf1a" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sdh4: UUID="5b9804e6-0076-47d4-abd4-dfd300907013" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sdc2: UUID="4a16e80d-1cdf-4461-aed4-689350c2c0b4" TYPE="swap" 
/dev/sdc3: UUID="d4df3e26-4890-4cbc-ac71-4919c9e54dfc" TYPE="ext3" 
/dev/sdc4: UUID="5b9804e6-0076-47d4-abd4-dfd300907013" TYPE="ext3" 
/dev/sdb1: UUID="859cd38b-3a8a-449b-9989-4467bedacefd" SEC_TYPE="ext2" TYPE="ext3" 
sh-4.2#

The ID given for the second partition for each of five devices is the uuid shown in mdadm.conf.LARGE EDIT:

The ID given in the boot sequence is the ID for md0 which is the root partition.

Since the boot sequence is looking for the root partition, the listing in grub is probably correct.

I should think that mdadm.conf should also list the root partition. I ran a chroot and re-ran mkinitcpio....it created a second listing of uuid for the sda2 partition...again the boot partition.

So mdadm.conf has two array lists of uuid for partition sda2 ......and all the other devices have partition#2 with the same uuid....EDIT:

Am not certain that this arrangement is correct...if it isn't, then mkinitcpio has mucked up my array.

Last edited by lilsirecho (2011-10-08 15:43:38)

Arch Linux

#1 2011-10-05 18:55:57

Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#2 2011-10-05 19:15:42

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#3 2011-10-05 19:24:22

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#4 2011-10-05 23:27:14

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#5 2011-10-05 23:58:52

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#6 2011-10-06 01:03:08

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#7 2011-10-06 01:29:25

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#8 2011-10-06 01:41:16

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#9 2011-10-06 01:57:27

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#10 2011-10-06 02:20:03

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#11 2011-10-06 02:38:37

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#12 2011-10-06 02:43:49

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#13 2011-10-06 02:45:01

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#14 2011-10-06 02:46:29

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#15 2011-10-06 03:05:51

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#16 2011-10-06 03:20:26

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#17 2011-10-06 04:09:27

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#18 2011-10-06 17:25:29

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#19 2011-10-07 11:40:01

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#20 2011-10-07 13:40:19

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#21 2011-10-07 14:05:32

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#22 2011-10-07 15:31:21

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#23 2011-10-07 16:13:49

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#24 2011-10-07 16:27:01

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

#25 2011-10-08 15:36:07

Re: Upgrade to linux-3.0.6-1 causes no boot(Success with fewer devices in

Board footer