Ayster Posted March 2, 2023 Share Posted March 2, 2023 Hi, Hoping someone can help with this. I'm running Unraid 6.11.5 on an HP Z820 Workstation with 32GB RAM and dual Xeon E2687W's I get intermittant lock ups of the server where the webui is unresponsvie and any running dockers stop working or take a long time to respond. This can happen from a few seconds to a few minutes, it will eventually resond again without crashing. I've tried replacing several docker containers with different versions, and can't seem to fix this. I'm not even sure if it is a docker problem! Im at the point of binning Unraid and trying another platform, I used to run Open Media vault on a much lesser server with no issues, but am having a time trying to figure this out. I'm not a Linux expert so am a bit stumped. I've attached the diagnostics zip if somebody with more knowledge could please have a look that would be amazing. Thanks, Alan. ur01-diagnostics-20230302-0747.zip Quote Link to comment
JorgeB Posted March 2, 2023 Share Posted March 2, 2023 Enable the syslog server and post that after a crash. Quote Link to comment
Ayster Posted March 2, 2023 Author Share Posted March 2, 2023 ok will do, thanks, though it doesnt actually crash as such, just goes unresponsive for a while. Quote Link to comment
Ayster Posted March 11, 2023 Author Share Posted March 11, 2023 I enabled syslog but it hadn't recorded anything for a while, until I realised I had to set the syslog server to the server! Anyway, I've had it on since the 4th of march and had a lot of times when the server goes unresponsive as origially stated above, then recently it was behaving itslef normally, no lags or pauses for about a week, now its back to being unresponsive and I've had to reboot 3 times this morning, I've basically had enough of unraid now so have started the process of moving to another platform, but I thought I'd put the syslog on here anyway in case anyone can see why it might be happening before I finally pull the plug! I did notice some errors with SMBD not having access to something when I was just looking through the log, not sure if that is part of the problem? Thanks for looking anyway, A syslog-192.168.1.206.log Quote Link to comment
JorgeB Posted March 12, 2023 Share Posted March 12, 2023 You have multiple devices dropping offline: Mar 4 10:00:06 ur01 kernel: ata7.00: status: { DRDY } Mar 4 10:00:06 ur01 kernel: ata7: found unknown device (class 0) Mar 4 10:00:16 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:00:26 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:01:01 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:01:01 ur01 kernel: ata7.15: limiting SATA link speed to 3.0 Gbps Mar 4 10:01:06 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:01:06 ur01 kernel: ata7.15: failed to reset PMP, giving up Mar 4 10:01:06 ur01 kernel: ata7.15: Port Multiplier detaching Mar 4 10:01:06 ur01 kernel: ata7.00: disable device Mar 4 10:01:06 ur01 kernel: ata7.01: disable device Mar 4 10:01:06 ur01 kernel: ata7.00: disable device Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=90s Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 Sense Key : 0x2 [current] Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 ASC=0x4 ASCQ=0x21 Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 CDB: opcode=0x2a 2a 00 00 7f 16 30 00 0a 00 00 Mar 4 10:01:06 ur01 kernel: I/O error, dev sdk, sector 8328752 op 0x1:(WRITE) flags 0x104000 phys_seg 146 prio class 0 Mar 4 10:01:06 ur01 kernel: sd 11:1:0:0: rejecting I/O to offline device Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: rejecting I/O to offline device SATA port multipliers should not be used with Unraid. Quote Link to comment
Ayster Posted March 12, 2023 Author Share Posted March 12, 2023 5 hours ago, JorgeB said: You have multiple devices dropping offline: Mar 4 10:00:06 ur01 kernel: ata7.00: status: { DRDY } Mar 4 10:00:06 ur01 kernel: ata7: found unknown device (class 0) Mar 4 10:00:16 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:00:26 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:01:01 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:01:01 ur01 kernel: ata7.15: limiting SATA link speed to 3.0 Gbps Mar 4 10:01:06 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:01:06 ur01 kernel: ata7.15: failed to reset PMP, giving up Mar 4 10:01:06 ur01 kernel: ata7.15: Port Multiplier detaching Mar 4 10:01:06 ur01 kernel: ata7.00: disable device Mar 4 10:01:06 ur01 kernel: ata7.01: disable device Mar 4 10:01:06 ur01 kernel: ata7.00: disable device Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=90s Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 Sense Key : 0x2 [current] Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 ASC=0x4 ASCQ=0x21 Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 CDB: opcode=0x2a 2a 00 00 7f 16 30 00 0a 00 00 Mar 4 10:01:06 ur01 kernel: I/O error, dev sdk, sector 8328752 op 0x1:(WRITE) flags 0x104000 phys_seg 146 prio class 0 Mar 4 10:01:06 ur01 kernel: sd 11:1:0:0: rejecting I/O to offline device Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: rejecting I/O to offline device SATA port multipliers should not be used with Unraid. Im not using a sata port multipliers, though I do have an external e-sata caddy with a couple of drives in it. Quote Link to comment
itimpi Posted March 12, 2023 Share Posted March 12, 2023 30 minutes ago, Ayster said: Im not using a sata port multipliers, though I do have an external e-sata caddy with a couple of drives in it. If that has more than one drive in it then it must be using a port multiplier internally to get them to run over a single eSata cable connection. Quote Link to comment
Ayster Posted March 12, 2023 Author Share Posted March 12, 2023 Just now, itimpi said: If that has more than one drive in it then it must be using a port multiplier internally to get them to run over a single eSata cable connection. hmm, ok thanks Quote Link to comment
Ayster Posted March 12, 2023 Author Share Posted March 12, 2023 5 hours ago, JorgeB said: You have multiple devices dropping offline: Mar 4 10:00:06 ur01 kernel: ata7.00: status: { DRDY } Mar 4 10:00:06 ur01 kernel: ata7: found unknown device (class 0) Mar 4 10:00:16 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:00:26 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:01:01 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:01:01 ur01 kernel: ata7.15: limiting SATA link speed to 3.0 Gbps Mar 4 10:01:06 ur01 kernel: ata7.15: softreset failed (1st FIS failed) Mar 4 10:01:06 ur01 kernel: ata7.15: failed to reset PMP, giving up Mar 4 10:01:06 ur01 kernel: ata7.15: Port Multiplier detaching Mar 4 10:01:06 ur01 kernel: ata7.00: disable device Mar 4 10:01:06 ur01 kernel: ata7.01: disable device Mar 4 10:01:06 ur01 kernel: ata7.00: disable device Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=90s Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 Sense Key : 0x2 [current] Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 ASC=0x4 ASCQ=0x21 Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: [sdk] tag#14 CDB: opcode=0x2a 2a 00 00 7f 16 30 00 0a 00 00 Mar 4 10:01:06 ur01 kernel: I/O error, dev sdk, sector 8328752 op 0x1:(WRITE) flags 0x104000 phys_seg 146 prio class 0 Mar 4 10:01:06 ur01 kernel: sd 11:1:0:0: rejecting I/O to offline device Mar 4 10:01:06 ur01 kernel: sd 11:0:0:0: rejecting I/O to offline device SATA port multipliers should not be used with Unraid. so, would this account for the locking up and unresponsiveness? Quote Link to comment
JorgeB Posted March 12, 2023 Share Posted March 12, 2023 Multiple disks dropping can cause that. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.