octhrope

This is great information and thank you for writing all of it for the community at large. For me i think im out of options, i guess the lesson is learned. Unless you have any other suggestions? Thank you for all your time and energy on this, I really appreciate all the information and assistance. Wouldn't have made it this…

moved the drives around. none of the commands run now, tells me the resource is busy. but there is an md1? mdadm: No devices given.~ # mdadm --detail /dev/md2 mdadm: cannot open /dev/md2: No such file or directory ~ # mdadm --detail /dev/md1 /dev/md1: Version : 1.2 Creation Time : Mon Oct 16 18:22:38 2017 Raid Level :…

none of the commands run, says the resources are busy. looks like the end. unless it was a raid 10, i dont remember...

far left (1) was the original offender. far right showed blank after the whole thing fell apart and i started trying to recover. i think they might be in there backwards at the moment though. disk 1 is in disk 4s spot. Ill swap them around

Commands failed but maybe this is promising? The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an…

Doesnt look good: ~ # vgscan Reading all physical volumes. This may take a while... ~ # lvscan -a ~ # vgscan Reading all physical volumes. This may take a while... ~ # lvscan -a ~ # vgscan Reading all physical volumes. This may take a while... ~ # lvscan -a ~ #

awesome. done. this isnt going to wipe anything? its asking to setup a new volume. i did a reboot without creating a volume, its beeping again. a good thing? =)

a drive was throwing an error and it asked me to replace it so i did and it was copying the data. i let it run for 24+ hours and then i was unable to login or see the shares. so i waited a bit longer and then rebooted. Then it came back in this state. so whatever happened took place at my time midnight, based on your…

i do have a sd card in there i was doing testing years ago and forgot about it. fans working, one drive is on its last leg, i have a new set of disk to replace after data recovery. Yeah that was the day the system hung, i was attempting to rebuild the array. but i couldnt access the system and around UTC 2:00 i manually…

~ # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : inactive sdc3[1](S) sde3[4](S) sdd3[2](S) 5848151040 blocks super 1.2 md1 : active raid1 sde2[4] sdb2[5] sdd2[2] sdc2[1] 1998784 blocks super 1.2 [4/4] [UUUU] md0 : active raid5 sdd1[0] sdc1[3] sdb1[2] sde1[1] 5990400…

/ $ cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : inactive sdc3[1](S) sde3[4](S) sdd3[2](S) 5848151040 blocks super 1.2 md1 : active raid1 sde2[4] sdb2[5] sdd2[2] sdc2[1] 1998784 blocks super 1.2 [4/4] [UUUU] md0 : active raid5 sdd1[0] sdc1[3] sdb1[2] sde1[1] 5990400…

i may have jumped the gun... i started following some of your older post with similar issues. at the moment i am attempting to recover data using software. but its hit and miss. ill follow up after it completes as the drives are in use. 

Outputs requested in previous posts. ~ # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : inactive sdc3[1](S) sdb3[4](S) sdd3[2](S) 5848151040 blocks super 1.2 md1 : active raid1 sde2[5] sdb2[4] sdc2[1] sdd2[2] 1998784 blocks super 1.2 [4/4] [UUUU] md0 : active raid1 sde1[5]…