MammothJerk

i've tried two different cables for this purpose, one was explicitly for a sff-8087 host to sff-8654 target from an email with the manufacturer, the other one was one "SFF-8654 to SFF-8087, Mini SAS 4.0 SFF-8654 4i 38Pin Host to Mini SAS 4i SFF-8087 36Pin Target Cable 1M" from amazon. I was a bit dubious about the amazon one but i couldn't find anything else about a "reverse breakout sff-8654 to sff-8087 cable" so i decided to go with it. Anyways neither of them worked so i decided to email asus about it. After a bit of back and forth they sent me a video of their testbench with the cable plugged into the motherboard but nothing connected on the other end, but they kept insisting it was plugged in on both ends even with their own video as proof. I believe it's my third interaction with asus customer support and their reputation is still accurate. i decided to just get another HBA card as you did.

Yeah that is weird, not sure where the script for the notification bubbles for the GUI is located but i would assume the issue is in there.

i'm trying to set up a notify notification when a user script finishes but i'm running into an issue where the equals symbol will hide everything after it. something simple like /usr/local/emhttp/webGui/scripts/notify -d "5+5=10" only displays 5+5 im trying to add a URL with the -l flag but it never works since it has a = in the URL, even with url encoding it will not work. Using a url shortener does work (as long as it doesn't have a = ) but i would like to avoid that if i can.

just hit 15k again and it crashed and i lost around 200 torrents 😬 Definitely looks like a hard limit. Seems like its about time to run multiple instances.

just had another "bad shutdown" crash and lost about 500 torrents and the archive did not save me this time.

I just had 500 torrents disappear after a crash but luckily i could grab the .state and .fastresume from the archive that was created and i only lost the label assignments. the archive message is and it appears the state went back to a day back or so. I'm not sure how to find out how the "shutdown" happened since i definitely did not trigger it myself so it wouldve had to have been a crash of some sort. Might just be relative instability since i just hit 15000 the other day... 🥲

Do you have any insight into how to use an "exclusive share" in delugevpn? writing to the cache through the FUSE file system is really bad for me and peaks my CPU usage during "big" writes 10MB/s+ Setting the /mnt/user/downloads share to an exclusive share completely solves this issue. However it creates a new issue where passing /mnt/user/ to the container no longer shows the download share (which is i think the expected behaviour for exclusive shares). I then have to explicitly pass through /mnt/user/downloads to the container but now all the torrents do a copy+delete and creating issues and wasted operations. I'm wondering if maybe its possible to pass through the downloads directory as /mnt/cache/downloads but treat moves to /mnt/user/* as still being on the cache and executing atomic moves? I'm not sure if i'm making sense or if a missing something that would make this easier.

haven't had any crashes since, mover has mover 3TB and parity check finished (with lots of errors 🥲) and the server has not crashed.

I also had this exact same issue but following the steps from @Gnomuz fixed it for me as well. It would also sometimes work for me if i power-cycled the UPS and then started the unraid server but as it was unreliable i was just using USB. Hopefully the issue can be fixed, not sure if it's unraid or apcupsd's problem. edit: bug report created by gnomuz in 2020 here:

New cpu installed. i'll try to run a parity check now and see what happens.

I started the RMA process and should receive the replacement CPU within the week.. I tried disabling docker and VMs and just running mover for the past 24 hours and it did not result in a crash, i turn on VMs (HAOS) and it results in a "hung" state within 4 hours. This time i was able to grab diagnostics since i destroyed the zpool. Not sure if it shows anything or if it's a different issue altogether.

was a long shot and it didnt work. I cant really think of anything else to try... It does seem like the server crashes more frequently now so that might hint that the CPU is even further degraded? the only error message i'm receiving is fro the IPMI but that doesn't really tell me what the issue is... Any other ideas @JorgeB?

I have an inkling that it's related to my HA VM. i think i've had it twice now that i trigger a lightswitch and shortly thereafter the server crashes. it might be the "USB manager" plugin i use to add a zwave and zigbee dongle to the same VM even though they have the same name in unraid, ill just add them in xml instead and see.

different PSU... still hard crash after 30~ hours 😬

Another full crash after 2 days 3 hours of uptime, no special activities were taking place (no mover, no manual moves, no parity check). I did get a troubling message yesterday about the 3.3V voltage sensor going off after searching the logs it appears i got a warning on the 28th of july as well, this time on the 12V voltage sensor I do have an extra PSU lying around, ill change it out and see if that fixes it...

i just ran into the same issue. setting the slimSAS port to SATA and plugging in a cable, the nvme slots AND all the pci slots stop working (even the ipmi board in the x1 slot stops working) Did you ever get it figured out with slimsas -> sas backplane cable? i was hoping to avoid getting a second HBA card if i can. i wasn't aware that these cables have any directionality to them and i am unable to find a "reverse breakout" SFF-8654 to SFF-8087 cable. this is the cable i got: https://www.inline-info.com/en/products/cable/sas/11195/inline-slim-sas-kabel-sff-8654-zu-mini-sas-sff-8087-12gb/s-0.5m edit: the manufacturer responded to my inquiry so it would appear they DO have directionality, i'll see if i can find such a cable on ebay instead...

The server ran fine for 4 days and 12 hours~ and then out of nowhere it did another hard crash where keyboard, webui, ssh, containers unresponsive, etc. Had to do a hard reset Syslog for the past couple hours: The crash happened a couple of minutes after i finished manually moving a couple of things (400GB~) off of the cache to the array. The mover is disabled. the self test didn't find any errors either. Could it be a bad PSU? edit: just saw my motherboard got ANOTHER BIOS update (beta 3802) though it specifically mentions a fix for non-k processors - I'll install that as well and see what happens...

I remember from the old docker folders plugin there was an option to indicate if a container with autostart enabled is not running, the green play symbol would turn into a yellow pause symbol. This to indicate that a container with autostart enabled is no longer running. This was very useful to me since i have some big folders and its hard to see at a glance if something crashed or not. Is it possible to add this function to folderview?

Since it seemed like the mover was causing the crash i searched around for previous issues pertaining to the mover crashing the server. I tried running xfs repair on all the disks in maintenance mode, a couple of them seem to have needed that with 10~ inodes being fixed. running "docker safe new perms" which seemed to get stuck at /disk13/Storage for over 15 hours before i decided cancel it. increasing the setting "minimum free space" for all my shares, i believe i set them when i created the server and didn't touch since. I then enabled mover logging and it ran for 5 minutes before crashing the server, stopping on disk13/appdata/Radarr/MediaCover/2018/poster-500.jpg so disk13 is mentioned in 2 issues, might be a coincidence. the disc is only about 3 months old and doesn't seem to have any obvious issues 1 Raw read error rate 0x000b 100 100 001 Pre-fail Always Never 0 2 Throughput performance 0x0004 148 148 000 Old age Offline Never 49 3 Spin up time 0x0007 094 094 001 Pre-fail Always Never 145 (average 137) 4 Start stop count 0x0012 100 100 000 Old age Always Never 62 5 Reallocated sector count 0x0033 100 100 001 Pre-fail Always Never 0 7 Seek error rate 0x000a 100 100 000 Old age Always Never 0 8 Seek time performance 0x0004 140 140 000 Old age Offline Never 15 9 Power on hours 0x0012 100 100 000 Old age Always Never 2610 (3m, 17d, 18h) 10 Spin retry count 0x0012 100 100 000 Old age Always Never 0 12 Power cycle count 0x0032 100 100 000 Old age Always Never 62 22 Helium level 0x0023 100 100 025 Pre-fail Always Never 6553700 90 NAND master 0x0031 100 100 001 Pre-fail Offline Never 0x004400000000 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 214 193 Load cycle count 0x0012 100 100 000 Old age Always Never 214 194 Temperature celsius 0x0002 049 049 000 Old age Always Never 45 (min/max 25/56) 196 Reallocated event count 0x0032 100 100 000 Old age Always Never 0 197 Current pending sector 0x0022 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0008 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x000a 100 100 000 Old age Always Never 0 I'm currently running an extended self-test but im doubtful that will tell me anything. Anything else i can do to troubleshoot Mover if that indeed is the issue?

i updated to 6.12.11 when it was released and my server started crashing this friday so i asssume that is not the issue, i will most likely do a rollback if my other troubleshooting does not fix the problem.

Formatted the cache as btrfs and started mover to try to move stuff back over... instantly crashed would appear that the issue is with either unraid or my storage...

yea thats what i'm afraid of. i updated the bios to 3701 but it mightve been too late and damaged the CPU. any ways i can test for it or would i need to start a return? memtest ran 1 pass with no errors i let it run overnight and it got up to 5 passes without errors Whats next?

I moved everything off using mc, then reformatted the cache, no issues. I then started the mover to move everything back to the cache, and the server crashed 🤔 I'll run memtest and get back to you...

trying to move data off of the cache to the array using Mover my server has crashed twice