nitewolfgtr

@itimpi I tried setting up syslog to mirror to flash but when it froze again and I rebooted it, there was no previous logs in to the `/boot/logs` directory. I did however also setup logging to a remote syslog server and have attached the diagnostics and the syslogs as well. I notice there was a lot of BTRFS errors and some kernel panics but not sure what to make of it. nas-diagnostics-20230909-0929.zip syslog-20230909.zip

My unraid server has been randomly freezing for awhile now.. 6+ months. I initially suspected it was due to my Ryzen 2700X CPU and tried various suggestions around c-state, power draw idle, etc. and none of them really solved the issue. During the onset of this issue, Unraid server would freeze every 3-5 days.. but in the past few weeks, it has been freezing every day. I would reboot the server after freeze, and it would happen the next day. Since Ryzen is known to cause freezes and hangs, I swapped out my CPU, RAM and Mobo to Intel Xeon E3-1245 v3. This was my old unraid hardware that had no issues in the past. I wanted a faster CPU so I upgraded to Ryzen. Swapping back to old hardware did not resolve my issue. Only changes I've made since upgrading from old Intel CPU to Ryzen CPU hardware is adding a 10GB NIC Card and replacing a faulty SAS expander card. I'm not sure what is causing it to freeze every day. I've attached my diagnostics. I would appreciate any help! Thank you! nas-diagnostics-20230906-1908.zip

Hello, I've been getting this error often lately and trying to figure out what is happening. When I go to Docker tab in Unraid, I get this error message and none of my Docker apps work. I have tried rebuilding the docker image few weeks ago and it worked for couple weeks and started happening again. Warning: file_put_contents(/var/lib/docker/unraid/images/plex-icon.png): failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 93 Warning: file_put_contents(/var/lib/docker/unraid/images/radarr-icon.png): failed to open stream: Read-only file system in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 93 I have attached the Diag zip file. What should I be looking for? Can someone please help? Thank you! nas-diagnostics-20230303-1705.zip

Hello, For past few months, my Unraid server has been periodically locking up and freezes completely causing a reboot to recover it. I have my Unraid set to log to a remote syslog server and I noticed bunch of warnings and errors right around 2/24 at 00:00 - 00:18 hours and starts with a general protection fault error. Can anyone please help me make sense of what could be the cause of my system freezes? Here's an export of my syslog. Thank you! All_2023-2-24-12_58_37.csv

Hello, I'm working on migrating my existing Unraid from Intel to AMD Ryzen and having some issues getting my 9211-8i card to recognize my hard drives. When I insert the 9211-8i card into any of the two PCIe x16 slots WITHOUT the GPU, it works fine. However, when I insert both GPU and 9211-8i, none of the drives are recognized by 9211-8i card. I have tried swapping the order of GPU and 9211 between either PICe x16 slots with no success. I have also attempted to reset CMOS, and BIOS without any success. I'm running latest F63a BIOS. Any suggestions? Thank you!

Thank you Cpt. Chaz for this solution. It was very helpful in getting my automated backup cron job set-up. I did however make a small tweak so that it calls the native unraid zip script directly as part of a backup script within the user script plugin. This way I only have to set-up 1 cron job. 🙂 #!/bin/bash #backup directory - update to target backup directory BACKUP_DIR=/insert/your/path/here echo "Creating backup directory if it doesn't exist" mkdir -p $BACKUP_DIR # unraid flash drive backup to zip via native backup script # backup saved to dir /usr/local/emhttp echo 'Executing native unraid backup script' /usr/local/emhttp/webGui/scripts/flash_backup echo "" echo 'Remove symlink from emhttp' find /usr/local/emhttp/ -maxdepth 1 -name '*flash-backup-*.zip' -delete sleep 5 echo 'Move Flash Zip Backup from Root to Backup Destination' mv /*-flash-backup-*.zip $BACKUP_DIR sleep 5 echo 'Deleting Old Backups' #ENTER NUMERIC VALUE OF DAYS AFTER "-MTIME +" find $BACKUP_DIR* -mtime +30 -exec rm -rfv {} \; echo 'All Done' ***Full disclosure - I don't assume any liability here for data loss or anything else. Use at your own risk!

Unplugged and plugged the Disk 7 back in, and stopped the array. When I did that, I noticed Unraid recognized the Disk 7 and I was able to choose it in the dropdown box for Disk 7. But for some reason, it's recognizing it as a new device and wants to rebuild it. This is what happened earlier this week and as soon as rebuild completed, Disk 7 went offline again. I've attached the latest diags. Any idea? Thanks. nas-diagnostics-20171005-2051.zip

Thanks Johnnie. Here's the new diags after I did a reboot. Now Disk 7 is showing red x and Not Installed... nas-diagnostics-20171003-1632.zip

One disk in my array was showing faulty (red x) over the weekend so I stopped the array, remove the disk, start array, stopped the array, added the disk, and started the array again which triggered the parity-sync/rebuild. That completed fine without any errors after about 13 hours but then it is showing faulty again due to read errors. Any idea what's causing it? Is it just a faulty hard drive? Thanks! nas-diagnostics-20171003-1544.zip

Ok cool. I'll give that a try. Thanks! Sent from my SM-G950U using Tapatalk

Hello, I woke up this morning to find all my user shares on Unraid 6.3.5 disappeared from the web GUI and I could not find them on the network. I tried stopping and starting the array service and it didn't recover the shares. Finally, stopped the array and reboot the system and all the shares were restored. I captured the diagnostic package before I rebooted just in case. Can anyone tell me from the diagnostics what went wrong? Thanks. nas-diagnostics-20170915-0744.zip

Yes, BIOS is up-to-date and I thought the same as well... I believe it's compatibility issue.. perhaps with the Linux kernel that's used in unraid...

So I've isolated the issue to my motherboard (asus p7h55d-m evo). When I boot up unraid on another server using the same SAS card, unraid detects the card fine and everything works. What's odd is that why does my Asus motherboard works just fine with the SAS card in Windows but fails in Unraid?

I updated the motherboard BIOS, downgraded the SAS card to P11 and still doesn't work..

Here's my diagnostics. I know the card work and all the cables are connected fine because it was a working system running Server 2016 with DriveBender couple hours ago until I rebuilt it as Unraid. I just did a firmware upgrade to v20.00.07.00 IT mode and that didn't fix it... tower-diagnostics-20170820-1641.zip It appears that it is failing to load the driver? Aug 20 16:40:03 Tower kernel: mpt2sas_cm0: diag reset: FAILED Aug 20 16:40:03 Tower kernel: mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8845/_scsih_probe()!

Hello, I just installed Unraid 6.3.5 and have a SAS9211-8i with firmware version 19 in IT Mode. I see that Unraid recognizes my SAS card but none of the hard drives attached are detected. I can confirm the drives are powered on and spinning with all connectors firmly connected. Any idea what's the issue? Thanks!

Awesome! I did not realize that feature existed. Is it fair to say that Write speed for array with no-parity drive vs array with parity mode set to turbo write are about equal?

Hello, I'm planning to migrate from DriveBender to Unraid and have a few questions I'm hoping I could get some help on... I'm running running NAS with DriveBender in mirrored setup on Server 2012 R2 with about 15TB of actual contents mirrored for total of 30TB. I want to re-use this NAS server as the Unraid and migrate all existing contents from DriveBender pool. I'm currently considering doing it in following steps... In DriveBender, disable mirror mode and delete all duplicate files. This will leave files scattered across 12 of the HDDs. Remove all HDDs from DriveBender except for 5x 4TB drives to force DriveBender to consolidate all files to only these 5 drives. Move the 5x 4TB HDDs to another server and restore the DriveBender pool (this is so I can still access the contents for a few days while I rebuild the existing NAS server as unraid). Install Unraid to the NAS server and create an unraid array using the 7 extra HDDs I recovered from consolidating DriveBender files from step 1. Copy all files from DriveBender pool I restored from Step 2 to the new Unraid array via SMB or via Unassigned Devices Plugin. I think the above steps will work.. although step 4 will take quite a bit of time.. Here are my questions: In step 3 when I create the unraid array, is it better to create the array with Parity disk or should I add the parity disk after all the files have been copied from Step 4? The reason I ask is because I'm concerned that by adding the parity disk first that my write speed will be impacted thus severely impacting the total time it takes to copy the data. Is it even possible to add a parity disk after the fact? Are there any issues with the steps I've outlined above? Thank you!

Hello, I am trying to test out unraid inside of my VM just to see if it would work before I commit to wiping my existing NAS and rebuilding it as Unraid as I don't have a spare physical PC to test it. When I try to test the Unraid via GUI web interface, I'm unable to do so because of registration error... I'm getting the following message... Is there any way I can get a trial key to test this out? Thanks! Error accessing your physical USB Flash boot device There is a physical problem acessing your USB Flash boot device. Please Contact Support. Flash GUID: Error code: ENOFLASH6