Jump to content

Shares disappearing


Recommended Posts

Posted

I had my drive 1 fail and I replaced it and rebuilt it from parity. But then my shares disappear. If I reboot they come back... but when I turn on Docker the shares disappear again. I tried to delete the Docker image, but without the shares it says the Image and the app data path does not exist. 

Thank you,

John

tower-diagnostics-20240606-1711.zip

Posted

Looks like you need to run a check filesystem on disk1 as the syslog shows:

Jun  6 16:54:29 Tower kernel: XFS (md1p1): Corruption detected. Unmount and run xfs_repair

Such file system corruption can have the effect you describe until it is fixed.

 

It might also be a good idea to run a memtest in case the corruption was caused by RAM acting up.

Posted

Thank you itimpi, That did the trick.

How/where do you see "Jun 6 16:54:29 Tower kernel: XFS (md1p1): Corruption detected. Unmount and run xfs_repair"?

Just so I can fix it myself next time... I looked in the diagnostics zip syslog, but I do not see it.

Posted
47 minutes ago, johnzimm said:

Thank you itimpi, That did the trick.

How/where do you see "Jun 6 16:54:29 Tower kernel: XFS (md1p1): Corruption detected. Unmount and run xfs_repair"?

Just so I can fix it myself next time... I looked in the diagnostics zip syslog, but I do not see it.

It was present both in the syslog file and the syslog-previous file so you must have missed it.

  • 3 weeks later...
Posted

Last time disk one was corrupted I did the flowing:

 

-Replaced drive with new drive

-Used new cable

-Connected to different port

-MemTest86 passed

-Checked file system with -n, then -L, them no "-x"

 

But now after a week, the disk has the red x buy it again. And it says its emulated. It is always drive 1.

Anything else I should look at before randomly replacing hardware?

Thank you,

John

Unconfirmed 540723.crdownload

Posted

Disk was already disabled at boot, so we can't see what happened, next time save the diags before rebooting, also make sure you confirm the diags download, to avoid us having to rename the file.

Posted
15 hours ago, JorgeB said:

Disk was already disabled at boot, so we can't see what happened, next time save the diags before rebooting, also make sure you confirm the diags download, to avoid us having to rename the file.

OK, Thanks JorgeB

I checked the original drive with SpinRight and it looks fine. So I put it back in and parity is now rebuilding. If it happens again, I will get the diags before reboot, and rename them.

John

  • Like 1

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...