Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: Upgrade destroys dmraid

  1. #1

    Default Upgrade destroys dmraid

    After upgrading from openSUSE Leap 42.1 to openSUSE Leap 42.2 the system boots from a single disk instead of the raid array. This happens when upgrading online using zypper as well as offline using the dvd. I suspect that the dmraid configuration is not written correctly to the configuration files and/or initrd. Is there a way to check and fix this in the rescue system during the first reboot?

    It is possible to mount the root partition and chroot to the mount point from the rescue system to edit the configuration files, make a new initrd and install grub. What files do i have to check?

    Unfortunately there is a windows installation on partition 1 and the extended partition 4 is filled with a FAT32 partition. So there is neither a free partition table entry nor space left for a boot partition. But this configuration worked for now.

    The array controller is an NVIDIA Corporation MCP55 SATA Controller (rev a2). After rolling back to the old openSUSE 42.1 installation, i could give some more information and give it another try.

  2. #2

    Default Re: Upgrade destroys dmraid

    Another try with a completely empty raid array letting Yast to decide the partitioning failed too. The system stops at the emergency shell.

    Unfortunately i could not post the whole log, but the red marked lines are:

    blk_update_request: I/O error, dev fd0, sector 0
    Failed to mount /var/lib/mailman.
    Failed to mount /var/lib/libvirt/images.
    Failed to mount /.snapshots.
    Failed to mount /opt.
    Failed to mount /tmp.
    Failed to mount /var/log.
    Failed to mount /var/cache.
    Failed to mount /var/lib/mariadb.
    Failed to mount /var/crash.
    Failed to mount /srv.
    Failed to mount /usr/local.
    Failed to mount /var/lib/named.
    Failed to mount /var/lib/machines.
    Failed to mount /var/lib/mysql.
    Failed to mount /var/spool.
    Failed to mount /var/opt.
    Failed to mount /var/lib/pgsql.
    Failed to mount /var/tmp.
    MPU-401 device not found or device busy
    Failed to activate swap /dev/disk/by-uuid/0040d135-e0b2-41b3-ae26-cc980f50d099.
    Failed to mount /home.
    Failed to mount /boot.
    Could not open dir /var/log/audit (No such file or directory)

  3. #3

    Default Re: Upgrade destroys dmraid

    Another try with a completely empty raid array letting Yast to decide the partitioning, but this time with openSUSE 42.3. Here dmraid is missing in initramfs.

    Is dmraid still supported at all?

  4. #4
    Join Date
    Sep 2012
    Posts
    5,112

    Default Re: Upgrade destroys dmraid

    Quote Originally Posted by amadrits View Post
    Is dmraid still supported at all?
    There were a lot of problem reports in the past. The problem is, it requires specific hardware to test. Most common platform (Intel) was switched to mdraid long ago, which leaves less common systems and those cannot use automated test framework that runs on VM. So dmraid support depends on users having specific hardware and actively contributing, at least by troubleshooting and determining root cause of issue (of course, submitting patches to fix it would be ideal).

    If as you say Leap 42.1 works and Leap 42.2 not it is clear regression; you should open bug report to investigate. Before doing it you should test with 42.3 whether this is fixed there.

  5. #5

    Default Re: Upgrade destroys dmraid

    Quote Originally Posted by arvidjaar View Post
    If as you say Leap 42.1 works and Leap 42.2 not it is clear regression; you should open bug report to investigate. Before doing it you should test with 42.3 whether this is fixed there.
    I did already test with 42.3 as you can see above.

  6. #6

    Default Re: Upgrade destroys dmraid

    I confirm the same problem after I upgraded. The existing raid was no longer recognized and not present in the partitioner of yast.

    After executing dmraid -ay the raid volumes did show up in partitioner of yast.

  7. #7

    Default Re: Upgrade destroys dmraid

    The message "blk_update_request: I/O error, dev fd0, sector 0" is not related to the dmraid problem and disappears, when i disable the floppy controller. Because i use the floppy drive and it works as expected, i ignore this message.

    The message "MPU-401 device not found or device busy" is not related to the dmraid problem too. Because i don't have such hardware, i blacklisted the kernel modules snd_mpu401 and snd_mpu401_uart.

    A strange behavior i observed, is that this dmraid problem sometimes does not occur and the system boots as expected, when the system was shut down for several hours. A failed boot process, which stuck in the emergency shell, can be continued by pressing ctrl-d and the system then boots successfully.

    I will try to attach a more detailed log of a failed boot process.

  8. #8

    Default Re: Upgrade destroys dmraid

    Where can i post logs?

  9. #9
    Join Date
    Sep 2012
    Posts
    5,112

    Default Re: Upgrade destroys dmraid

    Quote Originally Posted by amadrits View Post
    Where can i post logs?
    https://paste.opensuse.org/ and post link here.

  10. #10

    Default Re: Upgrade destroys dmraid


Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •