HSEDuster

Hey guys, wondering if anyone knows where to get the bz* files? My bzfirmware is corrupt and my searching indicates replacing these files should either fix it, or at least be the first step. Problem is, I'm (obviously) not running the latest version, so... yeahhhh...

Short answer, no. Long answer, no, but after a lot of searching, I think it might be related to something to do with either the SAS drives or the HBA. I only guess that because I can find some (limited) information on ASC and ASCQ "codes".. It's pretty lame though as these eventually fill up my log file and as far as I know the only way to clear that is a restart... Out of curiosity, what's your setup? Just wondering if there's any common denominator here...

This is actually super helpful. I feel like an idiot for not thinking of this. I access my unraid servers at work sometimes when things are slow (err like now), and never thought of this to get into my dockers...

For a few months now my primary unraid server experiences seemingly random times when it becomes unresponsive. That is, SMB and NFS shares are inaccessible, VM's don't work, and I can not access the web GUI. I don't know for sure, but I believe it might be connected to a repeating log entry I keep getting: Jan 31 16:39:54 Tower kernel: sd 3:0:6:0: [sdh] tag#1347 Sense Key : 0x1 [current] Jan 31 16:39:54 Tower kernel: sd 3:0:6:0: [sdh] tag#1347 ASC=0x1c ASCQ=0x0 That's just from one disk, but all the disks get them and its absolutely unrelenting. Sometimes the server will run for weeks, though more often it will run for a few days before needing to be hard-reset. While I can't recall exactly, I know this started happening after I moved my server from an R410 to an R710. All of my drives are (and have been) SAS drives. After the upgrade, however, I did replace my SATA cache SSDs with LB806M SAS SSDs. Those are mounted in the actual R710 with the HDDs being mounted in an MD1000 external case. Diagnostics attached, and I would be happy to provide any other information needed. Side note, I don't know what it will show in diagnostics, but when downloaded, I was (am) running a parity check with Disk 3 missing. The drive was failing so I replaced a parity drive with a new 10Tb and once this parity check is done, the old 8Tb parity will go in Disk 3's place. There is also a UD that is 'unhealthy', but it's an old desktop drive I was pulling files off of, nothing related to the system as a whole. Just figured I would mention it. tower-diagnostics-20220131-1638.zip

I apologize and certainly see what you're saying. I will be proactive in the future with the diagnostics files. I really appreciate the help and support on the forums in aggregate. This is the the first time I think I have ever posted an issue. 99% of the time I can solve any issue in looking through these forums and spaceinvaderone videos... Ah... I think I might know the issue then. I was having some other issues a while back and in the process of troubleshooting I replaced the cable between my server and the SAS enclosure. When I worked out that it wasn't the cable, or the controller modules in the drive enclosure (an MD1000), I left both cables attached. I assume that this could be the cause. I'll try unplugging one and restarting and see what comes up. I have new processors to install as well, so I might install those while its down this weekend... Of course I guess the alternative culprit could be the HBA card, which is also due to be replaced soon, so hopefully one of the two fixes things. Thank you guys for the help. I really can't convey how appreciated it is. This place is a gold mine of information.

Oh okay, here you go then. Thank you very much. tower-diagnostics-20201005-1609.zip

So I feel pretty dumb asking this, but which? I downloaded the diagnostics but I somewhat doubt you need/want all the various files. I am including the syslog but if there's another, I'll happily post it. syslog.txt

I have a quick (hopefully) question/issue. I'm sure I'm just missing something, but UD shows my array devices as... well... Unassigned devices... Screen shots included, and hopefully self explanatory. The sd* identification is different between the two, but as you can see the HDD ID is the same.