Yousty

I tried a couple different ethernet cables and ports on my switch (rebooting Unraid each time) but the NIC still isn't working properly. It won't pull an IP address from my router and I keep getting the red text at the bottom of Unraid "Interface Ethernet Port 1 is down. Check cable". Am I just unlucky and have a faulty NIC?

Here you go. nas-diagnostics-20230630-1149.zip

I have an ASRock X370 Professional Gaming motherboard with a built-in AQUANTIA 5 Gigabit LAN NIC. The problem is Unraid doesn't seem to recognize it. If I plug an ethernet cable into it neither of the network activity LEDs turn on. Do I have to manually install a driver? I'm running Unraid 6.11.5. Thank you!

Sold to Whaler_99. Smooth transaction!

Final Price Drop. Pricing these to sell because I feel bad that I have 64TB of storage just sitting here that could be put to use by somebody. $500 for all 64TB ($7.81 per TB!) w/ free shipping in the US.

Just upgraded to 16TB HDDs so no longer have need for these. Most have only seen a few hour spin up time in my NAS each day. They have all just been zeroed and successfully precleared and ready to put in an array. $700 $600 $500 for all 64TB ($7.81 per TB!) w/ free shipping in the US. They're all packaged up in custom HDD foam and ready to ship w/ tracking provided. Model #s: 5 x Seagate ST8000DM004 3 x Seagate ST8000AS0002 See this post for my previous sale with positive feedback.

I assumed that as well but wanted confirmation from some other more experienced people before I initiated an RMA. Thank you!

I recently got a bunch of new hard drives and was preclearing them when one of them failed early in the post-read. I've done dozens of preclears and never had a preclear fail, so I was hoping for some suggestions on how to proceed? Thank you! preclear_disk_ZL24A79Y_23305.txt ST16000NM001G-2KK103_ZL24A79Y-20220415-1630.txt

Just upgraded to 16TB HDDs so no longer have need for these. I bought all of them new and most have only seen a couple hour spin up time in my NAS each day. Never had any errors reported in Unraid with any of them and all have just been zeroed and successfully precleared. $90 $80 for both drives w/ free shipping in the US Model #s: Seagate ST4000DM000, Date: 13226 Seagate ST4000DM000, Date: 13416 See this post for previous sale with positive feedback preclear_report_Z3002190_2022.04.03_21.25.44.txt preclear_report_W3005LFH_2022.04.03_21.52.22.txt

THANK YOU! THANK YOU! THANK YOU! THANK YOU! After going into BIOS and setting "Power Supply Idle Control" to "typical current idle" and disabling C-states, Unraid has been running without any issues for the last 48 hours. Updating my BIOS must have triggered this issue because it had been running fine without changing those settings for years before updating BIOS.

It just did it again after being stable for 4 hours, but this time I was booted into safe mode. Here are the logs: nas-diagnostics-20220318-2035.zip syslog

It just happened again. Here is another diagnostics log and syslog. Any help would be greatly appreciated, I'm pulling my hair out with frustration. Thank you. nas-diagnostics-20220318-1158.zip syslog

My Unraid server has worked perfectly for the last several years but then my nvme cache drive completely failed overnight. I replaced the cache drive and restored it with CA Backup/Restore, but ever since then my server has been restarting itself after being on a couple hours and then a couple hours after that it will completely freeze up (can't access via GUI and even local access is frozen, can't type anything). I'll have to hard restart to bring it back online but it will just do the same thing again after a couple hours, even if I disable all dockers. I reseated the ram and ran a memtest and it passed with 0 errors and I reseated all of the hard drive power and sata cables but I can't figure out what is going on. Can anybody please look at my log and see if anything catches your eye? This was taken right after it restarted itself and automatically began a parity check. nas-diagnostics-20220317-2251.zip

Using Unraid 6.9.2 and my cache drive completely stopped responding and is officially dead. I have successfully replaced the cache drive and all of the docker/appdata via the CA Backup/Restore app, which also backed up my libvirt.img which I was using to run a Windows 10 VM off of an unassigned drive. I turned off VM manager and placed the libvirt.img backup file in cache/system/libvirt where it was before and then turned VM manager back on but when I go to the VM tab I get "Libvirt Service Failed to Start." Can somebody PLEASE help me restore my VM? I'm relatively amateur when it comes to VMs and used a guide years ago to set mine up, so I'm not sure what I may be missing.

Last night my cache drive completely stopped responding and is dead. I have successfully replaced the cache drive and all of the docker/appdata via the CA Backup/Restore app, which also backed up my libvirt.img which I was using to run a Windows 10 VM off of an unassigned drive. I turned off VM manager and placed the libvirt.img backup file in cache/system/libvirt where it was before and then turned VM manager back on but when I go to the VM tab I get Libvirt Service Failed to Start. Can somebody PLEASE help me restore my VM? I'm relatively amateur when it comes to VMs and used a guide years ago to set mine up.

So last night it appears my nvme cache drive just completely stopped working. I've tried everything but Unraid won't even recognize it. Thanks to this amazing app I have a backup of my cache drive from 3 days ago. The problem is I have no idea how to restore it. Could somebody please give me step by step instructions of what to do once I install the new cache drive and boot up Unraid?

That was the first thing I tried. I removed the VM nvme and swapped the cache nvme to the other slot on my motherboard and booted. BIOS listed the drive when I went to the Storage tab, but when I booted into Unraid it's not there. Here is a picture I just took from BIOS that lists the missing 960 nvme.

In the middle of last night I received an error email from my server: I logged into unraid gui this morning and it still showed the drive listed on the main screen but no temp was displayed. I could browse the folders/files located on it but I couldn't copy or modify any of them. So I tried restarting Unraid and now it doesn't even display that drive anywhere, but it still shows my other nvme drive that has a VM running on it. I powered down and decided to upgrade my motherboard BIOS to the latest just in case and I even swapped my 2 nvme drives on the motherboard slots to make sure it wasn't a bad slot but Unraid still isn't seeing my cache drive, but my Asrock BIOS does see both nvme drives. Please help! Here is my diagnostic log: nas-diagnostics-20220316-1012.zip

I actually figured out how to do it on my own and it's super easy. Figured I'd post the solution here in case anyone else finds this thread via googling like I did. I'm assuming everyone is following the guide on OmerTu's github and you're at step B.3. Just create a new docker container and add the following port and variables to it.

Did you ever get this figured out sonofdbn? I would like to set it up as well but not sure where to begin.

Thank you!!! I updated my AMC input and output directories using storage as shown in the picture and move now works!

I'm hoping somebody can help. I have Filebot setup and working perfectly. I download files from my seedbox to a temp folder (mnt/user/temp) and then have AMC rename and move the files to where they belong (mnt/user/Movies or TV Shows) because I don't need the files in the temp directory after they're renamed/moved. However I've noticed using the move command requires reading and writing the entirety of the file, which seems odd to me since it's staying on the cache drive (until unraid's mover runs and moves the files to the array). Usually it's not that big of a deal but a lot of times I'm downloading 60GB files and that's a lot of unneeded wear and tear on the disk, not to mention time consuming. I've gone into Midnight Commander and manually moved a file from mnt/user/temp to mnt/user/Movies and it was instant so there must be something wrong in the Filebot docker permissions or setup that's causing it read/write the entirety of the file when it performs a move. I've attached pictures of my Filebot Docker setup

Aaaand I solved it. Decided to make sure I had the latest NIC software installed on my Windows 10 source machine, and sure enough after installing that I am now transferring at 113MB/s to my Unraid server. Thank you everyone for helping me troubleshoot and leading me down the right path to fix the issue!

Finally had some time to watch the video and run iperf and shockingly it is the network causing the slowdown. C:\iperf3>iperf3 -c 192.168.1.3 Connecting to host 192.168.1.3, port 5201 [ 4] local 192.168.1.2 port 58770 connected to 192.168.1.3 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 84.0 MBytes 704 Mbits/sec [ 4] 1.00-2.00 sec 83.9 MBytes 704 Mbits/sec [ 4] 2.00-3.00 sec 84.0 MBytes 705 Mbits/sec [ 4] 3.00-4.00 sec 83.9 MBytes 704 Mbits/sec [ 4] 4.00-5.00 sec 83.8 MBytes 703 Mbits/sec [ 4] 5.00-6.00 sec 84.0 MBytes 704 Mbits/sec [ 4] 6.00-7.00 sec 84.0 MBytes 704 Mbits/sec [ 4] 7.00-8.00 sec 84.0 MBytes 704 Mbits/sec [ 4] 8.00-9.00 sec 83.9 MBytes 704 Mbits/sec [ 4] 9.00-10.00 sec 83.5 MBytes 700 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 839 MBytes 704 Mbits/sec sender [ 4] 0.00-10.00 sec 839 MBytes 704 Mbits/sec receiver iperf Done. It just makes no sense to me since literally nothing about my network has changed since switching from SATA to NVMe SSD.

I transfer mostly video files, ranging from 1GB to 60GB and they always max out at 84MB/s now. The screenshot shows a transfer I just did. As you can see it hits 84MB/s right away and sits there, almost like there's a bottleneck somewhere. I am positive it's going to the cache drive. I monitored the cache drive temp in Unraid during the transfer and it stayed 88°F the whole time. I have the SSD trim app installed and set to run every 4 hours. I'll watch that video and do the tests but it's highly unlikely it's a network issue when I've been doing hardwired transfers to this server at 113MB/s for over 5 years now and the ONLY thing that changed was switching out my SSD cache drive from a SATA one to an NVMe one.