May 3, 20233 yr Hello. I have 3 disk in my array. disk 2 have bad file system ( it was xfs). I can it repair ?
May 3, 20233 yr Author I don't understand. How it can help me ? I don't have parity drive. It just array with 3 disk. I need repair my file system and data on disk 2. I have 4 VM on it disk. In that thread need format disk. I don't want format and lose my data in 4 VM
May 3, 20233 yr Community Expert Without parity you cannot do the usual solution, which is to rebuild to recreate the correct partition layout, see if the device mounts with UD.
May 3, 20233 yr Community Expert 1 hour ago, Exlife said: I don't understand. How it can help me ? I don't have parity drive. It just array with 3 disk. I need repair my file system and data on disk 2. I have 4 VM on it disk. In that thread need format disk. I don't want format and lose my data in 4 VM I would suggest that you click on the drive and explicitly set the format to be xfs. This should then allow you to a file system repair via the GUI.
May 3, 20233 yr Community Expert 1 hour ago, Yankton said: Some good info to go through here. Not sure why you posted in this thread as your issue seems to have nothing to do with the thread title. If you have put the new disk into a new slot on the array, then after starting the array it will need formatting. If your problem is anything else you should start a new thread about it.
May 3, 20233 yr Author 1 hour ago, JorgeB said: Without parity you cannot do the usual solution, which is to rebuild to recreate the correct partition layout, see if the device mounts with UD. I can only format 30 minutes ago, itimpi said: I would suggest that you click on the drive and explicitly set the format to be xfs. This should then allow you to a file system repair via the GUI. It still Unsupported partition layout 27 minutes ago, itimpi said: Not sure why you posted in this thread as your issue seems to have nothing to do with the thread title. If you have put the new disk into a new slot on the array, then after starting the array it will need formatting. If your problem is anything else you should start a new thread about it. Maby i bad can tell on English. I have array wothout parity. It just disk1 disk2 disk3. I don't add new disk2. My disk2 lose my file system after VM on it disk froze(stuck,halt). I wanna back 4 VM xfs_repair status: Spoiler Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_icount 1920, counted 1856 sb_ifree 533, counted 478 sb_fdblocks 59246843, counted 71799196 - 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 out-of-order bmap key (file offset) in inode 537359427, data fork, fsbno 79635562 bad data fork in inode 537359427 would have cleared inode 537359427 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 0 - agno = 2 entry "macos_disk.img" in shortform directory 537359424 references free inode 537359427 would have junked entry "macos_disk.img" in directory inode 537359424 out-of-order bmap key (file offset) in inode 537359427, data fork, fsbno 79635562 would have cleared inode 537359427 Missing reference count record for (2/12224889) len 48 count 2 xfs_repair: rmap.c:1267: fix_inode_reflink_flags: Assertion `(irec->ino_is_rl & irec->ir_free) == 0' failed. Missing reference count record for (2/12391962) len 112 count 2 Missing reference count record for (2/12476730) len 256 count 2 Missing reference count record for (2/12477210) len 5200 count 2 Missing reference count record for (2/12483690) len 896 count 2 Missing reference count record for (2/12485834) len 40864 count 2 Missing reference count record for (2/12526699) len 2976 count 2 xfs_repair status: It can see file with one of my VM. I think it good Edited May 3, 20233 yr by Exlife
May 3, 20233 yr Community Expert 5 minutes ago, Exlife said: I can only format 31 minutes ago, itimpi said: I would suggest that you click on the drive and explicitly set the format to be xfs. This should then allow you to a file system repair via the GUI. It still Unsupported partition layout If you change the format to explicitly be xfs and then reboot, when you click on the drive you should have the check filesystem option. This is the way to clear the unmountable status.
May 3, 20233 yr Community Expert 9 minutes ago, Exlife said: I can only format That means no valid fs is being detected, post output of blkid and fdisk -l /dev/nvme0n1
May 3, 20233 yr Author 22 minutes ago, JorgeB said: That means no valid fs is being detected, post output of blkid and fdisk -l /dev/nvme0n1 Spoiler root@Tower2:~# blkid /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272B-4CE1" BLOCK_SIZE="512" TYPE="vfat" /dev/loop1: TYPE="squashfs" /dev/sdb1: UUID="836a2078-1eb6-4765-8e54-bddabf3be7f5" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="e33d5dab-01" /dev/md2: UUID="a8c2b643-0e7d-4dc7-ab94-b619d1e032d2" BLOCK_SIZE="512" TYPE="xfs" /dev/loop0: TYPE="squashfs" /dev/sdc1: UUID="da98a68e-1703-400c-a7f9-6697ac36083a" BLOCK_SIZE="512" TYPE="xfs" /dev/md3: UUID="836a2078-1eb6-4765-8e54-bddabf3be7f5" BLOCK_SIZE="512" TYPE="xfs" /dev/md1: UUID="da98a68e-1703-400c-a7f9-6697ac36083a" BLOCK_SIZE="512" TYPE="xfs" root@Tower2:~# fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: ADATA SX6000LNP Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@Tower2:~# 25 minutes ago, itimpi said: If you change the format to explicitly be xfs and then reboot, when you click on the drive you should have the check filesystem option. This is the way to clear the unmountable status. Ok. now i read more for it utility. I try keys -n and -nv i get only it Spoiler Quote Phase 1 - find and verify superblock... - block cache size set to 2301864 entries Phase 2 - using internal log - zero log... zero_log: head block 397311 tail block 397061 ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_icount 1920, counted 1856 sb_ifree 533, counted 478 sb_fdblocks 59246843, counted 71799196 - 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 out-of-order bmap key (file offset) in inode 537359427, data fork, fsbno 79635562 bad data fork in inode 537359427 would have cleared inode 537359427 - 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 = 2 - agno = 3 - agno = 1 entry "macos_disk.img" in shortform directory 537359424 references free inode 537359427 would have junked entry "macos_disk.img" in directory inode 537359424 out-of-order bmap key (file offset) in inode 537359427, data fork, fsbno 79635562 would have cleared inode 537359427 xfs_repair: rmap.c:1267: fix_inode_reflink_flags: Assertion `(irec->ino_is_rl & irec->ir_free) == 0' failed. Missing reference count record for (2/12224889) len 48 count 2 Missing reference count record for (2/12391962) len 112 count 2 Missing reference count record for (2/12476730) len 256 count 2 Missing reference count record for (2/12477210) len 5200 count 2 Missing reference count record for (2/12483690) len 896 count 2 Missing reference count record for (2/12485834) len 40864 count 2 Missing reference count record for (2/12526699) len 2976 count 2 Edited May 3, 20233 yr by Exlife
May 3, 20233 yr Community Expert Without parity Unraid cannot recover it, you can use something like testdisk to see if it can fix it.
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.