1

I'm gettind this error at boot:

grub error: disk 'lvid/caoMWu-o417-GMgh-6vFj-1qrw-iJMi-ypwm0f/Z2eotR-N0HN-nrol-3hUd-odMB-GzHy-4PrsnL' not found. Entering rescue mode..

I can't even get the GRUB menu, the error message show immediately up.

Now here's the situation: I had to replace my motherboard because it was broken, and just after the change (I've replaced with an identical one) I'm not able to boot anymore.

This is my setup: Archlinux distro, two hdd with a RAID1 and LVM builded on top of it.

Now I can't understand what happened, cause the UUID of the disk/partition should be remained the same even after mb replacement ?

What can I do/check to restore the system ?

Below some info about the LVM setup:

--- Volume group ---
  VG Name               server
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  5
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               2
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               2.73 TiB
  PE Size               4.00 MiB
  Total PE              715318
  Alloc PE / Size       715318 / 2.73 TiB
  Free  PE / Size       0 / 0   
  VG UUID               caoMWu-o417-GMgH-6vFj-1qrv-iJMi-ypwm0f


  --- Logical volume ---
  LV Path                /dev/server/boot
  LV Name                boot
  VG Name                server
  LV UUID                3Z70U8-Mc1W-aKQU-tORg-oiaT-P2kI-aYG74K
  LV Write Access        read/write
  LV Creation host, time archiso, 2015-11-06 08:51:19 +0100
  LV Status              available
  # open                 1
  LV Size                512.00 MiB
  Current LE             128
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

  --- Logical volume ---
  LV Path                /dev/server/swap
  LV Name                swap
  VG Name                server
  LV UUID                z8PdBc-DZRL-zsC5-190M-nyUl-k3cn-9gaYRo
  LV Write Access        read/write
  LV Creation host, time archiso, 2015-11-06 08:51:28 +0100
  LV Status              available
  # open                 0
  LV Size                4.00 GiB
  Current LE             1024
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

  --- Logical volume ---
  LV Path                /dev/server/archroot
  LV Name                archroot
  VG Name                server
  LV UUID                Z2eotR-N0HN-nroI-3hUd-odMB-GzHy-4PrsnL
  LV Write Access        read/write
  LV Creation host, time archiso, 2015-11-06 08:52:37 +0100
  LV Status              available
  # open                 1
  LV Size                20.00 GiB
  Current LE             5120
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:2

  --- Logical volume ---
  LV Path                /dev/server/storage
  LV Name                storage
  VG Name                server
  LV UUID                cccOsD-GBXu-pMws-e4bS-tCic-ZCFs-OstIf9
  LV Write Access        read/write
  LV Creation host, time archiso, 2015-11-06 08:52:52 +0100
  LV Status              available
  # open                 0
  LV Size                2.70 TiB
  Current LE             709046
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3

and the /etc/fstab :

# /dev/mapper/server-archroot
UUID=c83b58a5-d4fd-4634-b6b7-1726ca6ffeb6   /           ext4        rw,relatime,data=ordered    0 1

# /dev/mapper/server-boot
UUID=1fffa9ae-ea36-4888-870e-47bd8fc16268   /boot       ext4        rw,relatime,data=ordered    0 2

# /dev/mapper/server-swap
UUID=a787eefb-692d-4d2a-9482-11196967ea62   none        swap        defaults    0 0

# /dev/mapper/server-storage
UUID=ae082954-b90a-482a-b002-e53f6f75df5a   /mnt/storage    ext4        users,rw,relatime,auto,exec,data=ordered
  • So what happened? What did you do to get this working? The below solutions didn't work for me. – Brian Stinar Dec 30 '18 at 23:30
  • Actually all was fine. I was running a HP microserver G8 wich has hardware RAID system wich is not compatible with linux (as fair as i understand). So basically I just disabled it from bios, like already did with the old motherboard. – lorenzolorenzo Jan 2 at 8:27
0

Have you tried update-grub2?

Now I can't understand what happened, cause the UUID of the disk/partition should be remained the same even after mb replacement ?

But new mobo could ascribe hdds in a different way, so now it is not possible to start even GRUB.

  • I've already tried it from a live image. Both update-grub and mkinitcpio are exectuted without errors, but didn't solve the problem. – lorenzolorenzo Jul 25 '16 at 8:39
  • I wander, what was the cause. I had a same problem, but grub2-install (which is run by update-grub) reported errors as the partition was really broken and even cryptsetup luksOpen /dev/sdXY crypt didn't work. – pevik Nov 5 '16 at 22:23
0

It seems that your motherboard changed the UUIDs of your disks and lvs as is apt to happen.

When you go into recovery mode, you'll need to run one of the following commands:

ls -l /dev/disk/by-uuid

blkid

To find the UUID of your boot partition.

If necessary, you can run fdisk -l to help find out which is the boot partition.

You can then add the correct UUIDs to /etc/fstab and you will be able to boot again with no issues.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.