February 12Feb 12 Author 1 hour ago, JorgeB said:Try now to check filesystem on both unmountable disks.Both disks are tied up in this, probably more promising as last time they failed quickly
February 12Feb 12 Author 6 minutes ago, Kosturi said:Both disks are tied up in this, probably more promising as last time they failed quicklySpoke too soon. Ill attach the diagnostics after that check tootower-diagnostics-20260212-2258.zip
February 12Feb 12 Community Expert Click the Fix button. I recommend doing one at a time, since they are being emulated.
February 12Feb 12 Author 1 minute ago, JorgeB said:Click the Fix button. I recommend doing one at a time, since they are being emulated.okay doing it on disk 3 now
February 12Feb 12 Author 20 minutes ago, JorgeB said:Click the Fix button. I recommend doing one at a time, since they are being emulated.Failed and caused Disk 4 to spin down. tower-diagnostics-20260212-2336.zip
February 12Feb 12 Community Expert 6 hours ago, Kosturi said:stopped the rebuild it triggered on the array startingAnother reason I wanted autostart disabled, so you could unassign those disks before starting the array. Then repair the filesystems on the emulated disks before rebuilding. That would have let us also consider the physical disk contents in case they were better than contents of emulated disks.Probably too far gone already though since you had been rebuilding unmountable disks since the beginning of your troubles.
February 12Feb 12 Community Expert You are still having issues with disk4; you need to fix that first. All disks need to be involved in fixing the emulated disks.
February 12Feb 12 Community Expert 1 hour ago, JorgeB said:till having issues with disk4Just like beforeOn 2/11/2026 at 9:56 AM, trurl said:SMART report for sdn (formerly disk4) looks OK, and syslog seems to indicate a problem communicating with the disk
February 13Feb 13 Author 13 hours ago, JorgeB said:You are still having issues with disk4; you need to fix that first. All disks need to be involved in fixing the emulated disks.Okay so I tried stopping the array, removing disk 4 from the array but it won't let me start the array now.Even after a reboot.
February 13Feb 13 Community Expert Of course. You already have 2 invalid disks still needing to be rebuilt, which is as many as dual parity can allow.Nobody said you should remove disk 4. My earlier idea was to remove the 2 invalid disks so you wouldn't be rebuilding them. Not sure there is any point to that idea though since you have already been rebuilding unmountable filesystems to those disks.But it also won't hurt anything to remove them or at least set them to "no device". That is allowed since they are already invalid and are being emulated.But disk4 must be read accurately in order to accurately emulate those disks so they can be rebuilt.And disk4 is not being read. You need to fix that before you can make any progress.
February 13Feb 13 Author Okay that makes sense. Sorry I'm fairly new to all of this. So just to be clear so I don't make anymore mistakes.I should remove the emulated disks, keep disk 4 and then start in maintenance mode and try a check disk on disk 4?
February 13Feb 13 Author xfs_repair status:Phase 1 - find and verify superblock...Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunkPhase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - process newly discovered inodes...Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 11 - agno = 12 - agno = 5 - agno = 7 - agno = 8 - agno = 6 - agno = 1 - agno = 10 - agno = 9 - agno = 14 - agno = 13 - agno = 2 - agno = 4No modify flag set, skipping phase 5Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ...Phase 7 - verify link counts...No modify flag set, skipping filesystem flush and exiting.
February 13Feb 13 Author 2 minutes ago, Kosturi said:xfs_repair status:Phase 1 - find and verify superblock...Phase 2 - using internal log- zero log...- scan filesystem freespace and inode maps...- found root inode chunkPhase 3 - for each AG...- scan (but don't clear) agi unlinked lists...- process known inodes and perform inode discovery...- agno = 0- agno = 1- agno = 2- agno = 3- agno = 4- agno = 5- agno = 6- agno = 7- agno = 8- agno = 9- agno = 10- agno = 11- agno = 12- agno = 13- agno = 14- process newly discovered inodes...Phase 4 - check for duplicate blocks...- setting up duplicate extent list...- check for inodes claiming duplicate blocks...- agno = 0- agno = 3- agno = 11- agno = 12- agno = 5- agno = 7- agno = 8- agno = 6- agno = 1- agno = 10- agno = 9- agno = 14- agno = 13- agno = 2- agno = 4No modify flag set, skipping phase 5Phase 6 - check inode connectivity...- traversing filesystem ...- traversal finished ...- moving disconnected inodes to lost+found ...Phase 7 - verify link counts...No modify flag set, skipping filesystem flush and exiting. tower-diagnostics-20260213-1552.zip
February 13Feb 13 Community Expert Since SMART looks fine for disk4, first thing to do is to replace its cables.
February 13Feb 13 Author 2 hours ago, JorgeB said:Since SMART looks fine for disk4, first thing to do is to replace its cables.Okay, I replaced that group of HDD's sata cables with the spare one I had. I then re-seated all of the HDD's. rebooted it, and it looks the same now.
February 13Feb 13 Community Expert What do you mean by looks the same? Did you get more errors on disk 4?
February 13Feb 13 Author Just now, JorgeB said:What do you mean by looks the same? Did you get more errors on disk 4?No, the same as before, No SMART errors, nothing flagging. The 2 emulated drives are still disabled
February 13Feb 13 Author Just now, Kosturi said:No, the same as before, No SMART errors, nothing flagging. The 2 emulated drives are still disabledxfs_repair status:Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 5 - agno = 12 - agno = 1 - agno = 6 - agno = 9 - agno = 8 - agno = 7 - agno = 3 - agno = 11 - agno = 10 - agno = 13 - agno = 14 - agno = 4 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. No file system corruption detected.
February 13Feb 13 Community Expert 31 minutes ago, Kosturi said:The 2 emulated drives are still disabledThis is expected.Post new diags after array start.
February 13Feb 13 Author 14 minutes ago, JorgeB said:This is expected.Post new diags after array start. tower-diagnostics-20260213-2235.zip
February 13Feb 13 Community Expert Array is started in maintenance mode, but assuming the emulated disks still don't mount in normal mode, try checking the file system again and see if you still get errors on disk4.
February 13Feb 13 Author 2 minutes ago, JorgeB said:Array is started in maintenance mode, but assuming the emulated disks still don't mount in normal mode, try checking the file system again and see if you still get errors on disk4.xfs_repair status:Phase 1 - find and verify superblock...Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunkPhase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - process newly discovered inodes...Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 1 - agno = 4 - agno = 5 - agno = 6 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 14 - agno = 12 - agno = 7 - agno = 13No modify flag set, skipping phase 5Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ...Phase 7 - verify link counts...No modify flag set, skipping filesystem flush and exiting.
February 13Feb 13 Author 3 minutes ago, JorgeB said:Array is started in maintenance mode, but assuming the emulated disks still don't mount in normal mode, try checking the file system again and see if you still get errors on disk4.I've been starting it in maintenance mode because it won't let me use the check file system tool in normal mode. I can do a normal mode start and get the diagnostics for you from that
February 13Feb 13 Author Diagnostics with array started in normal mode tower-diagnostics-20260213-2323.zip
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.