October 19, 20232 yr Hi there, I am trying to complete my move to a new NAS. I am moving from QNAP to Unraid, so a bit of a newbie. I have installed Unraid 6.12.4 on an Asustor Flashstor 12 Pro FS6712X. AI populated it with 12 2TB NVMe drives. 1 parity, 11 data. I got about 70% of my data moved over and then Drive 2 was marked as failed. It now shows as no device. Drive 3 shows as missing now. Both drives do not show temp in the Array display. I have stopped the array and it will not start now. "Stopped. Invalid configuration." Any ideas on how to get back up? All hardware is new and this is first use. I booted to ADM when I took the NAS out of the box to verify it worked, then immediately installed Unraid via thumbdrive. Diagnostics attached. Thanks! ramonanas-diagnostics-20231019-0843.zip Edited October 19, 20232 yr by rcrafte posted ahead of finishing
October 19, 20232 yr Community Expert Both NVMe devices dropped offline, power cycle the server (not just reboot) and they shoudl come back, if yes try this, it helps in some cases: On the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 pcie_aspm=off e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off Then reboot and try again. P.S. NVMe devices would perform much better as part of a raidz zfs pool vs the array, but you would lose some flexibility.
October 19, 20232 yr Author Thanks for helping, I really appreciate it. Disk 2 shows red x and says device is disabled. Disk 3 shows as fine now. It is set to menu view already. I added the new line to the boot section. Stopped the array, reboot. Disk 2 shows red x and is disabled and contents emulated still but does appear in Identification. What's the right way to get things in good shape now? Should I rebuild from parity? On the separate issue of zfs, I am down to do it just so new I don't know where to start. I don't plan on adding any new media, it's fully populated already and all disks are 2TB and I don't plan on needing more ahead of upgrading hardware a few years down the line.
October 19, 20232 yr Community Expert Once a disk gets disabled it must be rebuilt: https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself Alternately you could do a new config and then run a parity check, assuming nothing was written to the emulated disk. 2 minutes ago, rcrafte said: On the separate issue of zfs, I am down to do it just so new I don't know where to start. I don't plan on adding any new media, it's fully populated already and all disks are 2TB and I don't plan on needing more ahead of upgrading hardware a few years down the line. You'd need to start over with the data, instead of assigning the devices to the array create a pool a zfs pool with them, note that for now at least one array data device is needed to start the array, but an old flash drive can fulfill that requirement.
October 19, 20232 yr Author Thanks Jorge. Did the amendment you gave me make NVMe better somehow? I have lost a bit of trust in Disk 2 and no idea why Disk 3 went wonky too. Rebuilding now in maintenance mode. Once completed, I'll move everything back to QNAP, nuke the Array, and start the ZFS journey. Is there a guide you can point me at so I stay on path?
October 19, 20232 yr Community Expert Just now, rcrafte said: Did the amendment you gave me make NVMe better somehow? It may or not help, but unlikely that it was a device problem, possibly that model devices have some issues with the kernel and/or the hardware used.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.