July 17, 201213 yr I seem to be having problems with my drives ever since upgrading to 5. Everything is fine for a while but at some point a drive (it has happened to 3 different drives so far, one of which is brand new) decides to go missing and the icon beside it goes red. The first time it happened is when I upgraded to 5, after running reiserfsck on it and then being told to run reiserfsck --rebuild-tree that drive still wouldn't work so I assumed that the drive was broken (It was quite an old disk). So I swapped it out with a new one. Everything seemed to be working fine then for a day or so, I added another disk to the array as well at this point. Then I came home yesterday to see that the same thing had happened to my parity drive, red icon beside it and it claiming there was no device. I shutdown the machine and checked all the cables to make sure there was no loose wires or the likes. And started the machine up again the drive appeared with no problem except that I had to rebuild the parity. Which I did. Then this morning, after the parity was fully rebuilt everything seemed to be working fine until an hour ago another drive (that's 3 different disks) had the same problem, red icon beside (see screenshot of this one). The weird thing here is that I can see and access all the files on that drive in /mnt/user/disk5. And also write to that drive using the same. And df -h also returns the full size of the drives under shfs. I've attached the syslog file. Has anyone any suggestions, this is starting to drive me mad. System Specs that I can recall: 8 drives of various sizes and makers (Most are WD Green) Corsair CX 400W ATX Power Supply Intel Core i3 530 2.93GHz Gigabyte GA-H55M-S2H Intel H55 (Socket 1156) DDR3 microATX Motherboard Patriot G Series Sector 5 4GB (2x2GB) DDR3 PC3-10666C9 1333MHz Dual Channel syslog.txt
July 17, 201213 yr Just a thought, since the failures are seemingly random - when did you last run Memtest at boot up rather than unRAID? It could just be that you've got a hardware problem which is only showing up now that you're running newer software.
July 17, 201213 yr Another possibility is that by adding another drive, you put your PSU over the top and it it can't quite power all the drives if you spin them all up at once. I believe I saw that the requirement on the new seagate drives are 8W. it might be something to look into.
July 17, 201213 yr This is weird (Red-->expected, but Blue should be the same size??) Jul 17 07:58:32 EpicStorage kernel: mdcmd (1): import 0 8,48 2930266532 ST3000DM001-9YN166_S1F0J0RN Jul 17 07:58:32 EpicStorage kernel: md: import disk0: [8,48] (sdd) ST3000DM001-9YN166_S1F0J0RN size: 2930266532 Jul 17 07:58:32 EpicStorage kernel: mdcmd (2): import 1 8,16 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2537879 Jul 17 07:58:32 EpicStorage kernel: md: import disk1: [8,16] (sdb) WDC_WD20EARS-00S8B1_WD-WCAVY2537879 size: 1953514552 Jul 17 07:58:32 EpicStorage kernel: mdcmd (3): import 2 8,32 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2480277 Jul 17 07:58:32 EpicStorage emhttp: shcmd (18): /usr/local/sbin/emhttp_event driver_loaded Jul 17 07:58:32 EpicStorage kernel: md: import disk2: [8,32] (sdc) WDC_WD20EARS-00S8B1_WD-WCAVY2480277 size: 1953514552 Jul 17 07:58:32 EpicStorage kernel: mdcmd (4): import 3 8,64 976762552 SAMSUNG_HD103UJ_S13PJ90QB21621 Jul 17 07:58:32 EpicStorage kernel: md: import disk3: [8,64] (sde) SAMSUNG_HD103UJ_S13PJ90QB21621 size: 976762552 Jul 17 07:58:32 EpicStorage kernel: mdcmd (5): import 4 8,80 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZ20193091 Jul 17 07:58:32 EpicStorage kernel: md: import disk4: [8,80] (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZ20193091 size: 1953514552 Jul 17 07:58:32 EpicStorage kernel: mdcmd (6): import 5 8,112 2147483612 ST3000DM001-9YN166_S1F0HRT4 Jul 17 07:58:32 EpicStorage kernel: md: import disk5: [8,112] (sdh) ST3000DM001-9YN166_S1F0HRT4 size: 2147483612 Edit: I can't see the screenshot from work.
July 17, 201213 yr Author @S80_UK: I'll run Memtest when I get home. I last ran it a few months ago. @Johnm: PSU is what I thought it might be. But it's weird the way I can still access the data on all drives when they are all spun up, they just aren't coming into the array. @mbryanr: Drive size difference is due to the sata controller the second 3TB is plugged into, can't support over 2048.
July 17, 201213 yr @S80_UK: I'll run Memtest when I get home. I last ran it a few months ago. @Johnm: PSU is what I thought it might be. But it's weird the way I can still access the data on all drives when they are all spun up, they just aren't coming into the array. @mbryanr: Drive size difference is due to the sata controller the second 3TB is plugged into, can't support over 2048. Not weird, it is unRAID simulating the drive it has disabled.
Archived
This topic is now archived and is closed to further replies.