Marc_G2

Members
  • Posts

    72
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Marc_G2's Achievements

Rookie

Rookie (2/14)

5

Reputation

  1. Ah yes, thanks. It'd been so long since I configured my VM, I completely forgot about that. The issue is resolved now. I just need to edit it the correct way
  2. So this is my syslinux.cfg file that currently works. I thought I just needed to delete vfio-pci.ids=1022:43c7,1b73:1100 Is that not right? I attached my broken .cfg file. I know using notepad can cause issues. But I figured it would've fine for this. default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot vfio-pci.ids=1022:43c7,1b73:1100 label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest (broken) syslinux.cfg
  3. It turns out my issue was caused by something completely different. But I will keep that in mind going forward.
  4. At the moment it's set to 35 min after disks are spun down. I'll create a new thread if I can't figure it out in the next day or so.
  5. That's a good theory, but it looks like changing that setting didn't make a difference. I did recently change my default spin down time from 60 to 30 mins. But increasing it to 45 min didn't fix it either. For now I'll try a reboot to see if a setting isn't properly getting applied immediately or something. This was never a problem when prior to updating to 6.9.2. I only made a handful of small changes since that update. But I can't think of anything else that would cause this.
  6. So I was hoping this plugin could help me determine what was pinging my Cache SSD every 30 minutes (almost on the dot) which was preventing my system from going to sleep. But sadly the plugin doesn't detect anything. Do you have any advice? I already posted on the Dynamix thread. nas-ng-diagnostics-20210428-1559.zip
  7. Actually I found the exact cause. Apparently I can't competently delete something from the syslinux.cfg file. I got tire of seeing this warning from the fix common problems tool: vfio-pci.ids or xen-pciback.hide found within syslinux.cfg. For best results on Unraid 6.9+, it is recommended to remove those methods of isolating devices for use within a VM and instead utilize the options within Tools - System Devices. See HERE for more details I tried following the directions I saw here twice. But apparently I don't know what I'm doing. https://forums.unraid.net/topic/103525-vfio-pciids-found-within-syslinuxcfg/?tab=comments#comment-955697&searchlight=1
  8. Deleting all plugins didn't allow it to boot out of safe mode. So I guess that's ruled out
  9. So did it only work for you after you tried a third USB stick? Did you ever try booting in safe mode?
  10. Title says it all. Here's a photo of where it hangs. I've tried flashing to a different USB (same model), but that didn't work. It does boot in safe mode. But where do I go from here? Is it possible to revert back to 6.8.3? In unRAID it looks like there's an option. But it doesn't seem to be functional.
  11. I've just encountered this for the first time today. Still trying to deal with it. Could there be an issue with 6.9.2? It was working for me a while though.
  12. My server is set to go to sleep after an hour of inactivity. But for some reason the S3 plugin is detecting activity on one of my cache drives every 30 minutes like clockwork. This is a recent development so I though it may have been caused by a docker program after I moved the docker.img file to my cache. But disabling the docker service didn't fix the issue. Does anyone have an idea about what keeps pinging my cache drive? nas-ng-diagnostics-20210428-1559.zip
  13. I do have that checked. When it's checked, the options for 'preserve ownership, times' and 'preserve permissions' options become grayed out. You can toggle those two options if switch off NTFS mode first. But doing that didn't make a difference.
  14. I think I've fixed the spindown issues I was having. Updating unRAID to 6.9 fixed the unassigned drive and moving the docker Vdisk to the cache allowed the array to spin down. Anyway I'm backing up to an External NTFS drive and I'm getting a huge number of errors saying "failed to set times....... operation not permitted". Is there a way to fix this? Enabling the "attempt super-user activities" option didn't change anything.
  15. So these errors are a more concerning. Why am I getting drive errors right after they all spin down? The server is in maintenance mode at the moment, so does that have something to do with it?