July 18, 201411 yr Help disk 4 when disabled again with 4 write errors and I can't find anything wrong with, also there is nothing on the disk yet. It is running on a brand new LSI 9211-8i and cables, last time it went disabled it was on a different 9211-8i and cables. Since I had nothing on disk 4 yet I removed the drive from array using new config and started a parity sync, I had already started a preclear of a new refurb drive I just got back a few hours early, and I started testing disk 4 using WD disk tool. The WD disk tool has completed both short and extended test successfully. Test Option: QUICK TEST Model Number: WDC WD30EZRX-00MMMB0 Unit Serial Number: WD-WCAWZ1424060 Firmware Number: 80.00A80 Capacity: 3000.59 GB SMART Status: PASS Test Result: PASS Test Time: 01:22:26, July 18, 2014 Test Option: EXTENDED TEST Model Number: WDC WD30EZRX-00MMMB0 Unit Serial Number: WD-WCAWZ1424060 Firmware Number: 80.00A80 Capacity: 3000.59 GB SMART Status: PASS Test Result: PASS Test Time: 09:49:21, July 18, 2014 I am uploading a syslog that I had to edit to get size down but I only deleted successful movers and a bunch of duplicate stuff at the end. I am also getting this error in the command prompt. REISERFS abort (divice mdq): Journal wite error in flush_commit_list REISERFS abort (device md2): Journal write error in flush_commit_list Looking at these errors it seems to be on my parity disk and disk 2 according to the log. but these might be because I pulled a few disks out to test if they were properly spundown. My last LSI card was not flashed to IT mode and was not spinning down disks even though the web interface said they were. So this new card I flashed to IT and I wanted to know if the disks were actually spundown. This is the system that I am running it on. According to my UPS I am running at 270 watts and this is between my server and main desktop. This is with my server running a parity check with 5 disks, and 1 disk preclearing. OS: ESXi 5.5 on SSD unRAID: 5.0.5 Power supply: 650w Seasonic with a single 12v Rail Hard Disks: 7 red and green WD drives on LSI 9211-8i syslog.zip
July 18, 201411 yr Author Here is the other half of the smart info. I couldn't add it to the other post.
July 18, 201411 yr What does this mean? I pulled a few disks out to test if they were properly spundown Did you disconnect the drives without stopping the array?
July 18, 201411 yr Author What does this mean? I pulled a few disks out to test if they were properly spundown Did you disconnect the drives without stopping the array? Yes, as I stated before with my last card they were not spinning down and caused my last problem. With the last card if I stopped the array they would spin down if I did not they would not spin down but unRAID would claim they are. So the only way that I could test if the drives were actualy spun down was to actualy hold the drive while the array was started. I understand that this should not be done under normal conditions. I made sure that all drives were not being written to and unRAID showed them as spun down. Since disk 4 was empty and I was not going to be put back in the array till I can confirm the disk was bad, I knew that I was going to be creating a new configuration and do a parity sync. The original LSI card was not flash to IT mode and was not really spinning down drive while array was online and caused my parity drive to go bad as well as another disk go disabled. I was unaware that the drives were not really spinning down and I didn't want a repeat, so that is why I did this and would not have if I was worried that I would lose anything important. All I have on my server is blue rays that I own and secondary backups, primary backups are off site. My array is currently under a new configuration and running a parity sync with all drive showing green smart status. What I would like to know is what caused disk 4 to go disabled again since it is on a new card and cable. Also the last time when I had disk 4 go disabled the parity disk showed green but what making noises and when I restarted the drive would not get discovered by the LSI card or any other computer's UEFI/BIOS. Disk 4 turned out to be OK as far as Smart tests and Preclears go. Both the Parity drive and disk 4 turned out to be the only 2 WD green drives in the system. This time disk 4 went disabled it was the only green drive in the array because I replaced the parity with a brand new WD red drive. I may just replace disk 4 also with a red drive.
Archived
This topic is now archived and is closed to further replies.