alexandru360 Posted April 3, 2021 Share Posted April 3, 2021 Hy guys unfortunately I rearranged my hdds in the server (new array - software) and for one hard-disk I get this: Apr 4 02:34:17 AlexHomeTower kernel: ata8: SATA max UDMA/133 abar m8192@0xfbe80000 port 0xfbe80180 irq 71 Apr 4 02:34:17 AlexHomeTower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 4 02:34:17 AlexHomeTower kernel: ata8.00: ATA-10: ST2000NM0008-2F3100, ZDS12462, SN02, max UDMA/133 Apr 4 02:34:17 AlexHomeTower kernel: ata8.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA Apr 4 02:34:17 AlexHomeTower kernel: ata8.00: configured for UDMA/133 Apr 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Apr 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] Write Protect is off Apr 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 4 02:34:17 AlexHomeTower kernel: sdb: sdb1 Apr 4 02:34:17 AlexHomeTower kernel: sd 8:0:0:0: [sdb] Attached SCSI disk Apr 4 02:36:33 AlexHomeTower emhttpd: ST2000NM0008-2F3100_ZDS12462 (sdb) 512 3907029168 Apr 4 02:36:33 AlexHomeTower emhttpd: read SMART /dev/sdb Apr 4 02:39:52 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:39:52 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:39:52 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:39:52 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:39:52 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:39:52 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:39:52 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:39:53 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:39:53 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:39:53 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:39:54 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:39:54 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:39:54 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:39:54 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:39:55 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:39:55 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:39:55 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:39:55 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:39:55 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:39:55 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:39:55 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:40:04 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:40:04 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:40:04 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:40:04 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:40:04 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:40:04 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:40:04 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:40:05 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:40:05 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:40:05 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:40:05 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:40:05 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:40:05 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:40:05 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:40:06 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:40:06 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:40:06 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:40:06 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:40:06 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:40:06 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:40:06 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Apr 4 02:40:07 AlexHomeTower unassigned.devices: Adding disk '/dev/sdb1'... Apr 4 02:40:07 AlexHomeTower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdb1' '/mnt/disks/ST2000NM0008-2F3100_ZDS12462' Apr 4 02:40:07 AlexHomeTower kernel: XFS (sdb1): Mounting V5 Filesystem Apr 4 02:40:07 AlexHomeTower kernel: XFS (sdb1): Corruption warning: Metadata has LSN (1:79595) ahead of current LSN (1:77215). Please unmount and run xfs_repair (>= v4.3) to resolve. Apr 4 02:40:07 AlexHomeTower kernel: XFS (sdb1): log mount/recovery failed: error -22 Apr 4 02:40:07 AlexHomeTower kernel: XFS (sdb1): log mount failed Apr 4 02:40:07 AlexHomeTower unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/ST2000NM0008-2F3100_ZDS12462: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Quote Link to comment
trurl Posted April 4, 2021 Share Posted April 4, 2021 1 hour ago, alexandru360 said: (new array - software) What do you mean by this? If possible before rebooting and preferably with the array started Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. Quote Link to comment
alexandru360 Posted April 4, 2021 Author Share Posted April 4, 2021 (edited) Quote (new array - software) --------> Tools -> New Config alexhometower-diagnostics-20210404-1000.zip xfs_repair -n /dev/md3 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... - 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 - 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 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... Maximum metadata LSN (1:79588) is ahead of log (1:77215). Would format log to cycle 4. No modify flag set, skipping filesystem flush and exiting. Edited April 4, 2021 by alexandru360 Quote Link to comment
trurl Posted April 4, 2021 Share Posted April 4, 2021 Ordinarily, SSDs are not recommended in the array. But in your case only parity disks are SSDs. I'm not sure how that plays out in the discussions we have had about SSDs in the array. I will ask @JorgeB to comment on that. 7 hours ago, alexandru360 said: xfs_repair -n /dev/md3 ... No modify flag set, skipping filesystem flush and exiting. Disk3 unmountable as you realized. You will have to remove -n to get it to actually fix the filesystem. Also use -L if it asks for it. Unrelated, but why do you have 100G allocated to docker.img? Have you had problems filling it? 20G is usually more than enough, and making it larger won't fix filling it, it will only make it take longer to fill. Also, your system share has files on the array, in fact, it is set to move files to the array. You want appdata, domains, and system shares to be all on cache and set to stay on cache. Your dockers / VMs always have open files, and this will prevent array disks from spinning down. Also their performance will be impacted by slower parity. Even having SSDs as parity won't completely eliminate that since the data disks still have more work to do updating parity. Quote Link to comment
alexandru360 Posted April 4, 2021 Author Share Posted April 4, 2021 xfs_repair -v /dev/md3 Phase 1 - find and verify superblock... - block cache size set to 1508680 entries Phase 2 - using internal log - zero log... zero_log: head block 77215 tail block 77209 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. It is that corruption I fear but I guess it is much better than not being able to mount the HDD. I will wait a little for your friend's input and then do the -L thing ... Quote Ordinarily, SSDs are not recommended in the array. But in your case only parity disks are SSDs. I'm not sure how that plays out in the discussions we have had about SSDs in the array. Quote Link to comment
itimpi Posted April 4, 2021 Share Posted April 4, 2021 The -L option virtually never causes corruption, and even if it does it will only be to the last file(s) written to the disk. That warning message reads a lot more ominously than turns out to be the case in practice. Quote Link to comment
alexandru360 Posted April 4, 2021 Author Share Posted April 4, 2021 5 minutes ago, itimpi said: The -L option virtually never causes corruption, and even if it does it will only be to the last file(s) written to the disk. That warning message reads a lot more ominously than turns out to be the case in practice. Ok ... here goes ... fingers crossed ... Quote Link to comment
alexandru360 Posted April 4, 2021 Author Share Posted April 4, 2021 Well ... it worked I got my HDD back ... Thank you all for the assistance Quote Link to comment
trurl Posted April 5, 2021 Share Posted April 5, 2021 Still recommend you do something about those other things I mentioned. Quote Link to comment
JorgeB Posted April 5, 2021 Share Posted April 5, 2021 19 hours ago, trurl said: I'm not sure how that plays out in the discussions we have had about SSDs in the array. I will ask @JorgeB to comment on that. It's fine with the usual warning that since they can't be trimmed write performance might degrade over time. Quote Link to comment
Recommended Posts
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.