January 17Jan 17 Hello,Just upgraded to 7.2.3 in the last couple of days. I stopped the array to change the server name (mysteriously changed to Tower...) and saw that there were several empty slots. I moved one of the data disks to an empty slot and saw "new device". Moved that drive back to its original slot and now it shows as unmountable. When the array is started that drive has a green ball, but still shows unmountable. Parity is valid. There have been no writes to the array since the update or after the failed drive move.Can this be recovered by doing a parity rebuild or is there another possibly better approach? The drive was full and has been in the array for years .Thanks in advance for any assistance!! nas1-diagnostics-20260117-1318.zip
January 17Jan 17 Community Expert Looks like the disk was still using an unaligned partition and lost that setting after the unassign and assign, which I believe should not happen.Post the output from fdisk -l /dev/sdjIn any case, and if parity is valid, a rebuild should resolve the issue, and as a bonus, rebuild to an aligned partition which is better for performance, so if you like, you can try unassigning the disk, starting the array, and seeing if the emulated disk mounts and looks OK, but if it doesn't mount, don't rebuild on top of the old disk.
January 17Jan 17 Author And the output of the fdsk command...>>>>>>>>>>>>>>root@NAS1:~# fdisk -l /dev/sdjDisk /dev/sdj: 1.82 TiB, 2000398934016 bytes, 3907029168 sectorsDisk model: ST2000DM001-9YN1Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 16773120 bytesDisklabel type: dosDisk identifier: 0xf935f989Device Boot Start End Sectors Size Id Type/dev/sdj1 64 3907029167 3907029104 1.8T 83 Linuxroot@NAS1:~#
January 17Jan 17 Author Thanks!!Unassigned the drive and restarted the array. After a looong wait, nearly 5 minutes, it's back with a red X in that position saying the drive is disabled but the contents are being emulated. Given that parity is good, I'm wondering if I should just go ahead and replace that drive. It's really old, now approaching 14 years in service. No SMART errors to speak of so I've been lucky. I assume I can replace it with a 4T drive? It's 2T now. The replacement can be here tomorrow.
January 17Jan 17 Community Expert Solution Emulated disk8 is mounted and nearly full. Should be OK to rebuild to a new drive.
January 18Jan 18 Community Expert 19 hours ago, Craigb said:Device Boot Start End Sectors Size Id Type/dev/sdj1 64 3907029167 3907029104 1.8T 83 LinuxThis confirms the starting sector changed to aligned. This looks like an Unraid bug, but I'll need to make some tests to confirm.P.S. Disk10 is also using an unaligned partition; you may want to correct that mostly for performance reasons; a rebuild on top will do it.
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.