November 9, 20223 yr I just upgraded unRAID to 6.11.3 and I get this error after reboot: I seems to connect fine but says my FS is corrupt? I get this when starting array in "Log disk info": Nov 9 10:23:40 Tower kernel: sd 1:0:5:0: [sdm] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) Nov 9 10:23:40 Tower kernel: sd 1:0:5:0: [sdm] 4096-byte physical blocks Nov 9 10:23:40 Tower kernel: sd 1:0:5:0: [sdm] Write Protect is off Nov 9 10:23:40 Tower kernel: sd 1:0:5:0: [sdm] Mode Sense: 9b 00 10 08 Nov 9 10:23:40 Tower kernel: sd 1:0:5:0: [sdm] Write cache: enabled, read cache: enabled, supports DPO and FUA Nov 9 10:23:40 Tower kernel: sdm: sdm1 Nov 9 10:23:40 Tower kernel: sd 1:0:5:0: [sdm] Attached SCSI disk Nov 9 10:24:11 Tower emhttpd: ST16000NM001G-2KK103_WL206EZD (sdm) 512 31251759104 Nov 9 10:24:11 Tower kernel: mdcmd (9): import 8 sdm 64 15625879500 0 ST16000NM001G-2KK103_WL206EZD Nov 9 10:24:11 Tower kernel: md: import disk8: (sdm) ST16000NM001G-2KK103_WL206EZD size: 15625879500 Nov 9 10:24:11 Tower emhttpd: read SMART /dev/sdm Nov 9 10:28:12 Tower s3_sleep: excluded disks=sda sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl sdm sdn sdo Nov 9 10:30:50 Tower emhttpd: read SMART /dev/sdm Nov 9 10:30:51 Tower s3_sleep: excluded disks=sda sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl sdm sdn sdo Nov 9 10:34:22 Tower s3_sleep: excluded disks=sda sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl sdm sdn sdo So I can see on the first line that the data is still there. What can I do? I tried new cables and power connectors. tower-diagnostics-20221109-1033.zip
November 10, 20223 yr Author On 11/9/2022 at 11:13 AM, JorgeB said: Check filesystem on the emulated disk 8 log.txtRan the command for 20 hours: xfs_repair /dev/sdm Finally it said: "Sorry, could not find valid secondary superblock" Secondly, this just fails immediatly: xfs_repair -v /dev/md8 Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error Edited November 10, 20223 yr by mrbusiness
November 10, 20223 yr Community Expert 24 minutes ago, mrbusiness said: xfs_repair /dev/sdm That's not how you check filesystem on an array disk, link above has the instructions. 25 minutes ago, mrbusiness said: xfs_repair -v /dev/md8 That's more concerning, reboot to clear the log, run that command again after starting the array in maintenance mode and post new diags right after.
November 10, 20223 yr Author 1 hour ago, JorgeB said: That's not how you check filesystem on an array disk, link above has the instructions. That's more concerning, reboot to clear the log, run that command again after starting the array in maintenance mode and post new diags right after. I just did as you said and the same errors occcur: Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error tower-diagnostics-20221110-1517.zip log.zip
November 10, 20223 yr Author @JorgeB I usesd UFS Explorer now to see if it might work. I am not missing any crucial data, so I guess I will just reformat the disk now. Thanks for the help.
November 10, 20223 yr Community Expert 28 minutes ago, mrbusiness said: and the same errors occcur: That was expected, just wanted to clear the log, you don't have parity assigned so the disk cannot be emulated, disk looks healthy so just go to Tools and do a new config, keep all assignments, then start array, disk should now mount, if it doesn't post new diags.
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.