Farvneho

Hello, I have an Unraid Basic installation that's all set up. A family member just gave me a USB disk with Unraid Pro on it, which is great because I want to use more drives. Do I just need to copy over the /config folder, or is there more to migrating my installation? Thanks in advance!

Thank you for this. I think this is why my VM was lost. What I am going to do from now on is have a cache pool so there is at least some redundancy even if a VM is running from the cache. I could go through the trouble of shutting the machine down before Mover starts, but it's a Minecraft server and people like to afk.

I have been using Unraid for about 2 years, with 4 platter drives and 1 SSD cache. On Sunday, the 10-year-old SSD failed, but took with it an entire VM which was not being moved to the proper part of the array. I am not using Mover Helper. The share settings are as follows: And the logs from the last mover instance run before the drive failure show: Apr 25 03:40:07 holly move: move: file /mnt/cache/appdata/swag/keys/letsencrypt Apr 25 03:40:07 holly move: move_object: /mnt/cache/appdata/swag/keys/letsencrypt No such file or directory Apr 25 03:40:07 holly move: move: file /mnt/cache/appdata/swag/etc/letsencrypt/keys/0015_key-certbot.pem Apr 25 03:40:07 holly move: move: file /mnt/cache/appdata/swag/etc/letsencrypt/csr/0015_csr-certbot.pem Apr 25 03:40:07 holly move: move: skip /mnt/cache/domains/Debian/vdisk1.img Apr 25 03:40:07 holly root: mover: finished Apr 25 14:16:54 holly emhttpd: read SMART /dev/sdb Apr 25 14:30:30 holly kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 25 14:30:30 holly kernel: ata4.00: failed command: FLUSH CACHE Apr 25 14:30:30 holly kernel: ata4.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 17 Apr 25 14:30:30 holly kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 25 14:30:30 holly kernel: ata4.00: status: { DRDY } Apr 25 14:30:30 holly kernel: ata4: hard resetting link Apr 25 14:30:35 holly kernel: ata4: link is slow to respond, please be patient (ready=0) Apr 25 14:30:40 holly kernel: ata4: COMRESET failed (errno=-16) Apr 25 14:30:40 holly kernel: ata4: hard resetting link Apr 25 14:30:45 holly kernel: ata4: link is slow to respond, please be patient (ready=0) Apr 25 14:30:50 holly kernel: ata4: COMRESET failed (errno=-16) Apr 25 14:30:50 holly kernel: ata4: hard resetting link Apr 25 14:30:55 holly kernel: ata4: link is slow to respond, please be patient (ready=0) Apr 25 14:31:25 holly kernel: ata4: COMRESET failed (errno=-16) Apr 25 14:31:25 holly kernel: ata4: limiting SATA link speed to 3.0 Gbps Apr 25 14:31:25 holly kernel: ata4: hard resetting link In every instance of that vdisk, it seems to skip moving it. I'm planning to install a new cache drive this weekend, and I don't want this to happen again. What could have caused this? Thanks for your help.