ericup

Late to the party but this just happened to me. Is there a way to build a script that reinstalls these all for me in case it happens again?

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

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 stateIt still shows up after the reboot.

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

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.

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

So disabled all plugins, managed to get it back up by defaulting the network settings then adapting them one step at a time to my config (2 routers, 2 NICs, 2 subnets). Found the instability was coming from accessing the webui on the far router. switched to the router my device is connected to and it's fine. Had 2 drives drop for some reason so I am running a data rebuild now. Long story short, no clue why it happened but I solved the webui issue by deleting and regenerating the network.cfg file. I am solving the drive issue by rebuilding onto the existing drives.

so, not wure what caused the console to freeze but it is working now. webui is still dead for some reason.

Yes, I managed to turn off the auto start yesterday because I needed to check the drive issues. It kept locking up while I was trying to figure out why 2 drives with no issues were disabled.

Hey all, My unraid server has completely locked up. The most noteable thing I remember was it complaining about parity2 having read errors. I also ran the unraid patch plugin but it failed because of something about the startup already being modifidied. I thought it was just the GUI so I spent all day rebooting and testing a completely different thing. (new boot drive, /etc/config/network.cfg, and nginx restarts.) Now after going back to the old drive the entire system console included locks up in under 5 minutes of reaching the login prompt. I am attaching old diagnostics and hoping I don't dox myself. I made the diagnostics earlier today when I started having issues. tower-diagnostics-20250307-1722.zip

Update for any future explorers. Disk 2 and 4 were cleaned using the xfs_repair tool in the webui in maintenance mode. I decided to cut my loses on disk 3. I believe it is to corrupted for recovery so I formatted the emulated drive and am now rebuilding.

Dashboard is clean. I know that parity 2 can fail and I can still rebuild but then I am not protected. When the drive is removed from the array (emulated) it is still unmountable. If I can not get the repair tool to fix it then wouldn't formatting/new config be the only answer?

It was collecting reallocated sectors for a few weeks there but seems to have slowed down. tower-diagnostics-20250118-1231.zip

Well other than corruption the drive and having 4 years of run time it is functional is it not? If I can fix the corruption the device will be fine. I am getting paranoid the longer this goes on as parity2 has been accumulating smart errors.