Unraid 6.8.3 Unmountable disk.

[xrqp]

For the unmountable disk, I ran the "Checking a File System"  with -n option, and copied the report into the attached docx file.  If I pasted it here, it is so many pages it seems to create problems.

 

unmountable hard drive, check file system report .docx

 

"Repairing a File System" instructions say:

Add any additional parameters to the Options field required that are suggested from the check phase. If not sure then ask in the forum.

 

I am not sure at all what the report means, so asking here what parameters I should set?   Thanks.

[JorgeB]

That looks like a very corrupt filesystem, but basically you can only attempt to repair it without -n, is that an emulated disk or actual disk?

[xrqp]

I think it is an actual disk.  How do you tell if it is emulated or actual?  What parameters I should set for the repair, other than remove the -n?

[JorgeB]

3 minutes ago, xrqp said:

How do you tell if it is emulated or actual? 

Actual disk will have a green ball on main page, emulated disk yellow or red.

 

3 minutes ago, xrqp said:

What parameters I should set for the repair, other than remove the -n?

You can use -v for increased verbosity, though it doesn't make much difference.

[xrqp]

it has the green ball if I spin it up, so it is actual disk.   Running the check fix now with no options (no parameters) for about 10 minutes and ongoing. 

The help said when the check fix is running to "refresh" the monitor. I guess they are referring to the internet browser program.

 

The help said use -L option if it tells you to.  Mine did not tell me that yet.  My disk is xfs.  What does -L do?

[JorgeB]

7 hours ago, xrqp said:

What does -L do?

Clears the LOG if needed.

[xrqp]

I started the repair Feb. 18 at 5pm, now Feb 22 1am it is still repairing the 8TB drive.  Is it supposed to take this long?

I checked the "reads" periodically.  (Help says "reads" is a count of I/O requests sent to the device I/O drivers.)

Reads   Date time

113k      Feb 18

126k     Feb 18  11:40pm

421k     Feb 19  1pm

233k    Feb 21  1pm  (why did reads go down?)

253k    Feb 22  1am

 

why did reads go down on Feb 21.

how long does it take to repair 8TB drive?

 

Here is what my screen says at Check Filesystem Status,  xfs_repair status:

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
Log inconsistent or not a log (last==0, first!=1)
empty log check failed
zero_log: cannot find log head/tail (xlog_find_tail=22)
ERROR: The log head and/or tail cannot be discovered. Attempt to mount the
filesystem to replay the log or use the -L option to destroy the log and
attempt a repair.

 

Should I stop the repair, and start it again with -L option?

Edited February 22, 2021 by xrqp

[itimpi]

4 minutes ago, xrqp said:

I started the repair Feb. 18 at 5pm, now Feb 22 1am it is still repairing the 8TB drive.  Is it supposed to take this long?

I checked the "reads" periodically.  (Help says "reads" is a count of I/O requests sent to the device I/O drivers.)

Reads

 

Repair time is normally measurable in minutes so it seems something is going wrong  

 

You are likely to get better informed feedback if you attach your systems diagnostics zip file (obtained via Tools->Diagnostics) to your NEXT post.

[JorgeB]

1 hour ago, xrqp said:

Should I stop the repair, and start it again with -L option?

That repair is already stopped, you need to use -L.

[xrqp]

11 hours ago, JorgeB said:

That repair is already stopped, you need to use -L.

I thought the reads increasing was the only way to know it is running (built in help).   Last night I found spaceinvaders youtube on this called How to Fix XFS File System Corruption on an Unraid Server.  Now I did repair with -L.  This time I watched it closer.  I think it went well.  Thanks for your replies.

 

Edited February 22, 2021 by xrqp