UnRAID 6.7.0 Failure. Diagnostics Attached.

[RevelRob]

Hi,

I am having an issue with my instance of UnRAID.

I'm running 6.7.0.

Firstly, I haven't really had time recently to play with it (UnRAID, not my peter ) so I've been sitting on 6.7.0. I hope to update soon when nobody is using the server.

The UI has gone a bit crazy and is showing me this, which is different than the usual dark mode:

I assume it has to do with this:

Which is also leading to this?:

 

Also, it says that VM and Docker is down but my containers and VMs are working fine (as far as I can tell).

 

Just wondering if my fix is to buy a new USB stick or is there something else in the diagnostics file that says otherwise?

tower-diagnostics-20190725-1402.zip

If USB is it, I hear this one is great: https://www.amazon.ca/dp/B006W8U2WU/ref=cm_sw_em_r_mt_dp_U_8UBoDbETEF34F

 

Further info:

- My SATA controller is a Marvell 88SE9215 which I hear is not the worst offender of Marvells.

- I have been seeing crc error counts every once in awhile. Since I can't read diagnostics files well, I was wondering if it looks like that problems have been resolved (I think my SATA cable was just loose the last time I saw it. Around the end of June.)

 

Thanks so much for the support here everyone. Probably the best community for getting incredible and friendly help when you're tech savvy enough to want to play around with this cool software/hardware but not savvy enough to understand the inner workings. It is truly appreciated.

[JorgeB]

It appears you're already using an USB 2.0 port, can still try a different one, if the same happens it's likely the flash drive.

 

35 minutes ago, RevelRob said:

My SATA controller is a Marvell 88SE9215 which I hear is not the worst offender of Marvells.

Usually not, but there are some ATA errors on the SSD using it, though they could be cable related, replace cables and see if they go away.

Jul 25 04:48:21 Tower kernel: ata8.00: status: { DRDY }
Jul 25 04:48:21 Tower kernel: ata8.00: failed command: WRITE FPDMA QUEUED
Jul 25 04:48:21 Tower kernel: ata8.00: cmd 61/20:f8:e8:18:7c/01:00:33:00:00/40 tag 31 ncq dma 147456 out
Jul 25 04:48:21 Tower kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 25 04:48:21 Tower kernel: ata8.00: status: { DRDY }
Jul 25 04:48:21 Tower kernel: ata8: hard resetting link
Jul 25 04:48:22 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 25 04:48:22 Tower kernel: ata8.00: supports DRM functions and may not be fully accessible
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 25 04:48:22 Tower kernel: ata8.00: configured for UDMA/133
Jul 25 04:48:22 Tower kernel: sd 10:0:0:0: [sdd] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 25 04:48:22 Tower kernel: sd 10:0:0:0: [sdd] tag#11 Sense Key : 0x5 [current]
Jul 25 04:48:22 Tower kernel: sd 10:0:0:0: [sdd] tag#11 ASC=0x21 ASCQ=0x4
Jul 25 04:48:22 Tower kernel: sd 10:0:0:0: [sdd] tag#11 CDB: opcode=0x28 28 00 47 a7 38 20 00 01 00 00
Jul 25 04:48:22 Tower kernel: print_req_error: I/O error, dev sdd, sector 1202141216
Jul 25 04:48:22 Tower kernel: sd 10:0:0:0: [sdd] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 25 04:48:22 Tower kernel: sd 10:0:0:0: [sdd] tag#13 Sense Key : 0x5 [current]
Jul 25 04:48:22 Tower kernel: sd 10:0:0:0: [sdd] tag#13 ASC=0x21 ASCQ=0x4
Jul 25 04:48:22 Tower kernel: sd 10:0:0:0: [sdd] tag#13 CDB: opcode=0x28 28 00 55 b1 b1 80 00 05 40 00
Jul 25 04:48:22 Tower kernel: print_req_error: I/O error, dev sdd, sector 1437708672

As long as the CRC errors don't keep increasing problem is resolved, they don't reset.

[RevelRob]

1 minute ago, johnnie.black said:

It appears you're already using an USB 2.0 port, can still try a different one, if the same happens it's likely the flash drive.

Yes, it's the port on the motherboard. I'll try to put it on an external port and see if that helps.

 

 

Besides that, is there anything else that may be causing issues that you may have noticed in my diagnostics?

 

Thanks!

 

[JorgeB]

Besides the marvell controller issue didn't see anything special, though syslog is being spammed with smbus errors making it more difficult to analyze, look for a bios update, it might help with that.

[RevelRob]

Yes, I noticed that too. Something about IPMI. May just disable the sensors.

Thanks again!

[RevelRob]

Yup, flash disk is definitely corrupt. Took it out and put it in a separate machine and it gives me errors when trying to copy over certain files.

Also checked some of the xml files that the ui complained was corrupted against an older backup and it looks like they are:

 

I went ahead and made an order for a new flash drive but in the meantime, I plan to format the corrupted one I'm using and try it again until I receive the new one (to keep uptime and to avoid the "changing flash drives too often" UnRAID rule).

 

Would there be any issue with using a backup from June 28?

Unfortunately, I only backed up the "config" directory.

If no issue with an old backup of only config, am I correct in saying that I only need to re-make the usb, replace the new config directory with my old one, execute the proper "make_bootable" file (mac), then insert and boot?

 

Thanks again.

[JorgeB]

1 minute ago, RevelRob said:

 

Would there be any issue with using a backup from June 28?

Not if no device has being replaced/added since.

 

16 minutes ago, RevelRob said:

am I correct in saying that I only need to re-make the usb, replace the new config directory with my old one, execute the proper "make_bootable" file (mac), then insert and boot?

Yep