• Posts

  • Joined

  • Last visited

Posts posted by Marc_G2

  1. I have got an issue with the sleep plugin.  If I set it to monitor disk status, it ends up monitoring my ssd cache (which never goes into a spun down state), and so it never goes to sleep.  Is there a work around for this?

    • Upvote 1
  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. 13 minutes ago, xylcro said:

    I tried a couple of USB 3.0 drives and got an error on everyone of them, finnaly I tried a random USB 2.0 I had laying around and it worked on the first time. So maybe if you're using USB 3.0, switch to USB 2.0

    It turns out my issue was caused by something completely different.  But I will keep that in mind going forward.

  4. 1 hour ago, SimonF said:

    I suspect its because you have the following set for smart polling.  poll_attributes="1800" which will be 30mins. What is the time for your sleep? Try changing poll to 3600 to see if that fixes issue.

    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.

  5. 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.


  6. 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?


  7. 43 minutes ago, ich777 said:

    I don't think that NTFS supports this feature but could be maybe be wrong on that.

    Have you also ticked the box where it says that this is a FAT/NTFS drive in the advanced options dialogue in luckyBackup?

    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.  

  8. 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.



  9. I put system to sleep and woke it again with the array stopped.  And then tried starting it in maintenance mode.  I'm not getting fault so far.  My guess is the BIOS update fixed the issue.  I'd appreciate it if someone knowledgeable could look at this log after wake up to see if there's anything concerning.  


    The one concerning thing I saw was a warning.  

    ata4: COMRESET failed (errno=-16)


  10. Just now, JorgeB said:

    Have you tried not sleeping the server? Not every hardware supports sleep/wake up correctly.

    That's something that crossed my mind.  But I'm pretty sure that first time this issue happened was shortly after a boot up before ever going to sleep.  Later today I'm going to see if I can trigger the error by putting it to sleep and waking it up again. And just starting and stopping the array.


    Is there the a way to configure unRAID to better handle this error?  Could I make unRAID immediately stop the array once it starts seeing this particular fault?  The way unRAID disables one of my disks after trying repeated resets is major a headache.  

  11. 11 minutes ago, Vr2Io said:

    Previous reply amend

    You should disconnect the SATA link at disk side one by one ( HBA disk only, stop array ), then keep track web log until HBA no more reset, this could narrow down the cause a bit.

    The problem is there's no errors most of the time.   So if the array isn't active, it seems especially unlikely for the error to occur.   


    What line in the system log did you find that the issue started with disk 3?

  12. 2 minutes ago, Vr2Io said:

    Problem seems on ST4000VN000-2AH166 ( disk 3 ), it haven't response to HBA on-time, so HBA reset again and again, this will affect all disk which connect to HBA.


    You should disconnect the SATA link at disk one by one, then keep track the log until HBA no more reset, this could narrow down the cause a bit.

    That would show up as an error in the system log right?  The problem there is my disks are getting disabled which requires a full rebuild afterward.  I swapped the sata cables and I'm doing rebuild right now.  I haven't seen any errors yet.