wdpaynter

root@MEDIA-SERVER:~# ls -lah /mnt/user0/appdata total 4.0K drwxrwxrwx 1 nobody users 191 Nov 7 2024 ./ drwxrwxrwx 1 nobody users 74 Mar 19 20:10 ../ drwxr-xr-x 1 nobody users 28 Aug 20 2024 Kometa/ drwxr-xr-x 1 nobody users 50 Nov 7 2024 Plex-Media-Server/ drwxr-xr-x 1 nobody users 273 Nov 7 2024 Posterizarr/ drwxr-xr-x 1 1000 users 4.0K Jul 23 2024 TinyMediaManager3/ drwxrwxr-x 1 nobody users 26 Oct 10 2024 binhex-krusader/ drwxrwxr-x 1 nobody users 67 Apr 5 2025 binhex-lidarr/ drwxrwxr-x 1 nobody users 48 Mar 31 2025 binhex-radarr/ drwxr-xr-x 1 nobody users 100 Aug 30 2024 overseerr/ drwxrwxrwx 1 nobody users 52 Sep 14 2024 plex\ (old\ linuxserver)/ drwxr-xr-x 1 root root 28 Nov 7 2024 posterizarr/ drwxrwxrwx 1 nobody users 290 Jul 15 2024 radarr/ drwxrwxrwx 1 nobody users 43 Jul 13 2024 sabnzbd/ drwxrwxrwx 1 nobody users 48 Apr 16 2025 sonarr/ drwxr-xr-x 1 nobody users 62 May 17 2025 tautulli/ drwxr-xr-x 1 root root 63 Aug 21 2024 tdarr/ root@MEDIA-SERVER:~# ls -lah /mnt/cache/appdata total 736K drwxrwxrwx 1 nobody users 210 Mar 5 16:29 ./ drwxrwxrwx 1 nobody users 90 Mar 19 20:10 ../ drwxr-xr-x 1 nobody users 344 Mar 20 10:00 ErsatzTV/ drwxr-xr-x 1 nobody users 12 Aug 20 2024 Kometa/ drwxr-xr-x 1 nobody users 32 Nov 7 2024 Plex-Media-Server/ drwxrwxr-x 1 nobody users 8 Oct 10 2024 binhex-krusader/ drwxrwxr-x 1 nobody users 356 Mar 20 10:07 binhex-lidarr/ drwxrwxr-x 1 nobody users 356 Mar 20 09:55 binhex-radarr/ drwxr-xr-x 1 nobody users 50 Mar 5 16:29 channels-dvr/ drwxrwxrwx 1 nobody users 18 Jul 13 2024 sabnzbd/ drwxrwxrwx 1 nobody users 112 Mar 20 10:02 sonarr/ drwxr-xr-x 1 nobody users 32 Mar 20 10:12 tautulli/ root@MEDIA-SERVER:~#

root@MEDIA-SERVER:~# du -h -d 1 /mnt/disk12 16T /mnt/disk12/Mediastorage 150M /mnt/disk12/appdata 16T /mnt/disk12 root@MEDIA-SERVER:~#

root@MEDIA-SERVER:~# ls -lah /mnt/disk12 total 0 drwxrwxrwx 4 nobody users 41 Mar 19 20:10 ./ drwxr-xr-x 26 root root 520 Mar 19 20:08 ../ drwxrwxrwx 3 nobody users 19 Jul 15 2024 Mediastorage/ drwxrwxrwx 8 nobody users 146 Nov 7 2024 appdata/ root@MEDIA-SERVER:~# Regarding doubling up of the shares; Not sure this is relevant (or accurate), but I think sometime early on I read about backing up appdata onto the array and attempted to do so. I beleive I did it incorrectly and someone on this forum (perhaps you or JorgeB) pointed it out. I think we changed the setting(s), but this may be a result. How do I clean it up? EDIT: when I manually browse the individual disks, I notice that disk12 has (6) container folders in appdata and others have (8)

I will run the command in the morning and report back. Thanks for your help!

Here is new diagnostics. Oddly, server booted and array started faster than normal. Thx media-server-diagnostics-20260319-2010.zip

Well during dinner our neighborhood power went out. It was only out briefly, but server shut down (hoping the UPS did its job). I guess I'll swap PSU now unless you think I shouldn't

My shares disappeared during the rebuild. I thought maybe it was because of all the errors on those other drives.

Sorry, I was gone for a bit. Diagnostics attached. Rebuild is complete, and disk shows not emulated/disabled, but the notifications point out all the errors. I will wait for instruction before powering down to install new PSU and cables. Thx! media-server-diagnostics-20260319-1509.zip

I've refreshed the webGUI and its back up. Not all my shares. The rebuild of the drive was running, as it shows about 1hr 45mins left. Are all the read errors with the other drives affecting the rebuild? Or just my she=ares and my ability to run the container/apps? Hoping I can shutdown after rebuild, install new PSU and boot without further read errors...

yes, and a kvm switch from my office desktop. When I click over, I usually see command line, but do everything from the WebGUI on PC. Now there's nothing on either

I don't know how, as I cannot see the WebGUI nor the command line

So I started rebuilding the drive. It is 18TB and it takes about 2 days to rebuild. Everything was going good until it got to 60-70% completion and the same drives with the power issues began exhibiting read errors (one of the drives had LOTS of errors and growing. The other ones on that same connection had relatively small amount and didn't seem to be increasing. It kept rebuilding and got to about 80% and only 3-4 hours left, and I lost all shares and cannot access the webGUI nor directly switching my monitor to the server (connected via HDMI). Guessing it was the high number of read errors on that one drive? I can here the server making noises similarly to when it was rebuilding Not sure what to do: wait the 3-4 hours and then how do I power down safely (I can;t see anything to initiate it) power down now, replace PSU, boot up and start the 2 day rebuild again (if I even can). Again, not sure how to safely power down quick press of power button on server case? Makes me nervous unplug server power cord and hope my UPS settings work accordingly (doesn't seem likely with everything else not working) some other alternative? If ya'll could provide any guidance, it would be appreciated. Thanks

Ok, thanks!

As I am rebuilding the drive onto a new one, I am curious if I can reformat or perform another task that will "skip" the bad sectors and allow me to use the drive again by pre-clearing or whatever. Or is this asking for trouble? It is a 18TB HDD and only two years old. Hard drives are pretty expensive right now too Sorry, not that well versed in these things.

No problem. I really appreciate your help! BTW (and for anybody that may come across this thread) I found a power supply that has plenty of ports/cables to allow for only (4) per SATA cable: https://www.amazon.com/dp/B0BP8BJ7X4?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 It has a minimum of (5) SATA ports that can have (4) SATA connections per cable. I believe it comes with three or four of those cables and I will purchase the additional ones I need from Corsair as it is modular. They also have a model that has traditional (not side) connections Thanks- Bill

I did mention it above after I ran it, but no big deal. I will replace that drive with the extra one I have. Thanks

Here is latest diagnostics. No errors with the disks 1,2,3 & 4 (yet). How do I handle the disk12 issue? Should I try new config now? Or put in my extra 18TB HDD and rebuild that drive? I thought I read that a relatively small amount of bad sectors wasn't a big deal. Only if it was growing substantially media-server-diagnostics-20260316-1643.zip

I have rebooted after moving cables I wondered the same, but others guided me to choosing this PSU. I believe we used a calculator that conveyed that I had more than enough power. I'd happily purchase a more powerful PSU and/or one with addiitonal connections if I could find some guidance. I don't have experience with this I am afraid.

Oh, I meant small/temporary amount of data loss. I do not want to reduce to 1/4 the amount of current. Are there PSU's that have (3-4) dedicated Molex cables? I try to search, but results only show number of connections, not "cables". It is strange to me that I have no issues for weeks or months at a time and then all of a sudden...I used to have my server in a 4U Norco case with 24 drives and a similar power supply and never had issues. I ran Windows and not unRAID, but zero power issues (unless PSU needed replacing). Are you certain that this is the issue? I read that many people have 18+ drives. How would they be powering them if not for using splitters? Thx

Do I need a different power supply? What can I do to get my shares working again in the meantime? Not super concerned about data/file loss, as this is simply a media server.

see attached. Thanks media-server-diagnostics-20260316-1301.zip It looks like disks 1,2,3 & 4 have errors even after re-seating cables. All (4) are on the same Molex splitter from same PSU cable

Ok, thanks. It says "Completed: read failure". where can I obtain the full test results to attach?

I shutdown and re-seated the cables to those drives. Upon boot, I see that disk12 is still disabled and emulated (before starting the array). Should I simply start the array and rebuild that disk onto itself or do a New Config with the drives in their same spots? Thx Diagnostics attached (have yet to start array) media-server-diagnostics-20260316-1203.zip

Got it. Rebooting now. Thx!