February 27, 20251 yr Author 17 minutes ago, trurl said: Not sure I follow you there. sdb was parity in those last diagnostics, and parity has no format. Sorry for the confusion. I meant the former parity sdb... Currently sdc. Is there any way I can fully cancel the rebuild, and lose this disk, format it and add into the array? I've backed up most of the files so should be ok. Thanks!
February 27, 20251 yr Community Expert Let's try this. Unassign disk1, start the array, and post new diagnostics
February 27, 20251 yr Author 15 hours ago, trurl said: Let's try this. Unassign disk1, start the array, and post new diagnostics Disk 1 unassigned, please see attached diagnostics. Thanks! Edited February 28, 20251 yr by Zzzen
February 27, 20251 yr Community Expert 1 hour ago, trurl said: start the array, and post new diagnostics
February 27, 20251 yr Community Expert syslog still has lots of errors from sdg. Shutdown, remove that old disk. Reboot, start the array with nothing assigned as disk1. Post new diagnostics.
February 27, 20251 yr Author 14 hours ago, trurl said: syslog still has lots of errors from sdg. Shutdown, remove that old disk. Reboot, start the array with nothing assigned as disk1. Post new diagnostics. Rebooted without the failed old disk, nothing assigned, diagnostics attached. Now sdd is showing as unmountable... Edited February 28, 20251 yr by Zzzen
February 27, 20251 yr Community Expert 10 minutes ago, Zzzen said: Now sdd is showing as unmountable... Nothing we have done should have any effect on disk2. I'm beginning to wonder if you have some other problem. Have you done memtest recently?
February 27, 20251 yr Author 7 minutes ago, trurl said: Nothing we have done should have any effect on disk2. I'm beginning to wonder if you have some other problem. Have you done memtest recently? So sad and strange. And no sir, no memtest done recently.
February 27, 20251 yr Author 11 minutes ago, trurl said: memtest is on the boot menu Is the live memtest plugin sufficient? Thanks!
February 27, 20251 yr Author 1 minute ago, trurl said: I wouldn't count on it. Understood, let me find a monitor with vga first
February 27, 20251 yr Community Expert 25 minutes ago, Zzzen said: Is the live memtest plugin sufficient? Thanks! It is easier to run but not as thorough. You could try the plugin as first try as if it gives an error you have a problem but even if it passes you probably still want to try the one from the boot menu.
March 11, 20251 yr Author Update I've managed to rebuild and repair the whole system after several times of rebooting, rebuilding and formatting and parity check. I now believe the problem might be caused by hardware issue as every time I opened up the machine, something wrong popped up. I gave it 3 days for the whole data rebuild, the rebuild speed changed dramatically, but it completed at last, and I formatted the unmountable disk, thus lost all files from the original disk 1(toasted). then the disk 2 showed up as unmountable, but a filesystem fix then solved it. After rebuilding and checking and fixing corruptions the system shows all green for now. Now I see a 490G lost+found folder showed up located in disk2, i failed to go into the folder. Wondering if you may point me the way to restore whatever is in the lost+found folder? Also latest diagnostics attached, would you be so kind to check if everything is alright now? Any potential risks? Also I haven't done memtest yet, I know I shall do it sometime. Thanks in advance! Edited March 12, 20251 yr by Zzzen
March 11, 20251 yr Community Expert 1 minute ago, Zzzen said: Wondering if you may point me the way to restore whatever is in the lost+found folder? No simple answer to that unless you have backups. Typically what happens is repair can't figure out what folder a file belongs in, and/or can't figure out the name of a file or folder. The linux 'file' command might be able to tell you what kind of data is in a particular file so you can try to open it with an appropriate application to see what it is.
March 11, 20251 yr Community Expert Latest diagnostics shows constant problems communicating with disk2, and some with disk3 also. 10 minutes ago, Zzzen said: every time I opened up the machine, something wrong popped up. Disturbing disk connections is the most common reason for problems. Each disk plug must sit firmly and squarely on the connector (both ends of cable), with no tension in the cable. Don't bundle data cables to make things "neat". Similar for power connections. Ideally no more than 4 disks per PSU cable. Any power splitters? Those connections need to be considered also. Molex-SATA splitters are more reliable than SATA-SATA splitters.
March 12, 20251 yr Author 4 hours ago, trurl said: No simple answer to that unless you have backups. Typically what happens is repair can't figure out what folder a file belongs in, and/or can't figure out the name of a file or folder. The linux 'file' command might be able to tell you what kind of data is in a particular file so you can try to open it with an appropriate application to see what it is. I can access the folder through the specific disk, but not from the share folder which says invalid path. Is the folder created in the disk where the files originally located? If so I might know what they are and how to deal with them, millions of folders lol 4 hours ago, trurl said: Latest diagnostics shows constant problems communicating with disk2, and some with disk3 also. Disturbing disk connections is the most common reason for problems. Each disk plug must sit firmly and squarely on the connector (both ends of cable), with no tension in the cable. Don't bundle data cables to make things "neat". Similar for power connections. Ideally no more than 4 disks per PSU cable. Any power splitters? Those connections need to be considered also. Molex-SATA splitters are more reliable than SATA-SATA splitters. Thanks for the reminders, I'll see to the connections after the parity check. Thanks for the support!
March 12, 20251 yr Community Expert 14 minutes ago, Zzzen said: I can access the folder through the specific disk, but not from the share folder which says invalid path. Is the folder created in the disk where the files originally located? Repair put lost+found on the same disk you were repairing. It doesn't even know about other disks. User shares are simply the combined top level folders on disks and pools. Repair created a top level folder named lost+found, so that is why you have a lost+found user share, and it is only on the repaired disk (unless you had also repaired other disks). How are you trying to access the share that causes it to say invalid path?
March 12, 20251 yr Community Expert It is a good idea to run Tools->New Permissions on the lost+found share if you want to be able to access it via the network.
March 12, 20251 yr Community Expert 5 minutes ago, itimpi said: It is a good idea to run Tools->New Permissions on the lost+found share if you want to be able to access it via the network. You probably also have to go to the lost+found share settings and enable sharing in SMB
March 12, 20251 yr Community Expert 17 hours ago, Zzzen said: I'll see to the connections after the parity check. Sorry I missed this before. Parity check pointless when array disks are having connection problems. Not clear why you were doing parity check anyway. Parity check can't help with any data disk. Now I'm worried that you were doing a correcting parity check. I typically delete any diagnostics I download every day, so I don't have any of yours now.
March 29, 20251 yr Author On 3/13/2025 at 2:48 AM, trurl said: Sorry I missed this before. Parity check pointless when array disks are having connection problems. Not clear why you were doing parity check anyway. Parity check can't help with any data disk. Now I'm worried that you were doing a correcting parity check. I typically delete any diagnostics I download every day, so I don't have any of yours now. Hi, you were right, it was a correcting parity check. And I've got rid of all power cable splitters, and all runs well and it feels solid with stable power delivery. I've lost many files but mostly media files, nothing too serious. I thought the problem was solved so I deleted the diagnostics And I'm grateful for all the patience and help all along. Thank you! And community!
March 30, 20251 yr Community Expert 21 hours ago, Zzzen said: I've got rid of all power cable splitters, and all runs well and it feels solid with stable power delivery. Have you successfully run a parity check that completes with exactly zero parity sync errors?
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.