February 26, 20251 yr Dear community, Been using unraid for over a year, and earlier this year data disk one reports a failure, after trying self-rebuild learned from the manual with no luck, I decided to swap the failed disk with a bigger one, thus I followed the instruction step by step for a parity swap. Fomer config Parity: 4t Data disk 1: 2t Data disk 2: 4t Data disk 3: 4t New config Parity: 16t Data disk 1: 4t (formerly parity disk) Data disk 2: 4t (formerly disk 2) Data disk 3: 4t (formerly disk 3) Upon parity swap, I shut array down, unassign failed disk (showing content emulated), shut down, turn on, unassign the old 4t from parity, assign the new 16t as new parity, and reassign the former 4t parity as data disk 1, as the main page showed the config is valid, I started the move process, after it's done, the copy buttons showed up, thence I started the copying. So far I believe I followed every step of the instruction. Stupid as I was when I saw the estimate time rised up to 100 days, I stopped the process, and the array won't start ever since. Upon start of the machine without auto disk start, a valid config shows as above, and hit start, it only shows 'array is starting' and takes like forever but won't start.. tried several times.. Did I break anything when I canceled the copy process of data-rebuild? Anyone might help with any idea on the situation? Thanks in advance.
February 26, 20251 yr Author On 2/26/2025 at 8:15 PM, trurl said: Attach Diagnostics to your NEXT post in this thread. Thank you for your prompt reply, please see attached diagnostic zip. To my surprise the array was started and all services on the run about 50mins ago. However on the main page, it says data-rebuild in progress while a format button appears for the old 4t disk at the same time, says needs formatting. Please see the following screenshot also showing the estimated time of over 100days.. The gui shows writes into this disk, but how is it unmounted at the same time? Thank you! Edited February 28, 20251 yr by Zzzen
February 26, 20251 yr Community Expert Do you remember if disk1 was unmountable before you started all this? DO NOT FORMAT. We will have to check filesystem after rebuild.
February 26, 20251 yr Community Expert 2 hours ago, Zzzen said: Did I break anything when I canceled the copy process of data-rebuild? Maybe. Do you still have original disk1?
February 26, 20251 yr Community Expert Solution Looks like you were having connection problems. Probably best to stop and check connections. Do you know what was wrong with original disk1? Is original disk1 still attached?
February 26, 20251 yr Author Thank you for the reply! 5 minutes ago, trurl said: Do you remember if disk1 was unmountable before you started all this? DO NOT FORMAT. We will have to check filesystem after rebuild. No, I didn't unmount any disk the during this whole operation. And sure, I won't format, as it's still greyed out, though I wonder if this is prepared for the disk when complete data-rebuild? And for the estimated 100 days, I haven't checked if I have full access to the files yet, but if the data remains intact I don't mind 100days of rebuild lol One more thing, I originally had two shares, one was exclusively assigned to 2t disk1, while the other assigned to the other 4t disks. When the failure warning turned up, I re config the share of disk1 to disk2 & 3, excluding disk1. (Maybe I was thinking this might activate some sort of data moving between disks). And during the several self rebuild processes, I saw the exact share folder appeared in the disk2 & 3, I presume maybe the data was indeed or partially moved? 4 minutes ago, trurl said: Maybe. Do you still have original disk1? Yes, the original 2t disk 1 still in hand. If you have any idea on how I may deal with this, please let me know. Appreciate your time and help!
February 26, 20251 yr Community Expert 1 minute ago, Zzzen said: No, I didn't unmount any disk the during this whole operation. That isn't what I asked. I asked if disk1 was unmountable. 2 minutes ago, Zzzen said: I haven't checked if I have full access to the files yet Not possible to access anythiing on an unmountable disk. 3 minutes ago, Zzzen said: I re config the share of disk1 to disk2 & 3, excluding disk1. (Maybe I was thinking this might activate some sort of data moving between disks) Changing those settings only affects new files. Nothing was moved. 3 minutes ago, Zzzen said: Yes, the original 2t disk 1 still in hand. Do you have a free SATA port you can plug it in to?
February 26, 20251 yr Author 8 minutes ago, trurl said: Looks like you were having connection problems. Probably best to stop and check connections. Do you know what was wrong with original disk1? Is original disk1 still attached? Yes, the network was down for a while as I was upgrading the home network setup, and also I added a pcie NIC earlier today, went back and forth with the configs of interfaces for a while, but no actual connection problems that I recall. And the machine is currently online, connections are fine for now. Is the diagnostic showing any specific problem? Sorry I'm not a real superuser, not so good at reading through all the reports. I remembered getting a smart report of the disk, let me see if I can still find it on my PC later. Thanks for the help!
February 26, 20251 yr Author 2 minutes ago, trurl said: That isn't what I asked. I asked if disk1 was unmountable. Matter of fact I did changed the config once before starting the array when I found it not starting, I changed the disk 1 slot to a 5th new disk attached, and the config was valid and I hit the start button, and 30mins later I shutdown before it actually started. I believe this did unmounted the disk during that once start-up.. I was too eagerly trying to get it started.. 7 minutes ago, trurl said: 8 minutes ago, trurl said: Do you have a free SATA port you can plug it in to? Yes I do have ports available for the disk. What shall I do?
February 26, 20251 yr Community Expert 13 minutes ago, Zzzen said: the network was down for a while as I was upgrading the home network setup, and also I added a pcie NIC earlier today, went back and forth with the configs of interfaces for a while, but no actual connection problems that I recall. I meant the disks were having connection problems, nothing to do with the network. It is very common to disturb SATA or power connections whenever you have the case open for some reason. The disk connectors aren't really firm connections. This is definitely the main reason people have problems when adding, removing, or replacing disks. 10 minutes ago, Zzzen said: I did changed the config once before starting the array when I found it not starting, I changed the disk 1 slot to a 5th new disk attached, and the config was valid and I hit the start button, and 30mins later I shutdown before it actually started. I believe this did unmounted the disk during that once start-up.. I was too eagerly trying to get it started.. That will not have made the disk unmountable. It is unmountable because it doesn't have a valid filesystem, or because its filesystem is corrupt, so the OS can't access its files. Maybe it was already unmountable before you started any of this and you just hadn't noticed. Or maybe incomplete parity copy made the emulated disk unmountable. 5 minutes ago, Zzzen said: Yes I do have ports available for the disk. What shall I do? Go to Settings - Disk Settings, and disable autostart. Shutdown, check all connections, SATA and power, both ends, including splitters. Plug original disk1 in, but don't assign it. Boot up, don't start the array yet. Post new diagnostics.
February 26, 20251 yr Author On 2/26/2025 at 11:16 PM, trurl said: I meant the disks were having connection problems, nothing to do with the network. It is very common to disturb SATA or power connections whenever you have the case open for some reason. The disk connectors aren't really firm connections. This is definitely the main reason people have problems when adding, removing, or replacing disks. That will not have made the disk unmountable. It is unmountable because it doesn't have a valid filesystem, or because its filesystem is corrupt, so the OS can't access its files. Maybe it was already unmountable before you started any of this and you just hadn't noticed. Or maybe incomplete parity copy made the emulated disk unmountable. Go to Settings - Disk Settings, and disable autostart. Shutdown, check all connections, SATA and power, both ends, including splitters. Plug original disk1 in, but don't assign it. Boot up, don't start the array yet. Post new diagnostics. Thank you for explaining. I see it might be the physical connection as I've opened several times these days. I've re-pluged everything firmly. Original failed disk attached, unassigned, array not started, diagnostics as attached. Thanks! Edited February 28, 20251 yr by Zzzen
February 26, 20251 yr Community Expert Is unassigned disk sdg the original failed disk? I'm not getting much of a SMART report for that one even though it looks like it is plugged in to the same controller as the other disks.
February 26, 20251 yr Author 16 minutes ago, trurl said: Is unassigned disk sdg the original failed disk? I'm not getting much of a SMART report for that one even though it looks like it is plugged in to the same controller as the other disks. Yes sir, sdg is the original failed disk. The machine has 6 sata ports splitting into 3 controllers each with 2 slots, if this is what you were referring to. 22 minutes ago, trurl said: Install Unassigned Devices plugin Confirm plugin installed. Waiting for instructions. Thx!
February 26, 20251 yr Author 3 minutes ago, trurl said: Post a screenshot of Main - Unassigned Devices Screenshot attached.
February 26, 20251 yr Author 3 minutes ago, trurl said: Looks like sdg is also unmountable. What is sdf? Sdg is the 6th new disk, prepared for expansion. Edited February 26, 20251 yr by Zzzen
February 26, 20251 yr Community Expert 16 minutes ago, Zzzen said: Sdg is the 6th new disk, prepared for expansion. 54 minutes ago, Zzzen said: sdg is the original failed disk. Which is it? 20 minutes ago, trurl said: What is sdf? Where did sdf come from? It isn't new since it seems to be mountable.
February 27, 20251 yr Author 3 hours ago, trurl said: Which is it? Where did sdf come from? It isn't new since it seems to be mountable. Sorry my typo, sdg, 2t, the original failed disk, sdf, 16t, a new complete disk.
February 27, 20251 yr Community Expert 51 minutes ago, Zzzen said: sdf, 16t, a new complete disk. Was it ever assigned in Unraid? Was it ever used elsewhere? Just wondering why Unassigned Devices seems to think it has a mountable filesystem. In those last diagnostics, you seemed to still be having connection problems with sdg, the original failed disk. Or maybe it just isn't responding. Check its connections again, maybe try another cable (while being careful with other connections), and post new diagnostics.
February 27, 20251 yr Author 2 hours ago, trurl said: Was it ever assigned in Unraid? Was it ever used elsewhere? Just wondering why Unassigned Devices seems to think it has a mountable filesystem. In those last diagnostics, you seemed to still be having connection problems with sdg, the original failed disk. Or maybe it just isn't responding. Check its connections again, maybe try another cable (while being careful with other connections), and post new diagnostics. I think the following I did was why sdf thinks it has a valid filesystem because when I was messing up to start it I put it in the parity swap slot in the config to try if it can be started.. 12 hours ago, Zzzen said: Matter of fact I did changed the config once before starting the array when I found it not starting, I changed the disk 1 slot to a 5th new disk attached, and the config was valid and I hit the start button, and 30mins later I shutdown before it actually started. As for sdg, I've tried changing it's physical slots, re connect, but I think the disk itself may be broken physically, as it's buzzing when spinning.. could this be reported as the connection problem? Thanks!
February 27, 20251 yr Author Or perhaps there is any way to stop this rebuild process, to totally ignore the swapping and copying and add back sdb formatted as new while remain the other disks and array config untouched? I can withstand the minor data loss of that one disk. Thank you!
February 27, 20251 yr Community Expert 10 hours ago, Zzzen said: add back sdb formatted as new Not sure I follow you there. sdb was parity in those last diagnostics, and parity has no format.
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.