April 13, 20206 yr Author Linux 4.19.107-Unraid. Last login: Mon Apr 13 19:47:06 +0400 2020 on /dev/pts/0. root@Monstruo:~# xfs_repair -vL /dev/sdj1 Phase 1 - find and verify superblock... - block cache size set to 735904 entries Phase 2 - using internal log - zero log... Log inconsistent or not a log (last==0, first!=1) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=22) - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:126) is ahead of log (1:2). Format log to cycle 4. XFS_REPAIR Summary Mon Apr 13 19:48:25 2020 Phase Start End Duration Phase 1: 04/13 19:47:37 04/13 19:47:37 Phase 2: 04/13 19:47:37 04/13 19:47:53 16 seconds Phase 3: 04/13 19:47:53 04/13 19:47:53 Phase 4: 04/13 19:47:53 04/13 19:47:53 Phase 5: 04/13 19:47:53 04/13 19:47:53 Phase 6: 04/13 19:47:53 04/13 19:47:53 Phase 7: 04/13 19:47:53 04/13 19:47:53 Total run time: 16 seconds done root@Monstruo:~#
April 13, 20206 yr Community Expert Just now, gideva said: Was able to mount but there is NOTHING inside.... I already suspected that, since it had the same UUID has the emulated disk, someone/something deleted/formatted all data on that disk before.
April 17, 20206 yr Author Hi there... Just moved all data from the failing disks.... Before I will do a total disaster while proceeding with the New Config.... I reorder all the disks (I did not touch or moved the Parity that is still were is supposed to be) and now I have to pick one of the options but I do not want to screw everything... What shall I choose? I am sorry for the stupid question but I want to be sure
April 17, 20206 yr Community Expert Not understating the question, see if this helps: you can do a new config, keep all assignments, then unassign the disks you want to remove, you can take the opportunity to re-order the remaining data devices, then start array to begin parity sync.
April 17, 20206 yr Author Yes this is what I want to do... But actually I do not know if I am doing correctly... What I am doing is: 1) Stop the array 2) go to Tools and New Config 3) Preserve current assignments: All 4) Go to main (all disks are now with a blue square as they are considered as New Devices) and start Parity Sync Sorry but I am scared to loose everything....
April 17, 20206 yr Community Expert You need a step 3.5 where you Unassign any disks that you no longer want to be in the array before starting the array to commit the revised drive list and initiate a parity sync using the remaining disks.
Archived
This topic is now archived and is closed to further replies.