Moussa

The solution posted in https://github.com/Tautulli/Tautulli/issues/2183#issuecomment-1783969324 worked for me if you're comfortable with running commands on a sqlite database.

As an update to this, after much hair-tearing and swapping of cables and waiting for the issue to re-appear I finally decided to replace the PSU on a suspicion after reading some other forum threads. Upgraded to a newer beefier PSU and it looks like the errors have disappeared now, but still have my fingers crossed they won't reappear in the near future. Not sure if my PSU was faulty or I had too many drives on each cable but it turned out to be the culprit.

Ah thanks, that makes sense. I've figured out the new myunraid.net URL now. I think the link on https://forums.unraid.net/my-servers/ was throwing me off because I'm fairly sure it used to point to hash.unraid.net but now is pointing to blackbox.local for some reason. I'm not sure what's going on there but everything else is working now, thank you for the help.

@ljm42 Thanks, I missed that a new domain was being used. I've added that to my router exceptions for DNS rebinding and the message about DNS rebinding has now disappeared from the Management Access page, but I'm still seeing the same issue after restarting the server again. It still looks like it's still serving the blackbox.local cert for some reason rather than the LE cert.

Hi there, Recently my browser has started showing an invalid certificate warning when I navigate to <myserverhash>.unraid.net. Clicking on the cert details in the browser shows the cert is signed by <servername>.local despite Unraid showing a cert from LE in my Management Access settings. I've tried the steps described in with no luck, even rebooting my server. Strangely the Management Access page says `DNS Rebinding Protection is ENABLED` but I'd disabled that years ago on my router and nothing has been changed on the router in months. Doing a nslookup from my network resolves the <myserverhash>.unraid.net URL without issue so I don't think there is a DNS rebinding issue, but I'm at a loss as to why I can no longer access my server securely without a warning. Additionally if I leave SSL/TLS access on and ignore the cert warnings I can not see my array (just blank rows), cannot open a web terminal (the opened window either 504s or briefly opens and then closes), or even download diagnostics (it seems to hang immeadiately) so the server is in a pretty broken state. Thanks in advance for any help! blackbox-diagnostics-20220824-1255.zip

Thanks, I'll try to change out the cable again at some point.

After several attempts I managed to get an extended SMART test to complete, and it did so without any errors. So now I'm at a loss as to what the issue is. Faulty SATA connector on the drive? blackbox-smart-20220803-1226.zip

Unfortunately I cannot get an extended SMART test to complete. It seems to get aborted early with a `Aborted by host` message, and I'm not sure why. I have the spin down delay set to `Never` on that drive so it's not being spun down.

Thanks both, I'll run the extended SMART test and see what comes out.

For the last couple of months I've had a disk in my array that sometimes produces errors like the ones below: Aug 1 08:16:50 Blackbox kernel: ata6: hard resetting link Aug 1 08:16:56 Blackbox kernel: ata6: link is slow to respond, please be patient (ready=0) Aug 1 08:17:00 Blackbox kernel: ata6: COMRESET failed (errno=-16) Aug 1 08:17:00 Blackbox kernel: ata6: hard resetting link Aug 1 08:17:01 Blackbox kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 1 08:17:01 Blackbox kernel: ata6.00: configured for UDMA/133 Aug 1 08:17:01 Blackbox kernel: ata6: EH complete Aug 1 08:54:37 Blackbox kernel: ata6.00: exception Emask 0x50 SAct 0x40000 SErr 0x4890800 action 0xe frozen Aug 1 08:54:37 Blackbox kernel: ata6.00: irq_stat 0x0c400040, interface fatal error, connection status changed Aug 1 08:54:37 Blackbox kernel: ata6: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Aug 1 08:54:37 Blackbox kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 1 08:54:37 Blackbox kernel: ata6.00: cmd 60/00:90:70:bc:bb/04:00:8c:00:00/40 tag 18 ncq dma 524288 in Aug 1 08:54:37 Blackbox kernel: ata6.00: status: { DRDY } Aug 1 08:54:37 Blackbox kernel: ata6: hard resetting link Aug 1 08:54:43 Blackbox kernel: ata6: link is slow to respond, please be patient (ready=0) Aug 1 08:54:47 Blackbox kernel: ata6: COMRESET failed (errno=-16) Aug 1 08:54:47 Blackbox kernel: ata6: hard resetting link Initially I put it down to an issue with the motherboard, cables, or power supply but I've since swapped cables and also moved the drive to another motherboard SATA port without any success. This is now causing some parity check errors, and I think the drive is at fault even if SMART is saying the drive is fine. Should I be replacing this drive now or is there something else I can try? Thanks in advance for any help. blackbox-diagnostics-20220801-1600.zip blackbox-smart-20220801-1613.zip

Fantastic, thanks for the quick fix!

Not sure if this has been reported before but I'm seeing these errors whenever my mover runs Apr 12 06:00:01 Blackbox root: mvlogger: Pool /mnt/cache is above 'move all' percentage, moving all cache-yes shares to array Apr 12 06:00:01 Blackbox root: mvlogger: Not in Test mode Apr 12 06:00:01 Blackbox root: mvlogger: Complete Mover Command: find /mnt/cache/TV Shows -depth | /usr/local/sbin/move -d 1 Apr 12 06:00:01 Blackbox root: find: '/mnt/cache/TV': No such file or directory Apr 12 06:00:01 Blackbox root: find: 'Shows': No such file or directory Apr 12 06:00:01 Blackbox root: mvlogger: Done checking Move All from Share Apr 12 06:00:01 Blackbox root: mvlogger: Share Name Only: TV Shows Apr 12 06:00:01 Blackbox root: mvlogger: Cache Pool Name: Apr 12 06:00:01 Blackbox root: mvlogger: No shareCachePool entry found in config file, defaulting to cache Apr 12 06:00:01 Blackbox root: mvlogger: cache Threshold Pct: Apr 12 06:00:01 Blackbox root: mvlogger: OVERALL Threshold: 0 Apr 12 06:00:01 Blackbox root: mvlogger: Share Path: /mnt/cache/TV Shows Apr 12 06:00:01 Blackbox root: mvlogger: Pool Pct Used: 79 % Apr 12 06:00:01 Blackbox root: mvlogger: DFTPCT LIMIT USED FOR SETTING: 0 Apr 12 06:00:01 Blackbox root: mvlogger: Threshold Used: 0 Apr 12 06:00:01 Blackbox root: mvlogger: Adding Age Apr 12 06:00:01 Blackbox root: mvlogger: Age 7 Apr 12 06:00:01 Blackbox root: mvlogger: Skipfiletypes string: find "/mnt/cache/TV Shows" -depth -mtime +6 Apr 12 06:00:01 Blackbox root: mvlogger: Not in Test mode Apr 12 06:00:01 Blackbox root: mvlogger: Complete Mover Command: find "/mnt/cache/TV Shows" -depth -mtime +6 | /usr/local/sbin/move -d 1 It looks like the space in my `TV Shows` share is causing issues with the path. I'm not sure if that's a bug in the original mover script or this plugin.

I'm going to be using ddrescue. I think I've got it running now. Thanks again for the help.

@JorgeB I have moved over both source and destination drives to onboard SATA, but I'm a little confused on how to proceed. Your guide says the drives shouldn't be mounted, but how do I access them through the CLI without them being mounted? They do not show up under `/dev/mnt/` (which is to be expected). I've installed the Unassigned Devices plugin but wary of proceeding with formatting the destination drive so it can be formatted, and then I'd have to mount them anyway? Would appreciate any guidance. Thanks in advance. Edit: For further clarification, this is what I see under `/dev`

Thanks, that's good advice. I'll give this a whirl this weekend and see it how it goes. Thanks for your help and for your guide!

Or actually I could temporarily take the parity disk out of the array and use that to clone to, and then copy the results into the array before returning the parity disk to the array. Just hope nothing else fails during this process...

Thanks for the reply. Your post on using ddrescue looks very helpful, but I don't have another empty disk of the same size to copy to. The only choice I have is another larger array disk that is mounted and has data but has enough free space to rsyc the salvaged data onto. I've already used `xfs_repair` to salvage some data. In this case do you recommend that I just take the dying disk out of the array into unassigned devices and rsync data from there into the array disk?

Hi all, For the last few weeks my parity disk has been sporadically producing read errors which don't stop until I restart the array. I'm fairly confident the disk is okay and the issue lies in my cabling, motherboard, or SATA card (probably the latter). However, I had a power cut recently and it appears as though one of my array disks is now dying. The `Current pending sector` SMART attribute is now at `3` and it's producing a ton of read errors. Because of the parity disk situation I believe I'm going to lose some data, as the parity disk was in an error state at the time. It's not the end of the world, but I'd like to recover what data I can from the array disk before removing it. Starting the array with both the parity disk and array disk allocated I can see some data on the disk. However unraid is showing the disk state as `device contents emulated` and trying to read data off the disk eventually results in read errors from the parity or array disk, locking up my server. My plan is to remove the parity disk and array disk from the array and mount the array disk as an unassigned disk. Then try to copy what data I can from the disk to the array. Is this plan sane? Thanks in advance for any advice. blackbox-diagnostics-20220301-1956.zip

Thanks a lot, much appreciated!

Hi there, Is it possible to change my username to Moussa if possible (and if available obviously!) please? Thanks very much in advance.

This did the trick, thanks so much!

Hi there, I've been experiencing an issue with backing up my unraid flash drive since updating to 6.8.1 from 6.7.x. In my Docker config for this container I have `/boot` mapped to the container path `/flash` and previously this worked fine with Duplicati able to access the entire contents of the USB stick and back them up. But now Duplicati is showing signs of being unable to access the path, with backups failing with a "[Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-FileAccessError]: Error reported while accessing file: /flash/" message. Is there a setting I need to change or something?

Love unRAID! Only thing that could improve it for me would be a native phone app to manage the server.

Right, it shouldn't be uploading them again but it is I can see it's uploading the files again verrrrry slowly (through the app logs and my network monitor), and at this rate it's going to take over a year to finish whatever it's doing. I'm not sure why it correctly scans and analyzes the files to be backed up after a fresh start but then starts over from the beginning on the next full scan. Perhaps this is a Crashplan issue and nothing to do with the docker image? Though the timing is suspect with the unRAID upgrade.

Hi @Djoss. I can confirm I can see all my files when I click 'Get Files'. The crashplan website also shows that my backup is still the full size I expect. Any logs or files I should post?