cat /proc/mdstat
i did that but, then i got this
how can i see on what drive the superblock is?
cat /proc/mdstat
i did that but, then i got this
how can i see on what drive the superblock is?
Maybe sda is your os drive. What is the output of: fdisk -l | grep "Disk " | grep sd
thanx for the support ryecoaaron btw , i really like it , , i have no usb key or omv attached to the machine just drives and usb dvd-rw
I have moved out the drives and stacked them ontop of eachother so i can handle the cables more easily :)..
seems like i swapped the discs / cables around maybe...the drives show up atleast....
i have more pictures also with command output
I really have no idea why the four drives show up but the array info is gone. Using the create command with assume clean flag is the only idea I have left but it results in a wiped array about half the time.
Ok , just to be sure .
To rebuild the array, do i need to have the omv boot media attached ? I cloned the messed up USB you know.
I assume resquecd is enough to rebuild.??
Maybe more moderators could help ?
This is abit , is the arrayinfo stored on all the 10 driver Or only on the omv installation
do i need to have the omv boot media attached ?
no
I assume resquecd is enough to rebuild.??
yes
Maybe more moderators could help ?
Good luck with that. I am the one who answers most of the raid questions.
is the arrayinfo stored on all the 10 driver Or only on the omv installation
array info is stored on the array drives.
Thanx for your reply , so there something more i could try ?
By the way , Did not meen to upset you.
I know you are elite at this ,)
Just abit Sad about the whole thing ....
The only other thing I would try is the mdadm create command. I don't like recommending that because it wipes the array too often.
You didn't upset me. I was just telling you that others probably don't have any ideas either.
I get the sad part but raid is not backup. I see a lot of raid issues and not really sure what causes them. I've moved away from software raid myself even though I never had problems. Real hardware raid cards are easy enough to get reasonably priced on eBay and I haven't seen people (or myself) having problems with them. Unless you really need the speed, I would use unionfilesystem pooling.
Ok i understand . Just got Therese discs and new chassi and stuff so not fun.
But the good news Is the data mostly torrents that i can download again. But alot of Them..
IF i could find where the superblock is Then maybe
IT reports that IT cant be found on sda
When i do this.
18 hours ago
Assuming sdk is still the boot drive, I would try:
mdadm --stop /dev/md0
mdadm --assemble --force --verbose /dev/md127 /dev/sd[abcdefghij]
I would look for a howto on recovering superblocks. Never had much luck doing that myself but I haven't had many opportunities.
Hi again ryecoaaron , i was actually able to create a md0 with a command i googled.
got 9 out of 10 drives , and added the last drive in the webgui , so the raid is up again
and now new data has been written to the discs since crash..
one problem tho no files or filesystem popup in omvwebgui
the raid shows tho
is there away ti get the actual files back? or filesystem and folders?
using command or som resquecd
my array is called md0 now
not new data
no new data should it be....:)
i did a fresh install on omv an a external harddrive.
and the raid6 filesystem are there during install , but as i said no filesystem , i think there is a way to fix that , or hope
Last login: Thu Oct 6 23:25:50 2016
root@HP-Z400-Workstation:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid6 sde[10] sdb[0] sdd[9] sdc[8] sda[7] sdj[5] sdi[4] sdh[3] sdg[2] sdf[1]
23441080320 blocks super 1.2 level 6, 512k chunk, algorithm 2 [10/9] [UUUUUU_UUU]
[==>..................] recovery = 14.7% (432694060/2930135040) finish=440.2min speed=94548K/sec
bitmap: 0/22 pages [0KB], 65536KB chunk
fsck.ext4 /dev/md0 did not resolve in any filesystem tho get errors
If you create a new array, the filesystem and files are gone.
Oki , i learned something atleast.
I workt out what exakt drives that had bad superblocks.
I also found out how to display copies of superblocks on each disks.
Tries to fix/repair Them .
But Did not got any luck , but Its abit like investigating
I think that omv Did not like that i had feernas installed on the disks .
Because 2 reported as zfs members and i Did not enable that in omv.
the last command i was hoping to fix part of the problem , but i think it fuxurd the filesystem
The last command on the screen in that picture , i Should say
Question : is there away to get what you had in the recyclebin on omv.
I empty IT by mistake .
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!