Pool Device - Invalid Path?

[yyc321]

I have a pool device consisting of a single spinner.

 

The drive shows up on the main page.  Clicking the device name pulls up the drive properties etc.

 

However, the drive doesn't show up in midnight commander.  Clicking the view link on the main page results in "invalid path".

 

In the logs, you'll notice that the server pulled a drive for UDMA CRC errors - the cable has been replaced.  Just waiting to deal with this path issue before I fix the emulated drive.

 

 

 

 tower-diagnostics-20221004-1737.zip

Edited October 4, 2022 by yyc321
Added images.

[JorgeB]

Oct  4 17:13:18 Tower kernel: XFS (sdl1): Corruption warning: Metadata has LSN (-977856008:384760175) ahead of current LSN (15:2420592). Please unmount and run xfs_repair (>= v4.3) to resolve.

Check filesystem on that pool.

[yyc321]

Thanks!!

[xxbigfootxx]

I've suddenly got this on one of my data drives. What can I do to repair it? 

 

zeus-diagnostics-20231002-2046.zip

[JorgeB]

37 minutes ago, xxbigfootxx said:

What can I do to repair it? 

See link above, also should update to latest stable.

[xxbigfootxx]

9 hours ago, JorgeB said:

See link above, also should update to latest stable.

I updated to stable and as the array came online I saw the contents of the disk appear again. Now missing again.

 

That link just takes me to the home page, is this what I should go through? https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/#checking-and-fixing-drives-in-the-webgui

 

[xxbigfootxx]

@JorgeB So I started the array in maintenance and ran the XFS_REPAIR check and this is the output. 

 

 

It doesn't specify the next commands to run, but it does look like there were detected CRC errors? Which is odd that I wasn't alerted to any of them and the SMART checks didn't detect it? Should I run the check again without the -n to correct the errors?

[JorgeB]

Run it again without -n or nothing will be done.

 

 

[xxbigfootxx]

Thanks @JorgeB - it's all working again now.