Hello,

I got an alert that my cache drive filled up so I was moving files with Krusader because the mover seems to take forever and only moves a few files.

Suddenly I started getting errors and disk 2 wouldn't come up in the webUI. I checked my shares and almost everything is gone, even the appdata share. The files are still on their appropriate drive but the share access is just gone.

I pulled diagnostics, but have not reboot as I worry that with the shares gone my access to the syslog history (syslog server points to store on the array) will disappear when I reboot.

I would like to fix the shares and the disk2 issue if anyone has advice. I will be monitoring this page from 4pm to 10pm central time.tower-diagnostics-20251007-1908.zip

There are what look like power/connection issues being logged for multiple disks, check all cables, especially any existing power splitters, and post new diags after array start.

Checked the power cables and splitters, everything seems fine.

Here are new diags.

tower-diagnostics-20251008-1632.zip

Edit to add after posting these I actually checked the system and my shares are back and disk2 seems to be working.

So problem resolved but I would still like to figure out what happened and how to prevent it in the future.

Edited October 8, 2025Oct 8 by ericup

Looks good, no disk errors so far.

4 minutes ago, ericup said:

I would still like to figure out what happened and how to prevent it in the future.

Most likely a power/connection issue, if it happens again, recommend replacing the cables.

Thanks for saving my bacon again JorgeB. I feel stupid because a simple reboot fixed it but I was too afraid to do it.

Can you tell me what this is from my logs?

Oct  8 16:47:05 Tower kernel: vethcacadaf: renamed from eth0
Oct  8 16:47:05 Tower kernel: docker0: port 19(vethe22d574) entered disabled state
Oct  8 16:47:05 Tower kernel: vethe22d574 (unregistering): left allmulticast mode
Oct  8 16:47:05 Tower kernel: vethe22d574 (unregistering): left promiscuous mode
Oct  8 16:47:05 Tower kernel: docker0: port 19(vethe22d574) entered disabled state

It still shows up after the reboot.

Those are normal when the containers start, but it's not normal if they show 24/7.

Yeah something is still happening. Just checked the logs and got this

Oct  9 16:15:35 Tower kernel: sd 9:0:2:0: attempting task abort!scmd(0x000000002c1f89b4), outstanding for 60056 ms & timeout 60000 ms
Oct  9 16:15:35 Tower kernel: sd 9:0:2:0: [sdg] tag#3318 CDB: opcode=0x12 12 00 00 00 24 00
Oct  9 16:15:35 Tower kernel: scsi target9:0:2: handle(0x000a), sas_address(0x4433221102000000), phy(2)
Oct  9 16:15:35 Tower kernel: scsi target9:0:2: enclosure logical id(0x500605b00471ab80), slot(1) 
Oct  9 16:15:35 Tower kernel: sd 9:0:2:0: task abort: SUCCESS scmd(0x000000002c1f89b4)
Oct  9 16:15:35 Tower kernel: sd 9:0:2:0: Power-on or device reset occurred
Oct  9 16:15:36 Tower kernel: sd 9:0:2:0: Power-on or device reset occurred
Oct  9 16:15:52 Tower emhttpd: read SMART /dev/sde
Oct  9 16:31:42 Tower emhttpd: spinning down /dev/sdb
Oct  9 16:46:56 Tower emhttpd: read SMART /dev/sdb
Oct  9 17:00:41 Tower emhttpd: spinning down /dev/sde
Oct  9 17:31:26 Tower emhttpd: read SMART /dev/sde

That's unrelated to the previous messages, but it does suggest a power/connection issue with that device.