Heya all, 

Longtime UnRaid user without to much complexity.

Current system has a mix of xfs and reiserfs disks.

 

I'm in the process of replacing a couple disks. First disk I replaced was a 2TB reiserfs disk that I cleared off all data via unBalance, then converted to xfs, then replaced with a new 8TB.

Great, no problems. Parity completed, no complaints.

 

I also had a 5TB xfs disk that was starting to show some errors, so I did the same process (although there really was no need to move the data off since it was already xfs....oops) and replaced it with a 6TB disk.

Upon powering back on, I assigned the new drive to the appropriate slot and started it up. I noticed parity stalled a bit at 1%. I also at that point noticed that "Total size" on my Main page was showing 6TB.

My parity drive is and has been 8TB. 

 

This total size should show 8TB, shouldn't it?

 

I got a little concerned so I tried to pause the parity-sync/data-rebuild. There seemed to be no response. 

I went to a different PC and tried a couple things. No response, webUI just hung.

 

I then killed the power and replaced the new 6TB drive with another 6TB drive. I also checked all the cables. Both new drives had already been pre-cleared via Preclear Disks plugin.

After replacing the drive again and powering on, I got the same result.

Total size is showing as 6TB.

 

I could be completely off my rocker and that's normal & indicating the size of the drive being rebuilt, but I wanted to make sure, so I've paused the parity-sync/rebuild immediately at 0% to make sure.

 

Attached is diagnostics.

 

Am I crazy or something not right?

 

Thanks!

tower-diagnostics-20201230-1803.zip

Edited December 31, 20205 yr by ms_1
solved

Apparently something happened to Sonarr docker as well.

I was checking my active dockers, and webUI for Sonarr didn't load. Log shows the following.

(I tried grabbing diagnostics again and it's just hanging now...not doing anything)

 

Dec 30 19:07:39 Tower nginx: 2020/12/30 19:07:39 [error] 8688#8688: *14852 open() "/usr/local/emhttp/plugins/resource.monitor/javascript/w3.js" failed (2: No such file or directory), client: 192.168.1.119, server: , request: "GET /plugins/resource.monitor/javascript/w3.js HTTP/2.0", host: "tower.local", referrer: "https://tower.local/Docker"

Dec 30 19:07:39 Tower nginx: 2020/12/30 19:07:39 [error] 8688#8688: *14852 open() "/usr/local/emhttp/plugins/resource.monitor/javascript/w3.js" failed (2: No such file or directory), client: 192.168.1.119, server: , request: "GET /plugins/resource.monitor/javascript/w3.js HTTP/2.0", host: "tower.local", referrer: "https://tower.local/Docker"

Dec 30 19:10:13 Tower nginx: 2020/12/30 19:10:13 [error] 8688#8688: *15092 open() "/usr/local/emhttp/plugins/resource.monitor/javascript/w3.js" failed (2: No such file or directory), client: 192.168.1.187, server: , request: "GET /plugins/resource.monitor/javascript/w3.js HTTP/2.0", host: "tower.local", referrer: "https://tower.local/Docker"

Dec 30 19:10:13 Tower nginx: 2020/12/30 19:10:13 [error] 8688#8688: *15092 open() "/usr/local/emhttp/plugins/resource.monitor/javascript/w3.js" failed (2: No such file or directory), client: 192.168.1.187, server: , request: "GET /plugins/resource.monitor/javascript/w3.js HTTP/2.0", host: "tower.local", referrer: "https://tower.local/Docker"

7 hours ago, ms_1 said:

I could be completely off my rocker and that's normal & indicating the size of the drive being rebuilt,

It is normal.

Thanks JorgeB.

Marking this as solved as I apparently focused on the wrong issue.

Looks like I had some plugin that was causing issues since I finally had to restart in safe mode to get things to not stop becoming unresponsive after a few minutes.