I read a few posts in the meanwhile about AUFS and it seems to be a bit problematic when it comes to permissions.
Is it really a better solution than a linear raid? Or should I wait for overlayfs?
Thanks
Beiträge von TheEmperor
-
-
ok, didn't know that.
Wiping sounds like all data will be gone, right?
What exactly do you mean by a Pool solution?
Thanks,
Robert -
Hello,
I have the same problem as so many others and I have already read lots of threads regarding this issue.
However, I have not found a solution for my problem.I have rebooted my OMV and all of a sudden my linear raid consisting of two brand new 6 TB WD Red disks was gone.
It was not the first time I rebooted the server, nor have I done something special before the reboot (I was resetting the permissions on a shared folder, because it was read-only for some reason).I work as a developer and I think I have quite some technical knowledge, but my experience with raids is little and I'm a Linux newbie
Here is the output from the support tab:
Code
Alles anzeigenPersonalities : [linear] md0 : inactive sdc[1] 5860522576 blocks super 1.2 unused devices: <none> /dev/sda1: UUID="88f1fb03-8b90-474b-8e19-2c821eb44dd4" TYPE="ext4" /dev/sda5: UUID="b27e24fa-da81-4019-ba96-28da337b671f" TYPE="swap" /dev/sdc: UUID="4a0cebf8-3297-5443-fb4b-b9655c49daf8" UUID_SUB="7038d1f7-fa71-557e-3777-faccc23e956c" LABEL="omvNAS:files" TYPE="linux_raid_member" Disk /dev/sda: 128.0 GB, 128035676160 bytes 255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0001496c Device Boot Start End Blocks Id System /dev/sda1 * 2048 239855615 119926784 83 Linux /dev/sda2 239857662 250068991 5105665 5 Extended /dev/sda5 239857664 250068991 5105664 82 Linux swap / Solaris Disk /dev/sdb: 6001.2 GB, 6001175126016 bytes 256 heads, 63 sectors/track, 726751 cylinders, total 11721045168 sectors 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 identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. Disk /dev/sdc: 6001.2 GB, 6001175126016 bytes 256 heads, 63 sectors/track, 726751 cylinders, total 11721045168 sectors 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 identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary.If it is neccessary I can reformat everything as the data is still available on my old NAS, but I had to copy 4 TB over the network, which I would not like to repeat if possible
Any help would be highly appreciated!
Thanks,
Robert