November 11, 20196 yr I did some upgrades this weekend. I had a 10TB parity drive and swapped it out for a 12TB in preparation for some HD size upgrades. I replaced a 3TB with the new 12TB. I then changed the parity from the 10TB to the new 12TB. The parity copy took about 24 hours, but it all completed. I then reassigned the 10TB that was my parity to be a data drive. I did the reassignments and then started the array so the 10TB could go through data rebuild. From reading numerous posts, while this operation was taken place, my server should have function normally, albeit slow, while this was happening. My shares were not available and Docker and VMs could not start because they had missing paths (appdata and domains). Is this normal? I still need to replace two 3TB drives with two new 12TB drives, but I am afraid to start this procedure for fear that my server will be useless for another two to three days. Can anyone comment or guide me on what I may be doing wrong?
November 11, 20196 yr Community Expert It should be available! Does the drive being rebuilt show as being mountable? If it does not then there may be corrupt at the file system level and a repair needs running.
November 11, 20196 yr Author I used this procedure for this operation... https://wiki.unraid.net/The_parity_swap_procedure
November 11, 20196 yr Author The only thing that stands out in the logs, barring the backups that are trying to be performed but can't, is this block. Nov 11 05:30:16 Musial emhttpd: shcmd (4942): /usr/sbin/hdparm -y /dev/nvme1n1 Nov 11 05:30:16 Musial root: HDIO_DRIVE_CMD(standby) failed: Inappropriate ioctl for device Nov 11 05:30:16 Musial root: Nov 11 05:30:16 Musial root: /dev/nvme1n1: Nov 11 05:30:16 Musial root: issuing standby command Nov 11 05:30:16 Musial emhttpd: shcmd (4942): exit status: 25
November 11, 20196 yr Community Expert This is what stands out to me: Nov 10 13:52:00 Musial emhttpd: error: get_filesystem_status, 6589: Operation not supported (95): getxattr: /mnt/user/test Not sure what's causing this but it's preventing Unraid for mounting user shares, try again after rebooting.
November 11, 20196 yr Author I just found those messages as well. I am at 93% on my data rebuild. After it is done, I will reboot and report back.
November 11, 20196 yr Author Once the rebuild completed, I rebooted the system. All came back fat and happy. The error messages are no longer appearing in the syslog. I will now move onto replacing a 3TB drive with a 12TB drive and allowing parity to rebuild the data drive. Cross your fingers.
November 19, 20196 yr Author After two and a half days, and a reboot, all went back to normal. Thanks for the help.
Archived
This topic is now archived and is closed to further replies.