Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. I'm going to say no. I had one of those ca plugins that did weekly backups, however, the folder it backs up to is a share on the array which I don't have access to now. I assume that ca plugin did a flash backup.
  3. Hi folks - I have a similar scenario. I have been running this Unraid array for years and notwithstanding a few new hard disks replacing some older ones, have had no issues with this array until today when one of my drives has become "red-balled" - or "Red X". I have undertaken a Smart Diagnostic Report and it doesn't appear to have any issues with the key stats of "Red Read Error rate" and "reallocated sector". Before rebuilding the drive from my parity (which is valid) I wanted to see if someone who is more knowledgeable about reading these SMART reports can check this drive to see whether it is indeed developing issues and should be replaced, or whether it is reasonably safe to rebuild to the same disk. SMART report attached. Thanks in advance. Best wishes Mike. WDC_WD20EARX-00PASB0_WD-WCAZAD181918-20200120-1457.txt
  4. thank you so much for the hardwork! rocking your plugin now
  5. I suddenly started seeing really slow transfer speeds (1 MB/s) to my UnRAID shared folders. A network test using a LAN Speed Test utility (from https://totusoft.com/lanspeed) confirmed that the server network adapter is only running at 10 mbps. Why would the network adapter suddenly drop its speeds to 10 mbps? Is that something that can be changed within UnRAID? (According to the specs it's supposed to be a 10/100/1000 adapter.) If the network adapter has suddenly flaked out can I install a PCIe network card? Any thoughts? I've attached the diagnostics if it will help. tower-diagnostics-20200120-0409.zip
  6. Added the linux in-tree driver to upcoming 6.8.2 release.
  7. got the firmware updated. Didn't get greeted w/a ton of udma crc errors (fingers crossed). Currently rebuilding array due to the disabled disk. Hope this works.
  8. You really should just take some time to determine what is truly important enough that you can't afford to lose it. Most likely it won't require a lot of capacity. Then just back that up to disks outside the array (those disks in the drawer after you weed out the bad ones). That is probably going to be a better approach than what you are considering.
  9. was something i wanted to do too. seems like a limited use. wish more info was out and test streams.
  10. Most likely just filesystem overhead and no actual files.
  11. I just upgraded to the 6.8.1 nvidia plugin from 6.8.0 nvidia plugin. Now the server will not boot. On the screen it keeps saying system initializing and stays like that forever. I tried a hard power off multiple times and even unplugged/turned off the power supply and the issue is the same. I really would appreciate any help since I do not know what else to do. Thanks.
  12. I just did a test with a 2 cpu vm and ran a process to max both cores continually while I could monitor the cpu load in htop on the unraid server. For me I could see the 2 cpu cores at 100% roam around the host CPU cores ‘randomly’ so it does allow threads to move around. No clue if it will be faster that way or slower but would be keen to know also.
  13. I am running 6.7. It is strange that the disk appears have rebuilt with 5.4GB of data. On the bright side I now have approx 4TB free Thanks for help, If anything happens again I will reach out before attempting to screw it up.
  14. Today
  15. Just updated and it's all up and running. Thanks so much!
  16. Good day, Disclaimer, I'm also new to unraid so take what I tell you with a grain of salt, having recently done some research for a mother board myself for unraid id like to share what little I know. Seeing that your considering ryzen 3600, I'd go with a mother board that had onboard VGA, as unraid needs a primary gpu to boot, if you don't you'll end up using one of your precious pcie x16 slot for a lame gpu just to get it to boot, which is not cool. My recommendation is Asrock X470D4U. Also has IPMI for remote management, no extra license to purchase to get full access to your mobo, (unlike supermicro). Availability of these boards are an issue but they are in and out if stock quickly. Hope this helps, Regards, Shane. Sent from my iPhone using Tapatalk
  17. Parity can't help if any of the remaining drives have errors. All drives in the parity array must be fully trustworthy. I don't know of any plugins that do what your are asking, but a one line rsync command for each share in user scripts set to run periodically could do it. Honestly it sounds like you are headed for major data loss, unless the strategy changes drastically.
  18. Is anyone using the HP290 (G4900) with Plex Pass and a DVR (HD HomeRun). I'm getting an "This live TV session has ended" when trying to tune, but it works fine from my dekstop plex server (4770k). Is there some config to do to the docker to make it work? The tuner setup worked just fine.
  19. This seems interesting, an I certainly won't mind trying it. It'll be the first thing I try in the morning, thanks! And of course I'll be back to report findings
  20. @Benjamin Picard @wreave Pushed a new build. I think it should be good, but had some issues with the overall build process and did it manually, and it's half two in the morning, so be grateful if you can test and let me know.
  21. Hopefully this is the right spot for this question! I'm using an ASrock 970 Extreme3. When I use the S3 Sleep Plugin to put the system to sleep, the front LED blinks. According to The Manual blinking means S1 Sleep. PLED (System Power LED): LED is on when the system is operating. The LED keeps blinking when the system is in S1 sleep state. The LED is off when the system is in S3/S4 sleep state or powered off (S5). This seem to indicate the system is in S1 sleep and not S3. This would explain why I can't wake it up using etherwake -i eth0 xx:xx:xx:xx:xx:xx From my raspberry pi. Is there a way to verify what sleep state it's in? I have "Suspend to Ram: Auto" (manual page 50) Selected in BIOS. Or why my Wake on Lan isn't working? I do have "PCI Devices Power On"(manual page 50) enabled in the BIOS as well. Thank you! Below is an excerpt of the s3_sleep log. Not sure if it would shed any light: Jan 19 20:00:42 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:43 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:45 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:45 Tower s3_sleep: ---------------------------------------------- Jan 19 20:00:45 Tower s3_sleep: command-args=-C 1 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -m 30 -e eth0 -N 0 -D 0 Jan 19 20:00:45 Tower s3_sleep: action mode=sleep Jan 19 20:00:45 Tower s3_sleep: check disks status=no Jan 19 20:00:45 Tower s3_sleep: check network activity=no Jan 19 20:00:45 Tower s3_sleep: check active devices=no Jan 19 20:00:45 Tower s3_sleep: check local login=no Jan 19 20:00:45 Tower s3_sleep: check remote login=no Jan 19 20:00:45 Tower s3_sleep: version=3.0.6 Jan 19 20:00:45 Tower s3_sleep: ---------------------------------------------- Jan 19 20:00:45 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:00:45 Tower s3_sleep: excluded disks=sda Jan 19 20:00:45 Tower s3_sleep: ---------------------------------------------- Jan 19 20:00:45 Tower s3_sleep: s3_sleep process ID 9973 started, To terminate it, type: s3_sleep -q Jan 19 20:00:46 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:47 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:48 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:17 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:18 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:19 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:21 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:21 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:21 Tower s3_sleep: command-args=-q Jan 19 20:02:21 Tower s3_sleep: action mode=sleep Jan 19 20:02:21 Tower s3_sleep: check disks status=no Jan 19 20:02:21 Tower s3_sleep: check network activity=no Jan 19 20:02:21 Tower s3_sleep: check active devices=no Jan 19 20:02:21 Tower s3_sleep: check local login=no Jan 19 20:02:21 Tower s3_sleep: check remote login=no Jan 19 20:02:21 Tower s3_sleep: version=3.0.6 Jan 19 20:02:21 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:21 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:02:21 Tower s3_sleep: excluded disks=sda Jan 19 20:02:21 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:21 Tower s3_sleep: killing s3_sleep process 9973 Jan 19 20:02:22 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:22 Tower s3_sleep: command-args=-C 1 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -a -m 30 -n -e eth0 -N 0 -D 0 Jan 19 20:02:22 Tower s3_sleep: action mode=sleep Jan 19 20:02:22 Tower s3_sleep: check disks status=yes Jan 19 20:02:22 Tower s3_sleep: check network activity=yes Jan 19 20:02:22 Tower s3_sleep: check active devices=no Jan 19 20:02:22 Tower s3_sleep: check local login=no Jan 19 20:02:22 Tower s3_sleep: check remote login=no Jan 19 20:02:22 Tower s3_sleep: version=3.0.6 Jan 19 20:02:22 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:22 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:02:22 Tower s3_sleep: excluded disks=sda Jan 19 20:02:22 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:22 Tower s3_sleep: s3_sleep process ID 10561 started, To terminate it, type: s3_sleep -q Jan 19 20:02:22 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:23 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:24 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:25 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:23:25 Tower root: plugin: running: anonymous Jan 19 20:25:49 Tower kernel: i2c /dev entries driver Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: command-args=-q Jan 19 20:27:28 Tower s3_sleep: action mode=sleep Jan 19 20:27:28 Tower s3_sleep: check disks status=no Jan 19 20:27:28 Tower s3_sleep: check network activity=no Jan 19 20:27:28 Tower s3_sleep: check active devices=no Jan 19 20:27:28 Tower s3_sleep: check local login=no Jan 19 20:27:28 Tower s3_sleep: check remote login=no Jan 19 20:27:28 Tower s3_sleep: version=3.0.6 Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:27:28 Tower s3_sleep: excluded disks=sda Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: killing s3_sleep process 10561 Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: command-args=-C 1 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -a -m 30 -n -e eth0 -N 62500 -D 0 Jan 19 20:27:28 Tower s3_sleep: action mode=sleep Jan 19 20:27:28 Tower s3_sleep: check disks status=yes Jan 19 20:27:28 Tower s3_sleep: check network activity=yes Jan 19 20:27:28 Tower s3_sleep: check active devices=no Jan 19 20:27:28 Tower s3_sleep: check local login=no Jan 19 20:27:28 Tower s3_sleep: check remote login=no Jan 19 20:27:28 Tower s3_sleep: version=3.0.6 Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:27:28 Tower s3_sleep: excluded disks=sda Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: s3_sleep process ID 18608 started, To terminate it, type: s3_sleep -q Jan 19 20:37:19 Tower emhttpd: req (3): startState=STOPPED&file=&csrf_token=****************&cmdStart=Start Jan 19 20:37:21 Tower emhttpd: shcmd (2755): /usr/local/sbin/set_ncq sdb 1 Jan 19 20:37:21 Tower kernel: mdcmd (46): set md_num_stripes 1280
  22. Well you could disable pinning and let the CPU use its own optimisation algorithm to roam the threads as it sees fit. It seems like a newer cpu so it might be better than trying to manually do it (or not in which case just change it back). To do this I would set threads back to 1 and cores to 44 then in each of the 44 lines regarding the cpu pin (cpuset) let them roam any of the 48 cores as they need to... so I will edit the first 4 (to show an example), but you can do all 44 lines. placement='static'>44</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0-47'/> <vcpupin vcpu='1' cpuset='0-47'/> <vcpupin vcpu='2' cpuset='0-47'/> <vcpupin vcpu='3' cpuset='0-47'/> also each of the numbers can be sequential now for the vcpu, 0,1,2,3...43 (43 is 44 cpus as 0 counts as the first one) rather than out of order in your current config. I am thinking this might be faster as a maxed core in the vm is no longer constrained to a domain on the cpu where a possibility may arise where its HT partner is also maxed, which would hamper performance (possibly). Sorry in advance if this is wrong, but the red hat documentation suggests this scenario is possible and this could work around such an eventuality. Dont hate me if its wrong I havent tested it. p
  23. Yeah, what's the idea? I have tomorrow off of work so I plan on hammering away at this issue as much as I can!
  24. I have been reading the kvm documentation and have another idea... its fairly dramatic and might make performance worse you want to try it anyway if you have time for testing?
  25. So after a few tests, here's what's occuring. It's not a time delay. It's only making one directory at a time on /mnt/cache to match what is on /mnt/user/. What could possibly be causing this? Persisted across reboots. After this next preclear, I'll be running in safe mode without plugins to see if it still occurs. Test command: while (true); do tree /mnt/cache/Archive; touch a; tree /mnt/cache/Archive; echo "Sleeping for 5 seconds..."; sleep 5; done So, after touching a file, it makes the first missing directory instantly. After 5 seconds, you can see no more have been made. Full output of that command: 20200119_unraid_cache_write_issue.log
  26. I have zero desire in creating any more custom Unraid builds. Currently the Nvidia one technically isn't a custom kernel as I change nothing there, it's more about adding extra packages and custom container runtime. DVB adds DVB drivers and some extra firmware (LibreELEC version) TBS and Digital Devices are completely different branches on the media_tree. I did help with the HP RMRR version as well, but I don't maintain it, and iirc there's currently no kernel patch for the kernel version we're using anyway. I had a play around with some docker swarm kernel parameters a while ago but that's about it. I don't enable anything else custom and don't want to.
  1. Load more activity