Disk showing "Unmountable: Wrong or no file system", suggestions on how to proceed

[dalmaar]

Having an issue with one of my unraid boxes. This unraid box has been running without
issue for years, I admit it has been so stable I am rusty on procedures
when something does go wrong.

 

I effort to prepare to upgrade, I was cleaning up files getting ready
for parity check, etc involved transferring files to/from Disk 6.
It started spewing errors. Google and this forum suggested they were are
pointing to a possible sata cable issue, clean shutdown, swap the cable.

Bring it back up and that disk is in emulation mode (yellow icon), but
disk share not showing up, (maybe a disk issue at this point?) I could not
get the array up and had to do a SYNC (or something like that, I did
NOT format disk).

 

~16 hrs later it finished and during that time I saw a few notifications pop
up the GUI about some smart parameters reset to zero. after it was done
without errors the disk is now in green but has status
"Unmountable: Wrong or no file system". I can see all the disk shares but not disk6.

 

Jul 29 12:17:58 Tower2 kernel: mdcmd (38): check correct
Jul 29 12:17:58 Tower2 kernel: md: recovery thread: recon D6 ...
Jul 30 03:40:01 Tower2  crond[1066]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null
Jul 30 04:39:07 Tower2 kernel: md: sync done. time=58869sec
Jul 30 04:39:07 Tower2 kernel: md: recovery thread: exit status: 0

Included the diagnostics zip file, but saw these in the logfile:

Jul 29 11:59:03 Tower2 kernel: XFS (md6): Corruption warning: Metadata has LSN (1:89786) ahead of current LSN (1:89698).
Please unmount and run xfs_repair (>= v4.3) to resolve.
Jul 29 11:59:03 Tower2 kernel: XFS (md6): log mount/recovery failed: error -22
Jul 29 11:59:03 Tower2 kernel: XFS (md6): log mount failed
Jul 29 11:59:03 Tower2 root: mount: /mnt/disk6: wrong fs type, bad option, bad superblock on /dev/md6,
missing codepage or helper program, or other error.
Jul 29 11:59:03 Tower2 root:        dmesg(1) may have more information after failed mount system call.
Jul 29 11:59:03 Tower2  emhttpd: shcmd (104): exit status: 32
Jul 29 11:59:03 Tower2  emhttpd: /mnt/disk6 mount error: Wrong or no file system
Jul 29 11:59:03 Tower2  emhttpd: shcmd (105): umount /mnt/disk6
Jul 29 11:59:03 Tower2 root: umount: /mnt/disk6: not mounted.

 

At this point I am unclear as what to do next, unfamiliar with the xfs_repair tool, or
the process to get it started. I was hoping to get it to emulation mode until replacement
drive arrives.

 

At this point I am not doing anything with server, no file transfers or reboot/shutdowns. \
Staying powered up in this state, Any help appreciated.

tower2-diagnostics-20230730-0604.zip

[itimpi]

Handling of unmountable drives is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

[dalmaar]

Update...

 

Thanks for the pointer, I never clicked that manual link before.  🙄

Unfortunately I was called out of town, will give those procedures a try when I get back.

 

[dalmaar]

I finally had a chance to try the procedures and It has worked perfectly, no data loss (other than the file

I was originally writing, but I was doing a copy so I still have the file).

 

I think this was all due to a faulty SATA cable, at least so far no errors. Will be keeping a close

eye on this drive/

 

thanks for the help