ReCoN

Members
  • Posts

    53
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ReCoN's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Initially only one drive showed as disabled, I presume this drive has failed. The 2 that are missing only showed up as missing once I swapped connections to rule out a bad connection. Could that cause a drive to fail? If we presume the disks have failed is it a case of switching in new drives then rebuilding? Could data be recoverable from the failed disks?
  2. So, I have now removed all the hard drives from the hotswap bays and connected them directly. Also i have booted straight into unraid in a non virtualised environment. The 3 drives (2 missing one disabled) still showed as missing and disabled. I then switched the cables with devices known to be working and also tried connecting directly to the motherboard this didnt resolve the issue. The drives also did not show up in the bios when connected to my workstation. I have attached a syslog of the drives connected directly to the hard drive controllers and running unraid without esxi. syslog-2014-12-30.txt
  3. I have now connected the missing and disabled hard drives directly, I.e not in the hot swap caddy and they still showed as missing. I then swapped them in the hot swap bay with 2 other drives and booted the system. There was no change in visible disks. I then added the 2 drives connected outside the hotswap bays into the empty spots and both are showing as missing giving 3 missing and one disabled. I am completely pulling my hair out over this. Really appreciate any help!
  4. That is correct. I actually hadn't reconnected the cable correctly to the second m1015 card so I reconnected that and the 2 missing drives showed up leaving just the original missing drive and the disabled drive. Firstly I noticed one drive was showing as disabled so I switched it with another in the same hot swap bay to eliminate it being a cable problem. What happened was the the disk still showed as disabled and the drive put it its place is now missing. Wherever I move these 2 drives the devises that take their place show as missing and the disabled drive remains disabled. I have tried switching all the cables around
  5. Yes the whole thing was shut down. I have attached it anyway. syslog-2014-12-27.txt
  6. My array was showing a disabled disk, unfortunately I rebooted before taking a syslog. Whilst I was checking the cables and re connecting them an additional drive showed up as missing. Now I have 3 drives showing as missing and one as disabled. What can I do to start rectifying the situation?
  7. It would seem that everything is in order, there have been 0 errors since resetting the server. In the event that there is a file corruption I can just re-rip the movie onto the server; although smart reports seem to say that everything is fine! Thanks to all who took the time to help me out, much appreciated. /solved
  8. After a busy weekend, I have followed the suggested steps an my array is now back online all drives with the green light next to them. I completed a non correcting parity check and it found 0 syncing errors. However the parity drive is showing 768 errors, should this be of concern?
  9. Yes I checked before running it: DISK_DSBL /dev/md2 /mnt/disk2 /dev/sdc WDC_WD20EARS-00MVWB0_WD-WMAZA4840105 Yes ofcourse, I have also swapped the drive into a different hotswap bay incase there were any cable issues.
  10. I tried doing a SMART test that way and it worked, I have uploaded the results. Does this make the problem apparent? Could I remove the problem disk and rebuild then re-add it?
  11. Ok, so the disk is online; does that mean it hasn't failed? Why does a S.M.A.R.T test fail? Are there any obvious next steps?
  12. fdisk /dev/sdc returns the following: Warning: DOS-Compatible mode depreciated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u').
  13. "unable to open /dev/sd2" So the disk is not online. I tried this for multiple disk and they all returned the same error, it occurred to me you may have meant /dev/md? So I tried that too and have attached the results
  14. I can still access the disks contents, I suspect that could just be simulated by the parity drive. I'm pretty sure the disk spins up as it should.