muntedewok

Decided stuff it. Pulled the drives and SATA RAID card out of the existing platform and stuffed it into a spare ML110 G8 I had sitting around collecting dust, tested USB key first, booted no issues, installed drives (using built in backplane controller as well as SATA RAID card w/ SATA breakout cables), existing drive configuration OK, installed "troublesome" Disk5 (the 3TB WD Red from last few diagnostic runs) and rebuilt correctly. Putting this down to either faulty motherboard or PSU however not going to bother trying to diagnose that issue..... suspect one or the other but both are getting on a bit.

Don't believe it's the miniSAS RAID card fault as the issue still happens even with drive connected directly to motherboard. Going to have to start considering either motherboard or PSU issues overall and swap them out. Hell, I've even switched SATA cables from working drives to the replacement drive slot with same issue. Before I begin tearing it down though looking for issues, do you think it'd be worthwhile creating a new configuration first and importing all the drives back in?

Same outcome for at least 5 drives now? Drives are all passing SMART tests, no disk errors. Drives never stops spinning, you just watch the transfer rate creep down for no reason then suddenly there's errors and the drive drops out of the configuration.

tower-diagnostics-20221025-1434.zip Unfortunately same issue with new SATA cable plugged directly into motherboard / different SATA power cable as well

Hi JorgeB, which disk is logged as the problem? Disk4 or Disk5? I might add I previously had various drives in the position of "Disk5" connected to either motherboard or SATA RAID controller on various SATA breakout leads. Cheers, -Chris

Hi guys, Have an issue with Disk5 on this array. It'd been working flawlessly for years, replacing a drive every once in a while. Recently Disk5 has been dropping and I've been replacing it with known good drives. Some will rebuild OK and others won't, it'll start then fail for no reason however the SMART data appears fine. I thought this might be a cabling issue so I've used many different data and power cables for the drive(s) being used for that slot, to no avail. Today I decided stuff it and went and bought 2x 3TB WD drives (1 as a spare) however now I'm having EXACTLY THE SAME issue with these drives and it's doing my head in. Not sure what's happening, next I might need to start considering the SATA RAID controller is on the fritz? Diagnostic logs attached. I suspect there MAY be an issue with Disk4 which is causing issues with the rebuild as well though haven't been able to confirm. I'm not particularly worried if I drop Disk4 but it's read/writable so I can move the data off this drive onto another for the time being...... Any help or insights greatly appreciated. -Chris tower-diagnostics-20221021-1608.zip

Apologies, will do!

Hey guys, Was just about to post the same thing. Since 1.18 was released I can't get the server to start. Spent a while diagnosing the issue and have determined it's as others have mentioned here, the version of Java inside the docker is not up to date. Anyone have an update as to when an update is going to be released for this? Cheers, -Chris

Very strange it's getting a different identifier for the same disk, I'd have thought it'd generate an identifier for a disk based on its serial number and not change? Oh well. I've got another cable to test with. Reckon it's worthwhile removing the existing config and creating a new one with the same disk configuration? Cheers, -Chris

Ok, so this is really starting to annoy me now. Disk 4 has dropped again and was reporting unmountable, so stopped array, rebooted, disk was there, start array again and it's rebuilding the disk. No idea why. This is the brand new disk I'd previously reported I was using. It's supposedly successfully rebuilt into the array several times now, and just keeps dropping off and being forgotten. This disk is also using the SAS -> SATA breakout cable again which I suspect may be faulty. Worthwhile replacing cable or is there anything else this could be? Cheers, -Chris tower-diagnostics-20190609-1502.zip

I'm finding that the settings aren't quite similar to the settings I configure on say HP MSA 2052 SAN arrays yes....... As for the cache setting itself, the setting is enabled for all of the shares. Is this what you mean? Cheers, -Chris

That would probably make sense then. Downloads folder is configured to use cache drive as well at the moment. With regards to the rebuild comment, being that I wasn't sure if it was supposed to be using all the disks in the RAID, I was going to delete the share and re-create it with all the disks in the RAID. Cheers, -Chris

Fair call as well, hadn't factored in the fact Disk 2 had a corrupted rebuild. Disk 4 has rebuilt into the RAID array OK, lost about 4TB worth of data however it was only movies and I have a log of all that was in there anyway so no big deal. Shares are showing correctly as being protected with exception to the appdata and Downloads folder, which if I view the folder structure, are showing different disks being used (single or multiple disks) for each folder. I'll probably just rip these out because they're small in size, rebuild the share then move the files/folders back in. Thank you very much for assistance on this Johnnie, greatly appreciated. -Chris

The interesting thing being that even though the write count is going up with the rebuild (now at 12% and 857,688 writes) the data count isn't increasing. I'm wondering if the parity that was available for the drive previously is hosed... -Chris

Managed to get it to mount this way. Started RAID with drive 4 unassigned, and performed format on it. Then dismounted RAID, then selected drive and mounted again. Now it says it's rebuilding RAID however it's back at the point where it's only showing 33.6mb on the drive. New logs uploaded. Thanks, -Chris tower-diagnostics-20190521-1539.zip

Just downloaded the unassigned drives plugin, going to run a pre-clear on the drive and see what it does afterwards. -Chris

New logs uploaded, unfortunately no dice on the format! -Chris tower-diagnostics-20190521-1506.zip

Is there a way to format it while it's in the server still? I've only got remote access to my server at the moment from my office -Chris

Hey Johhnie, Disk 2 has rebuilt OK and as predicted lost a heap of data, not too fussed about that easily recoverable from elsewhere, the shares have come back up correctly and data visible in the network mapped volumes now, all good! However, I've replaced the stuffed Disk 4 and it's complaining that the new disk is unmountable. I removed it and plugged it into my PC, used diskpart to clean the drive of all partitions etc and re-inserted it into the server. However when I start the volume again it's complaining the drive is unmountable even when I force a format on it. I've uploaded the latest log files if required. Kind regards, -Chris tower-diagnostics-20190521-0840.zip

No worries thanks for the heads up. I'll check on it in the morning and kick off the rebuild of Disk 4 as well, will take a good 6-7 hours or so judging by the last effort. Thanks for the assistance and hope it goes well! -Chris

Probably explains what all this is then: init_source_bitmap: Bitmap 14882 (of 32768 bits) is wrong - mark all blocks [487653376 - 487686144] as used init_source_bitmap: Bitmap 14883 (of 32768 bits) is wrong - mark all blocks [487686144 - 487718912] as used Looks like it's going to take a while...

5 found corruptions can be fixed only when running with --rebuild-tree Think it might be told to hold onto my balls!

Did you want me to post the outcome of the check or run a specific command against the drive as well? -Chris