Goreliann

Can anyone that can actually read diagnostics tell me why I've lost a disk? I have no idea if it's a bad disk or a connection issue or what. TIA storage-diagnostics-20240626-1737.zip

I have no idea what it's actually called. I just explore the files on the Main screen. Either way, I used the Terminal to copy everything to where I can manage the files via Windows. I seem to have figured it out. I've also found there's a lot more missing than just what's in the lost and found, but again, comparatively little so I can live with that. I'll just go about replacing it all. Thanks for all your help.

So I can terminal command copy these to their proper folders? Do I have to do it that way or will a Windows samba connection work?

Looks like 86GB. I can live with that. Is there a way to get those files out of the lost and found or do I have to replace them all?

I don't know where to enter that command. I do, however, notice a lost and found directory when I use the unraid file explorer on Disk 4. There are definitely some files in there, but not that many comparatively.

Except that they're not. Once the sync was completed, I rebooted the system, started in maintenance mode, ran a filesystem check/repair on Disk 4 (which failed again like last time this happened), restarted the array normally, and all the files are back now. I don't explain it because I'd agree that sync has nothing to do with missing folder contents (even though the folder itself is there). All I know is that this is twice now that this process has worked so I don't know what's going on. Everything seems to be working properly now. Go figure. Here's a diagnostic. Maybe you can figure it out. storage-diagnostics-20240212-1158.zip

Oh and thanks again for helping with this. You've been invaluable.

I figured people were busy so I just tried some research of my own while I was waiting. So far everything seems to be ok. I assigned the original Disk 4 and all seems to be running through parity-sync with no issues. I've got a similar circumstance to one I had earlier in this thread where one of my folders was empty while parity was rebuilding, but last time that sorted itself out once the sync was complete so until then, I'm not worried. This may be using a RAID controller, but it's functioning more as a SATA splitter than any actual RAID control. So far all seems good. I'll know more once the sync is complete. If that all works then I'll be looking to add Disk 1 to expand the array since Disk 4 now seems to be working properly. I see no errors or warnings. Here's a diagnostics in the meantime. Sync should finish in another 12 hours. 16TB parity drive. Oy vey. storage-diagnostics-20240211-1513.zip

I think I've managed to configure the new raid card. Once I rebooted after doing that, unraid can now see all the drives. I assigned them to the exact same Disk locations as before the new config and started the array. It's now doing a parity check. Let's hope to God that everything is ok after that.

Well since I didn't hear from anyone. I hit New Config. Now on the main screen everything is listed as unassigned and no disks are showing up at all. It's well and truly borked, isn't it?

It seems to me, what I need to do is Tools>New Config....Check parity is valid, start the array. Is that right? I think that will initiate a parity check, no? I just want to make sure this is the right thing to do before I do it.

For further info, I had a friend of mine suggest I reboot the array and look for a config tool for the new card. Maybe that's an option?

The post on the forum also said something about rebuilding the disks one at a time. Will that be possible when one was emulated to begin with?

The card I swapped is an HBA so maybe the old one wasn't. I honestly don't remember. I saw something on the forum about a new config, but that has me a bit nervous.

OK. So now I've swapped out the raid card and the cables. No when I fire up unraid, it says all my devices are missing. It's not recognizing any drive. Every slot says no device and doesn't give me any option to select one. Sigh.

So maybe while I'm replacing thing, I might as well replace the PSU too. I imagine the 16TB drives use more power than the 4TB, but I figured there's still enough power coming out of the thing. I did reseat the power connect6ions when I reseated all the drive cables. The problem for me is all this hardware is pretty old so it may be cascade failing. Oy vey. I'll start replacing stuff on a shotgun approach and hope that ONE of the things I replace, if not all, will allow me to rebuild a full array someday.

They're powered off a single standard PSU. None of the other drives have had any issues though so I would assume that if power was an issue, that all drives in a cage would fail. Additionally, Disk 1 and Disk 4 are in different cages, but those seem to be the only drives that are disconnecting.

Right now I'm at the point that although the contents are emulated, the files on Disk 4 are present. That would suggest to me that the parity, for most intents and purposes anyway, is functioning even if the emulated contents are incomplete. I can live with that. So it seems to me that my best step now is to replace the card and cables, physically replace Disk 4 with another drive and try to rebuild it. Does that sound reasonable?

It's been so long since I put this thing together, I'm not sure. I suppose I could. Right now I'm thinking just replace the card and cables. Then what? Try to rebuild Disk 4 onto itself again? Then if that works, new config and rebuild parity? Is that what I'm looking at?

All drives save the jump drive are connected through the card. It has two ports and two breakout cables connected to it totaling 8 drives.

I'm now tempted to swap the drive out and try to rebuild off the parity and just accept whatever is lost.

Well I've just shutdown, reseated Disk 4, and rebooted. Disk 4 still says contents emulated, but after attempting a filesystem check, it couldn't complete it and gave an error, but a few minutes later it says Disk 4 returned to normal utilization and all my files came back.

So what you're saying is I can't even try to repair the filesystem right now? Is there any possibility that the drives are responsible for the disconnect? I've already reseated everything and about the only thing left to do is replace cables and/or controller. That will take days and this thread will be lost in the meantime.

This is what it looks like after the parity rebuild. I then stopped the array and started it in maintenance mode per the instructions to check the filesystem.