February 16, 201610 yr All, I had a catastrophic failure on my array last night - Plugged a drive into a (as of the time) unused backplane on my Norco 4224 and POP - system shuts down, all my drives are dead. This is the _second_ time this has happened - they sent me a whole new set of backplanes and i replaced the power supply - still dead. Complaints about norco aside, it looks like it's just the drive controllers that are dead. I replaced the controller of a dead drive with the controller of a "living" one, and the drive spins up but when i try to attach it to a linux box, the drive doesn't mount. Loading it up in GParted on a ubuntu live CD spits out a "Can't have a partition outside the disk!" error. If i click "ignore", the drive doesn't mount and when i click on it for details i get the screenshot here: http://imgur.com/BlL2Lmo I tried manually mounting it at the command prompt, but it spits back that the drive has a "bad superblock". When i run xfs_check, it tries to look for a secondary superblock and can't find one. The question here is, am i hosed? Are there more steps i can take? It looks like the data is still on the drive, i just currently have no way to access it. Normally i wouldn't care but there are some pictures of my son on there that i'd love to get back.
February 16, 201610 yr Community Expert I believe you can’t replace just the controller, eeprom has to be switched from old disk.
February 20, 201610 yr This may not help with the data recovery, I had an XFX Pro modular power supply that had the wires swapped going into the molex connector. When I tried plugging it in to an empty backplane, the backplane got cooked and the computer would power up and reset endlessly. Now I check they all match before I use them Norcotek replaced the backplane for me, but XFX never replaced any of the modular wiring for the power supply. When a coworker without a surge protector came to me after a bout of lightning ... I helped them with finding replacement controllers off ebay and when they swapped the eeprom it worked long enough for recovery It was our Maintenance Supervisor ...
Archived
This topic is now archived and is closed to further replies.