Juscuz17

Cloudflared is restarting. I will have to uninstall/reinstall it and see if that fixes it. I will pull the drive tonight and put it in the drive shelf. I am starting to think I like the drive shelf better than the mess of wires in the case....

I have 4 of these, and 2 of them have already failed. Is this a hardware fail? Screen shot and diagnastics attatched. schmittnas-diagnostics-20260601-1224.zip

On the right side of the image where it says streams. here is screenshot after I moved the backup share and restarted docker. The streams from the dockers are now running on the appdata share where they are supposed to be. In the other image they are running off the backup share.

That's from the Dashboard. OK so I see what you mean, I originally had a folder in the pool backup. When I lost the disk and you helped me through getting back online I remember an error and I changed the location in app backup from backup/backup to just backup. that explains that part.

I have no idea why app data backup is creating a share. it is set to back up to a pool called back up. Today I looked and the back up has 40 streams connected to it and appdata has none. Any idea what the heck is going on?

I am getting this error. Any idea what I need to do? [Error] SonarrErrorPipeline: [POST /api/v3/series] [v4.0.17.2952] code = Corrupt (11), message = System.Data.SQLite.SQLiteException (0x800007EF): database disk image is malformed database disk image is malformed

Plex still is not responding. I restored the whole docker, then updated it. it will start but the web ui says cannot connect.

schmittnas-diagnostics-20260407-1739.zip

I will as soon as I get home. I cannot do that from work.

That is failed disk9. I moved it to a pool to see if I could get any data off it. I cannot. So I just haven't removed it yet.

schmittnas-diagnostics-20260406-1741.zip OK, the mover ran for a split second, then stopped. Docker and VM manager are disabled.

The button was only grey for a few seconds, but the log only said start mover, never mover ended or anything. I will be home in bit, I will triple check everything you told me and run the mover again and note how long the button is disabled. There isn't much to move right now, so it won't take long.

Mover is scheduled to move every night at 0300, I manually initiated it, and came back and there was no activity on any drives so I ran diag and posted it. that was about 11pm. the mover would have automatically moved anything at 0300 also, so I posted another diag a bit ago after your post. I made sure docker was shut down and invoked the mover again. I will check in when i get home and see what the log says.

I ran Mover waited a while then ran Diagnostics. Here is a fresh pull. schmittnas-diagnostics-20260406-1352.zip

schmittnas-diagnostics-20260405-2317.zip

OK! I also have a current APP Back up.

OK, that's what I thought. I am I correct that I cannot move anything till parity is done?

I have to wait 8 hrs for the parity sync to finish to run mover, I did everything else. Thank you! I will post as soon as I can. App Data was set to cache only.

Her e is a fresh diag. schmittnas-diagnostics-20260405-1149.zip

I don't even know where to start. I added a second parity drive and my older parity 1 failed. I had a disk in the array that had no data written to it so I shut down the array, moved the drive to parity, and ran new config. at about 90% drive 9 completely failed. I shut down the server, checked all cables and restarted it. Drive 9 definitely failed. I shut down the server and replaced drive9(yes I know total data loss) with a spare. after restarting the server everything was ok, BUT my shares are there, but all the share info is not, and my dockers don't work. I am at a loss. I will attach diagnostics. This was after I rebooted it, I will add a post with fresh diagnostics too. dual parity is currently rebuilding with 8 hours to go. schmittnas-diagnostics-20260404-2231.zip

I am going to mark this solved. I simply returned the drives.

I may try this tomorrow, They have agreed to take them back for a full refund. I don't know if that route would help because the server sees them, but I can't do anything but view logs. I can't even try to format them. All the buttons are grey.

These are 2024 HPE SAS drives I just bought. 2 drives both do the exact same thing. They are in an EMC Drive shelf with 6 6TB SAS drives that work fine. Feb 7 17:44:40 SchmittNAS emhttpd: device /dev/sdr has size zero Feb 7 21:05:23 SchmittNAS kernel: sd 11:0:14:0: [sdr] Spinning up disk... Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] Sense Key : 0x2 [current] [descriptor] Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] ASC=0x4 ASCQ=0x22 Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] Sense Key : 0x2 [current] [descriptor] Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] ASC=0x4 ASCQ=0x22 Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] 0 512-byte logical blocks: (0 B/0 B) Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] 0-byte physical blocks Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] Test WP failed, assume Write Enabled Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] Asking for cache data failed Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] Assuming drive cache: write through Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes) Feb 7 21:07:03 SchmittNAS kernel: sd 11:0:14:0: [sdr] Attached SCSI disk Feb 7 21:07:05 SchmittNAS emhttpd: device /dev/sdr has size zero schmittnas-diagnostics-20260208-1041.zip

Update: I upgraded to 7.0.1 and so far its stable and running.

I replaced The Ram with Brand new. I am starting to think its a motherboard issue. This server has run perfectly until recently. I thought it was the flash drive because I had a flash drive unresponsive error. so I changed that and it was better for a few days. The I changed the RAM and it seemed better... Now its back to doing it again.