dewittig

Hello ... I noticed a Red X on one of my drives. I've attached the diagnostics logs, it is disk ending in ...LDS that has the Red X. I've attempted to read through the Wiki and diagnose the problem with the SMART report, but I've not come to a conclusion. The only thing I notice is that the drive almost has a 3yr power on time. If anyone is able to identify what the problem is, I'd be interested in knowing how you came to that conclusion with the logs/smart reports. I do have a disk already precleared on standby ready to rebuild the data, if necessary. Steps I've taken so far: 6/25 - noticed Red X 6/26 - diagnostics/syslog/smart report downloads - power down server - checked cables - re-reseated all drives in chassis upon restart .... won't boot - blinking cursor in upper left, re-seated the flash drive, ended up having to go into BIOS to set usb drive as default boot device Now I am able to boot into unraid GUI / still have Red X on ..LDS drive / I have not restarted the array My system UnRaid 6.4.0 7 data drives / 1 parity 256GB SSD Cache Secondary 250GB SSD running VM's (outside of array) Motherboard - Supermicro - X8DT3 LSI9210 Controller (9 of 12 drive bays run through this controller) thanks in advance for the help, really appreciate this community forum! -Drew dwtower-diagnostics-20180626-2205.zip

It's been a while, but I finally got a new motherboard, CPU, Memory, SATA Controller card installed. I ran a Filesystem Check on all 6 disks and none came back with errors! Woo Hoo! I ran a Parity Check with the 'write corrections to disk' unchecked. It returned 124,830 errors. I'm guess this has to do with running the reiserdisk --rebuild-tree multiple times on disk1, like I mentioned in my first post. It seems like I'm on the right track, but just wanted to check on the next best steps. I'm guessing I should just write all corrections to parity, and I'll have to deal with whatever file loss the rebuild-tree process caused. I've attached my Diagnostic File, I looked through this but don't see where it says what the 124k errors are.... If you've got thoughts on next steps, it'd be appreciated! Thanks. dwtower-diagnostics-20171028-1920.zip

OK, so I thought I was onto something, based on the previous feedback. That it was hardware related, not disk related, which I still think is true, but I don't understand what it could be. I ran Memtest for a lot of hours, with no errors. I took Disk1 out and loaded it into another PC, I was able to run rebuild-tree successfully. This got me thinking that perhaps it is the SAT2-MV8 controller card in my SuperMicro server that is causing the problem. In my server I have 8 HD bays going through 1-MV8 card, and 4 HD bays, connected direct to MB. So I plugged in Disk1 direct to MB, no errors. I plugged into a HD Bay that goes through MV8, it had errors. I thought I found the problem and I have a spare MV8 card, so I swapped the cards. Same results. So I thought maybe the PCI Slot went bad, moved it to the other PCIX-133 slot on the board, same results. I thought maybe the PCI-100 slots were on a different bus than the PCI-133 slots, so I swapped the card into a PCI-100 slot, same results. Now, I thought i was going crazy so I connected Disk1 back direct to MB, and it shows no errors still. I tested with other drives. When connected through a MV8 card, they throw errors and recommend a rebuild-tree. When I plug them directly to MB, no errors. So besides jumping to the conclusion that my MotherBoard fried somehow. Is there any other explanation? FYI, here's my server specs: 12-bay Supermicro server Supermicro SAS826TQ Supermicro X7SBE Supermicro SAT2-MV8 any other ideas on what to look at next? Thanks. Disk1-Scans.zip

OK - I can try both of those things.

I am running v6.3.3 A few months ago I noticed that I had disks with file system errors. I attempted to troubleshoot them and then life got in the way. With a new baby now 2 weeks out, I’ve decided it’s time to get the server back online. The problems is a bit overwhelming for me, there are multiple disks with file system errors. I also remember, while running some of the disk maintenance before that the server would become unresponsive. I plugged in a monitor directly to server and noticed an error on the console. I can't find what that error was, and it hasn't happened in the past 2 days of re-attempting resurrection. I have a mix of XFS and Reiserfs disks. Tonight, I ran a disk check on all the drives, I’ve attached those results on the drives with errors (1,2,3,4,6) as well as a full diagnostics report. Disk5 is the only one without errors. If i had to devise a plan of action, it would likely the following: Disk1, I’ve already run rebuild-tree 4 times and the results do not appear to be making much progress. (I’ve attached all logs) / keep running rebuild-tree? Disk6, run: xfs_repair -v Disk4, locked up whole unraid during scan attempt another check. Then likely --rebuild-tree Disk3, run: reiserfsck --rebuild-tree Disk2, run: reiserfsck --rebuild-tree This forum has helped me once before with a disk issue, so I’m reaching out again before i do anything drastic (or incorrect). Unraid_08.21.2017.zip

thanks for the reply... I don't have a port multiplier that I know of... I was able to successfully preclear another drive a few days ago (WCC4N5HED88E), it was also connected through that controller.

So about a year ago I ordered a batch of WD Red 3GB drives. The first 2 have been used in Unraid and are stable, I am currently attempting to preclear the 3rd and 4th drive. One drive precleared no problem, one of the drives has crashed my Unriad 4x now when attempting to Preclear. Preclear runs for about 30min-1hr then the whole Unraid system crashes. I've attached a screen shot of the console view when the crash occurs. Every time UnRaid has to be rebooted and it runs a Parity Check automatically every time I restart it. I will also attach a diagnostics... The drive in questions is : WD-WCC4N7ZFR14R My setup. I am running on SuperMicro X7SB4, which has ESXi. Unraid is a VM in ESXi and I am using hardware passthrough to pass through a AOC-SAT2-MV8 Controller Card I have tried to preclear the drive in 2 different connections to Controller Card in attempt to rule out a loose connection / wiring problem. dwtower-diagnostics-20160413-1327.zip

I replaced parity, and it seems everything is running smoothly again. Thanks again for your help!

thanks. attached dwtower-diagnostics-20160405-1458.zip

OK, so I ran a chkdsk on the usb boot disk -- no errors I re-seated all cables and drives and booted back up the system. Now, I show Disk1 in the drop-down list, even though all the devices are still unassigned.

it is not showing up in the drop-down I have not intentionally written anything to that disk, however I have automated processes that write to Share folders so no way to be sure. I would assume that since that disk was pretty full and other are not as full, that the other disks would have received any new files.

-- Thanks for the help! -- Since I just upgraded a few days ago to v6, I don't have a backup of this drive, however I have the flash drive with v5 on it.

I took the array offline and the drive configuration disappeared. After reboot, same results. (see attached)

syslog zip, 4 of 4 seems there should be a better way to do that.... dwtower-diagnostics-20160405-1211_syslog.004.zip

syslog zip, 3 of 4 dwtower-diagnostics-20160405-1211_syslog.003.zip