HDD Device ids are mixed up

barrydick · 26. Juli 2023

Need some help before I make this worse please.

I physically added some HDDs to my server today and upon power up the drive ids of the existing drives were incorrect. I have since disconnected the new drives but I am still having problems.

I have the OS on a 120GB SSD and 4 2TB data drives in Raid 5. I (obviously) need to recover the RAID array get my data.

This is the configuration before the problem.

This is what I have now. Note that File System data is also mixed up.

If I disconnect the 4 data drives the OS drive is /dev/sda. If I reconnect the 4 data drives it moves the data drive to dev/sde. The cabling has not changed. Please help me normalise the situation before I re-attempt connecting my new drives.

raulfg3 · 26. Juli 2023

not possible for me to see the pictures (low resolution)

votdev · 26. Juli 2023

Zitat von raulfg3

not possible for me to see the pictures (low resolution)

Me too

votdev · 26. Juli 2023

Devices are named by udev and the kernel based in first come first serve. This means that /dev/sda can become /dev/sdb or /dev/sdX after a reboot or plugging new devices. This is only a visual thing because internally OMV is using predictable device names because of exactly that reason you see right now. Device names like /dev/sdX are not predictable.

barrydick · 26. Juli 2023

hi very sorry. I've the pictures as attachments. hopefully thats better

votdev · 26. Juli 2023

The RAID is degraded because one disk is missing. MD should not take care about the device names because it scans the devices for metadata on startup.

barrydick · 26. Juli 2023

Zitat von votdev

The RAID is degraded because one disk is missing. MD should not take care about the device names because it scans the devices for metadata on startup.

Thank you. The four disks that are part or the Raid are listed on disk screen in the GUI. They are now dev/sda sdb, sdc, sdd. What's the correct process to recover from this?

Code

  Version : 1.2
     Creation Time : Thu Dec  8 20:22:05 2011
        Raid Level : raid5
        Array Size : 5860540416 (5589.05 GiB 6001.19 GB)
     Used Dev Size : 1953513472 (1863.02 GiB 2000.40 GB)
      Raid Devices : 4
     Total Devices : 3
       Persistence : Superblock is persistent

       Update Time : Wed Jul 26 19:53:06 2023
             State : clean, degraded
    Active Devices : 3
   Working Devices : 3
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K

Consistency Policy : resync

              Name : MediaServer:ARY0
              UUID : 940050c6:21c49b95:5f99f61b:6f06e88b
            Events : 9534

    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       -       0        0        1      removed
       2       8       32        2      active sync   /dev/sdc
       3       8       48        3      active sync   /dev/sdd

Alles anzeigen

votdev · 26. Juli 2023

Please post the output of blkid.

barrydick · 26. Juli 2023

Code

root@openmediavault:~# blkid
/dev/sdc: UUID="940050c6-21c4-9b95-5f99-f61b6f06e88b" UUID_SUB="8a0d3006-e460-91                                                   fa-4331-0d1cba174bb1" LABEL="MediaServer:ARY0" TYPE="linux_raid_member"
/dev/sda: UUID="940050c6-21c4-9b95-5f99-f61b6f06e88b" UUID_SUB="ebca366d-84ed-77                                                   09-4aaf-83aaaaf356b3" LABEL="MediaServer:ARY0" TYPE="linux_raid_member"
/dev/sdd: UUID="940050c6-21c4-9b95-5f99-f61b6f06e88b" UUID_SUB="5f518e47-ee41-ea                                                   87-683e-1d4d8b859b39" LABEL="MediaServer:ARY0" TYPE="linux_raid_member"
/dev/sde: UUID="940050c6-21c4-9b95-5f99-f61b6f06e88b" UUID_SUB="26d0739d-6d84-f7                                                   d9-4af2-6b4d8950d322" LABEL="MediaServer:ARY0" TYPE="linux_raid_member"
/dev/sdb1: UUID="a8f206e8-92b8-43fe-a5b9-7fd3a58dba34" BLOCK_SIZE="4096" TYPE="e                                                   xt4" PARTUUID="c0477fe9-01"
/dev/sdb5: UUID="a69ea4ac-0d3d-4c7d-8724-1403c2955695" TYPE="swap" PARTUUID="c04                                                   77fe9-05"
/dev/md127: LABEL="Vol0" UUID="0ed1d785-1052-4684-8ff0-3fd868c09cd8" BLOCK_SIZE=                                                   "4096" TYPE="ext4"
root@openmediavault:~#

votdev · 26. Juli 2023

Zitat von barrydick

Thank you. The four disks that are part or the Raid are listed on disk screen in the GUI. They are now dev/sda sdb, sdc, sdd. What's the correct process to recover from this?

Code

  Version : 1.2
     Creation Time : Thu Dec  8 20:22:05 2011
        Raid Level : raid5
        Array Size : 5860540416 (5589.05 GiB 6001.19 GB)
     Used Dev Size : 1953513472 (1863.02 GiB 2000.40 GB)
      Raid Devices : 4
     Total Devices : 3
       Persistence : Superblock is persistent

       Update Time : Wed Jul 26 19:53:06 2023
             State : clean, degraded
    Active Devices : 3
   Working Devices : 3
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K

Consistency Policy : resync

              Name : MediaServer:ARY0
              UUID : 940050c6:21c49b95:5f99f61b:6f06e88b
            Events : 9534

    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       -       0        0        1      removed
       2       8       32        2      active sync   /dev/sdc
       3       8       48        3      active sync   /dev/sdd

Alles anzeigen

Zitat von barrydick

Code

root@openmediavault:~# blkid
/dev/sdc: UUID="940050c6-21c4-9b95-5f99-f61b6f06e88b" UUID_SUB="8a0d3006-e460-91                                                   fa-4331-0d1cba174bb1" LABEL="MediaServer:ARY0" TYPE="linux_raid_member"
/dev/sda: UUID="940050c6-21c4-9b95-5f99-f61b6f06e88b" UUID_SUB="ebca366d-84ed-77                                                   09-4aaf-83aaaaf356b3" LABEL="MediaServer:ARY0" TYPE="linux_raid_member"
/dev/sdd: UUID="940050c6-21c4-9b95-5f99-f61b6f06e88b" UUID_SUB="5f518e47-ee41-ea                                                   87-683e-1d4d8b859b39" LABEL="MediaServer:ARY0" TYPE="linux_raid_member"
/dev/sde: UUID="940050c6-21c4-9b95-5f99-f61b6f06e88b" UUID_SUB="26d0739d-6d84-f7                                                   d9-4af2-6b4d8950d322" LABEL="MediaServer:ARY0" TYPE="linux_raid_member"
/dev/sdb1: UUID="a8f206e8-92b8-43fe-a5b9-7fd3a58dba34" BLOCK_SIZE="4096" TYPE="e                                                   xt4" PARTUUID="c0477fe9-01"
/dev/sdb5: UUID="a69ea4ac-0d3d-4c7d-8724-1403c2955695" TYPE="swap" PARTUUID="c04                                                   77fe9-05"
/dev/md127: LABEL="Vol0" UUID="0ed1d785-1052-4684-8ff0-3fd868c09cd8" BLOCK_SIZE=                                                   "4096" TYPE="ext4"
root@openmediavault:~#

It seems you've rebooted the system in the meanwhile because the output of blkid does not match the output of mdadm anymore. Please post cat /proc/mdstat and mdadm --detail /dev/md127, too.

barrydick · 26. Juli 2023

Code

root@openmediavault:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md127 : active raid5 sdd[0] sde[3] sda[2]
      5860540416 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [U_UU]

unused devices: <none>


root@openmediavault:~# mdadm --detail /dev/md127
/dev/md127:
           Version : 1.2
     Creation Time : Thu Dec  8 20:22:05 2011
        Raid Level : raid5
        Array Size : 5860540416 (5589.05 GiB 6001.19 GB)
     Used Dev Size : 1953513472 (1863.02 GiB 2000.40 GB)
      Raid Devices : 4
     Total Devices : 3
       Persistence : Superblock is persistent

       Update Time : Wed Jul 26 22:00:27 2023
             State : clean, degraded
    Active Devices : 3
   Working Devices : 3
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K

Consistency Policy : resync

              Name : MediaServer:ARY0
              UUID : 940050c6:21c49b95:5f99f61b:6f06e88b
            Events : 10404

    Number   Major   Minor   RaidDevice State
       0       8       48        0      active sync   /dev/sdd
       -       0        0        1      removed
       2       8        0        2      active sync   /dev/sda
       3       8       64        3      active sync   /dev/sde

Alles anzeigen

votdev · 26. Juli 2023

Bash

# mdadm /dev/md127 -a /dev/sdc

barrydick · 26. Juli 2023

Zitat von votdev
Bash
# mdadm /dev/md127 -a /dev/sdc

Code

root@openmediavault:~# mdadm /dev/md127 -a /dev/sdc
mdadm: added /dev/sdc

ok. Thanks I've done that. The GUI shows its busy adding that drive.

Working on the assumption that fixes the RAID, I take it I'm ok to power down and add my new drive(s) afterwards?

barrydick · 28. Juli 2023

votdev thanks very much for your great support. Your solution worked but unfortunately the RAID array became degraded again about a day later so it seems I have a hardware issue to deal with. The good news is that I managed to backup my data so its no longer urgent. Thank you again.

HDD Device ids are mixed up

barrydick 28. Juli 2023

Jetzt mitmachen!