Raid5 inactive
-
-
-
-
/dev/md127
-
for a RAID you might have to use mdadm instead of tune2fs
-
Like this.
mdadm -U <64e3ec20-451e-4296-aa32-d1f5edc476a9> </dev/md127>
-
As I understand the man page, you have to pass the --uuid option when assembling the RAID. Would be best to try it in a virtual machine first.
-
tune2fs -U d0ce733b-af77-4acc-bc5f-76e290b0d0ee /dev/md127
worked for me in a VM with a RAID5 with ext4 filesystem
-
Sorry did not see your Post.
As i wrote i am an absolute noob.
I'm glad to get here help and support.
Unfortunately i have no idea how to try in VM.
Btw.
fschk says that the /dev/md127 was not unmount correctly.
-
can you run fsck /dev/md127 again to see if the issue has been fixed?
-
tune2fs -U d0ce733b-af77-4acc-bc5f-76e290b0d0ee /dev/md127
worked for me in a VM with a RAID5 with ext4 filesystem
Will give it a try.
-
If you do not have a backup of your data, NOW is a good moment to make one before trying anything else on the system.
-
-
-
Were you able to make it work?
-
Unfortunately not.
After every reboot the array is unmounted again.
The used space of the mounted Array is show as 88.02 MB, but the real used space is around 2,5 TB.
Trying to copy new data to a shared Folder ends in an error message (out of space).
Best way maybe to delete all Shares and remove the Array and set it up from scratch.
-
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!