• Content count

  • Joined

  • Last visited

  • Days Won

    14 last won the day on April 27 had the most liked content!

Community Reputation

136 Very Good



  • Rank
    If you don't see someone say something


  • Gender

Recent Profile Visitors

347 profile views
  1. You can do it like this: New config - assign all new smaller disks except the 3TB as parity, leave parity unassigned Mount parity with the UD plugin (or in the cache slot) Rsync or use your favorite tool to copy everything from UD disk to array When done assign 3tb as parity and start array to begin parity sync
  2. <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='unmap'/> <source file='/mnt/disks/840EVO/VMs2/Win10/vdisk1.img'/> <target dev='hdc' bus='scsi'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> And you need to add the controller: <controller type='scsi' index='0' model='virtio-scsi'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </controller>
  3. Using virtio-scsi together with discard='unmap' allows the vdisk to keep its "sparseness", i.e., Windows 8/10 detects the storage as thin provisioned and space is recovered immediately when a file is deleted on the vidisk, allowing the vdisk to remain as small as possible and for those sectors to be trimmed by fstrim when using the vdisk on an SSD. After changing to that controller it's also possible to run defrag to recover all unused space. It's now possible to add the virtio-scsi controller and change the bus by editing the XML but changes will be lost in any futures edits with the VM editor.
  4. You can also swap that disk with another using the same or different enclosure, if the same disk keeps failing it can be bad despite the healthy SMART.
  5. If it's not on bios 2.0 it will only boot with a Skylake CPU, if it had IPMI you could use it to update, although you'd need to pay Supermicro for a key.
  6. Kabylake on X11 requires bios 2.0, it's probably still on an older bios, you need to use a Skylake CPU to update the bios. I just recently bough an X11SSM-F and had to do the same.
  7. I had the same problem, out of memory errors after running the mover, from what I've read they are quite common with kernels 4.8 and 4.9, apparently fixed on kernel 4.10, but unRAID is still on 4.9. Since then I decreased my RAM cache and so far no more OOM errors, you could try the same, manually or using the Tips and Tweaks plugin. Values to change are vm.dirty_background_ratio and vm.dirty_ratio, default is 10 and 20, I set mine to 1 and 2, this also helped other users with same issue, so worth a try.
  8. To me looks more like a controller problem, there were issues with ata9 and then ata8. Check all cables and make sure the controller is well seated.
  9. Redo you flash drive, re-assign all disks in the same order as they were and trust parity before starting the array, all shares will be recreated but revert to default settings.
  10. Sorry, but by the way you talked of different results every time I assumed you never used it, because the results are always repeatable. In terms of predicting failure, I can only say that in my experience when disks start to get slow sectors like those above is just a question of time before they fail, but like all predictions it's not always right. i.e., a disk can keep working with slow sectors for a long time and most disks fail before slow sectors start showing.
  11. Grab the diagnostics on the console by typing diagnostics and then reboot by typing powerdown -r
  12. Try a different USB port, USB2 is more reliable than USB3, failing that get a new flash drive.
  13. I can repeat the scan 10 times and results will be practically identical, same for the disks with normal response times, have you ever used that program? if you try it you'll see results are very consistent.
  14. That one is Marvell also, it should work OK as long as don't use virtualization passtrough.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.