RAID5 missing

mediagiant · 10. August 2018

Yesterday, I went to access my RAID5 array through Windows, and it was disconnected. I couldn't get it back, so unplugged my Raspberry Pi and plugged it back in to power cycle it. I have three Toshiba Canvio 1 TB USB drives plugged in through a powered USB hub that is, in turn, plugged into my Raspberry Pi. I also have a fourth Toshiba Canvio drive that I use as a backup, and I can still access that one.

Here's the information from SSH:

Code

root@raspberrypi:~# cat /proc/mdstat
Personalities :
unused devices: <none>
root@raspberrypi:~# blkid
/dev/mmcblk0p1: LABEL="boot" UUID="CE83-8CE1" TYPE="vfat" PARTUUID="c5ac05a5-01"
/dev/mmcblk0p2: UUID="ae708a4d-982a-4a20-965c-01ec7e1f32b3" TYPE="ext4" PARTUUID                                                                                                                                                             ="c5ac05a5-02"
/dev/sda: UUID="8ff2382b-1011-e4f7-6b28-c7eb8dfe57ec" UUID_SUB="a2ad3e46-b810-22                                                                                                                                                             8c-feb9-34c85b486bc6" LABEL="raspberrypi:RAID5" TYPE="linux_raid_member"
/dev/sdb: UUID="8ff2382b-1011-e4f7-6b28-c7eb8dfe57ec" UUID_SUB="29412fe3-8c41-a7                                                                                                                                                             46-d389-ff434ecccc60" LABEL="raspberrypi:RAID5" TYPE="linux_raid_member"
/dev/sdc: UUID="8ff2382b-1011-e4f7-6b28-c7eb8dfe57ec" UUID_SUB="8ef099e8-8b8f-72                                                                                                                                                             4a-10b4-a5a619c384d0" LABEL="raspberrypi:RAID5" TYPE="linux_raid_member"
/dev/zram0: UUID="e1a5ce9f-3124-43ee-91bb-2005e464f464" TYPE="swap"
/dev/zram1: UUID="8535e5dc-f4bb-4594-a519-326701cdfb06" TYPE="swap"
/dev/zram2: UUID="e4aaf65f-77f6-49a6-8ee0-adac9f39edbf" TYPE="swap"
/dev/zram3: UUID="6e068c3a-df69-45b2-88b2-ed34d0acd8fd" TYPE="swap"
/dev/sde1: LABEL="New Volume" UUID="26DE1E1EDE1DE6B9" TYPE="ntfs" PARTLABEL="Bas                                                                                                                                                             ic data partition" PARTUUID="2214ec36-1426-4510-83f0-70e2c1d6d96f"
/dev/mmcblk0: PTUUID="c5ac05a5" PTTYPE="dos"
/dev/mmcblk0p3: PARTUUID="c5ac05a5-03"

Alles anzeigen

mediagiant · 10. August 2018

More details:

Code

root@raspberrypi:~# fdisk -1 | grep "Disk "
fdisk: invalid option -- '1'


Usage:
 fdisk [options] <disk>      change partition table
 fdisk [options] -l [<disk>] list partition table(s)


Options:
 -b, --sector-size <size>      physical and logical sector size
 -c, --compatibility[=<mode>]  mode is 'dos' or 'nondos' (default)
 -L, --color[=<when>]          colorize output (auto, always or never)
 -l, --list                    display partitions end exit
 -t, --type <type>             recognize specified partition table type only
 -u, --units[=<unit>]          display units: 'cylinders' or 'sectors' (default)
 -s, --getsz                   display device size in 512-byte sectors [DEPRECATED]


 -C, --cylinders <number>      specify the number of cylinders
 -H, --heads <number>          specify the number of heads
 -S, --sectors <number>        specify the number of sectors per track


 -h, --help     display this help and exit
 -V, --version  output version information and exit


For more details see fdisk(8).
root@raspberrypi:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>


# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=raspberrypi:RAID5 UUID=8ff2382b:1011e4f7:6b28c7eb:8dfe57ec

Alles anzeigen

ryecoaaron · 10. August 2018

We have said over and over to not use raid on usb drives let alone an RPi. Very bad idea. If this command doesn't work, you are on your own.

mdadm --assemble --verbose --force /dev/md127 /dev/sd[abc]

If that works, omv-mkconf mdadm

SuperUJ · 10. August 2018

I followed the same advice a week ago to get the RAID (on XU4) running again using this command ... and placed an order for a HC2 the same time. After a few reboots, my XU4 RAID array became unstable again while waiting for HC2's arrival. After some initial tests, the HC2 appears to be a lot more reliable on OMV 4. I know I will lose high availability with HC2, but it's better than the RAID not available at all. Currently, I am running HC2 in parallel and loading data into it. Keeping my fingers crossed.

Regards,

John

mediagiant · 13. August 2018

Well I knew it wasn't ideal, but I didn't think it would totally DIE on me. I just figured it wasn't going to be as fast as doing a proper RAID with a SATA card.

Fortunately, I have not lost any data as a result because I had an RSync backup in place to a single drive. It's just annoying and making me regret buying all those external hard drives.

Any thoughts on how I can put these drives to better use while not spending a ton of money on a pricey enclosure? I guess I could RSync from one to another for backup, but that still leaves two drives unused.

ryecoaaron · 13. August 2018

It definitely isn't just about speed. Raid redundancy makes no sense with a device that has no redundancy in it.

Zitat von mediagiant

Any thoughts on how I can put these drives to better use while not spending a ton of money on a pricey enclosure? I guess I could RSync from one to another for backup, but that still leaves two drives unused.

No idea what you are using it for but you could pool the drives with the unionfilesystem plugin. Create two pools and rsnapshot one pool to the other.

mediagiant · 14. August 2018

Zitat von ryecoaaron

We have said over and over to not use raid on usb drives let alone an RPi. Very bad idea. If this command doesn't work, you are on your own.

mdadm --assemble --verbose --force /dev/md127 /dev/sd[abc]

If that works, omv-mkconf mdadm

It worked, so thanks for that.

Of course, I'm trying to decide where to go from here because this doesn't seem like it's going to be very reliable.

Jetzt mitmachen!