mathomas3

for reference I was recently running 13 hdd and 2 ssds on a 1200watt psu and a low power GPU... but like you, years ago I had a 450? watt(ten years ago) psu running roughly 6 hdd and I had something close to what was said here... Glad it's fixed

Let me think about what you have said and try to understand it better... what you have said has raised a few questions to the operation of the cache... and while I would agree that mover might not move data from disk 8 to the new services disk pool... I would think it would move data from the cache...

tower-diagnostics-20220802-1946.zip Sorry for the delay. I ended up driving to a wedding and back... 1200 miles round trip. When I was trying to use mover to relocate data, everything was disabled and rebooted to ensure there were no file access issues... After leaving it over night it was still far away from where it needed to be... ended moving things by hand to where it needed to be and thus far it seems OK... The cache needs to be cleaned up though... I still have to pull one 265gig drive from there and add it to new disk pool. From what I have read this isnt something that can be done without wiping out the cache system again? My plan once I got back was to disable everything again and try mover(or by hand) once again... remove the cache setup... move the 256 to the disk pool and rebuild the cache with the single 1tb drive... and re-enable services

ended up doing a hard reset... everything seems fine

Seems like I keep getting myself into trouble... While attempting to get the cache setup with the 1tb drive I tried to let mover clear off the data, which didnt work. So I ended up unassigning one of the cache drives and assigning the 1tb in it's place. I waited for a bit for the btrfs process to complete and validating that by using btrfs fi usage -T /mnt/cache and when everything was complete I tried stopping the array to unassign the last small drive from the cache, but I am getting the error 'umount: /mnt/cache : target busy' do I have to do a hard power off again? tower-diagnostics-20220731-1018.zip

Both drives cleared on the extended check and thus far zero errors on disk 10... I will keep an eye on that disk... Parity and disk 8 are being rebuilt now... decided to replace both of the disk with the spares that I had on hand and plan to use trurl's advise... On a side note... I have never touched the docker vdisk since it was made years ago, and I would think that I can copy/cut it to a different location and update the location via the settings page... If I were to modify the size of the disk would that corrupt the disk/image? Again thank you to Trurl for your time and quick response... Well done... JorgeB, thank you for confirming this build months ago and confirming the issues at hand...

Disk 8 just completed with zero errors... Parity drive is still at 10%

I do like that plan... Just havent took the time to get it done... The fast pools are something new that I havent touched on yet. Again thank you for the help today. The UPS needs to be switched out. I suspect that it's too small for the new hardware, on boot it beeps for a second or two due to excess power draw

last check on the 15th lasted 1day 6h avg speed was 73.7mb though that was with many dockers running... If I turn that off and run it I get up to 175mb

Yes. Everything is in the DAS(two controllers and HDDs) which then connects to the LSI card in the server. That might be what is throwing you for a loop, the dual controllers that are inside/connected to the LSI card

The short SMART test passed and I am still waiting on the extended.

If needed I have a pair of Dell Compellent that I could try in the enclosure Disk Shelf Here is the controller that I am using that should have been flashed into IT Mode LSI SAS9207-8e

Running the extended test now on disk 8

Here is a complete Main page. I have 3 disks attached and unassigned, waiting to be added to the array should the need arise

So you think both parity drives are hosed?

When you say that the SAS disks have been disconnected and reconnected as different devices... what do you mean? I didnt reassign the disks when everything was moved into the new box.

I do have a UPS. Though I need to get a larger one, Im pushing this current one on what it can handle. For power I connected 1 PSU to the UPS and the second PSU directly to the wall. Im thinking what happened is that the DAS lost power for 0.01 of a second causing the errors on the disks and since Parity and disk 8 were actively being accessed they got disabled.

Negative. Smart reports look good for the ones I have looked at.

correct. All of the drives are connected via the RAID controller When I moved everything over I had to use a different RAID controller(thought I was using a recommended one from the unraid wiki) If I recall disks 9-11 are SAS and all the rest are SATA drives

Oh and after posting the most recent Diags I disabled docker to limit writes to the array. Dont think that should effect anything, but I figure it's for the best

Before I forget to mention it. Thank you for the quick assistance. It's been a while since I have had drive failures, but never had more then one die at a time. I did recently move UNRaid into this hardware, an HP 1u Server and a 24bay DAS, both with dual PSUs. Hasn't given me any issues up till now.

faster read times while also having the data protected is what I was aiming for... though I have been considering moving it out of the array for sometime now

tower-diagnostics-20220729-1423.zip Rebooted and posting Diags. Those two disks are still red balled... funny thing is though that disk 8 is a 2 month old ssd...

As a sysadmin... that's something you tell users all the time but not something you ever want to be told yourself 🤔