Impossible to mount raid grape

Okipa · 28. März 2023

Hello Everybody.

I fixed network issues, then i can access to my OMV UI but i don't have access to my files.

I try that command.

Code

root@homeserver:~# fdisk -l
Disk /dev/sde: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA HDWD105
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdc: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA HDWD105
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA HDWD105
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xe38d3587

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048 960184319 960182272 457,9G 83 Linux
/dev/sda2       960186366 976771071  16584706   7,9G  5 Extended
/dev/sda5       960186368 976771071  16584704   7,9G 82 Linux swap / Solaris

Partition 2 does not start on physical sector boundary.


Disk /dev/sdd: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA HDWD105
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdb: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA HDWD105
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdf: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA HDWD105
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Alles anzeigen

I tryed that one too :

Code

root@homeserver:~# sudo mount -t ext4 /dev/md0 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error.

Any Idea?

have a nice day all !

Clément

geaves · 28. März 2023

post the output of cat /proc/mdstat and blkid

Okipa · 28. März 2023

Code

root@homeserver:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [ra                                 id10]
md0 : inactive sdf[4](S) sdb[1](S) sde[0](S) sdc[2](S) sdd[3](S)
      2441272440 blocks super 1.2

unused devices: <none>

Code

root@homeserver:~# blkid
/dev/sdb: UUID="e76967b0-2c69-1845-4480-cdbcd351e1bf" UUID_SUB="abb8dd1c-1794-d817-90a3-7c32d84dfbe5" LABEL="homeserver:RAID" TYPE="linux_raid_member"
/dev/sda1: UUID="46cb65f6-77e9-43e6-b2c9-ba38f1bac0a8" TYPE="ext4" PARTUUID="e38d3587-01"
/dev/sda5: UUID="c8cbc88b-12a3-4d1e-b5a9-340716023993" TYPE="swap" PARTUUID="e38d3587-05"
/dev/sdd: UUID="e76967b0-2c69-1845-4480-cdbcd351e1bf" UUID_SUB="d8a95b43-2504-27cb-94fe-c3e1fb88d5cb" LABEL="homeserver:RAID" TYPE="linux_raid_member"
/dev/sde: UUID="e76967b0-2c69-1845-4480-cdbcd351e1bf" UUID_SUB="9daf07c2-1f71-2c40-a820-8a27daa0742d" LABEL="homeserver:RAID" TYPE="linux_raid_member"
/dev/sdc: UUID="e76967b0-2c69-1845-4480-cdbcd351e1bf" UUID_SUB="2e9bee1a-cc0c-e46c-d62b-5f2d60b8dad7" LABEL="homeserver:RAID" TYPE="linux_raid_member"
/dev/sdf: UUID="e76967b0-2c69-1845-4480-cdbcd351e1bf" UUID_SUB="a32b09fc-4c80-e974-e17c-af24480fb5b8" LABEL="homeserver:RAID" TYPE="linux_raid_member"

geaves · 28. März 2023

The answer is in the first output, you can't mount an inactive array

mdadm --assemble --force --verbose /dev/md0 /dev/sd[bcdef]

Okipa · 28. März 2023

Code

root@homeserver:~# mdadm --assemble --force --verbose /dev/md0 /dev/sd[bcdef]
mdadm: looking for devices for /dev/md0
mdadm: /dev/sdb is busy - skipping
mdadm: /dev/sdc is busy - skipping
mdadm: /dev/sdd is busy - skipping
mdadm: /dev/sde is busy - skipping
mdadm: /dev/sdf is busy - skipping

Strange, isn't it?

geaves · 28. März 2023

Zitat von Okipa

Strange, isn't it

No my error,

mdadm --stop /dev/md0 then the command I posted

not too good at multitasking

Okipa · 28. März 2023

You're GREAT at multitasking !!!!!

It works, I have now access to my files !

I still have trouble to connect to my nextcloud UI... I will try later.

Last more question, if i want to update to OMV 6, can I update with uplugged my HDD then done the same command as you provided and the raid grape will mount again in the newer version?

Okipa · 28. März 2023

OK Nextcloud solved

Just mount the file system before start nextcloud service

geaves · 28. März 2023

Zitat von Okipa

Last more question, if i want to update to OMV 6, can I update with uplugged my HDD

If you do a clean install disconnect all data drives, then do the clean install, set it up, and fully update, shutdown, connect data drives and restart, the only thing to do then is set up shared folders and smb the array should display under raid management

Okipa · 28. März 2023

It sounds not good now, when reboot, omv is in emergency mode...

I try CTRL+D to continue, then systemctl reboot.

Then when i connect to UI in raid section :

Code

  Version : 1.2
     Creation Time : Mon Mar 16 08:44:13 2020
        Raid Level : raid5
        Array Size : 1953017856 (1862.54 GiB 1999.89 GB)
     Used Dev Size : 488254464 (465.64 GiB 499.97 GB)
      Raid Devices : 5
     Total Devices : 4
       Persistence : Superblock is persistent

     Intent Bitmap : Internal

       Update Time : Tue Mar 28 14:58:56 2023
             State : clean, degraded
    Active Devices : 4
   Working Devices : 4
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K

Consistency Policy : bitmap

              Name : homeserver:RAID
              UUID : e76967b0:2c691845:4480cdbc:d351e1bf
            Events : 5187592

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

Alles anzeigen

One disk seems to be missing...

Okipa · 28. März 2023

it missed dev/sdf but it still in smart section

EDIT : I change the drive and RAID is recovering now.

Impossible to mount raid grape

Jetzt mitmachen!

Tags