New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessing APM causes HDD to not mount #242

Open
vtalikka opened this Issue Dec 20, 2018 · 8 comments

Comments

Projects
None yet
3 participants
@vtalikka
Copy link

vtalikka commented Dec 20, 2018

When I change the HDD's APM settings the following happens:

  • the HDD does not mount anymore after reboot
  • I can mount the HDD manually but the mount point is different
  • rebooting takes a very long time
  • monit sends an alert: "filesystem flags changed to 0x1008" (the flags are sometimes different)

I did a fresh install with the same hardware but without changing APM settings and everything works fine. Reboot takes about a minute and the HDD mounts automatically, also no monit alerts.

Symptoms seem almost exactly the same as described here: https://forum.openmediavault.org/index.php/Thread/24288-Odroid-HC2-8TB-WD-red-too-big/

I'm using OMV 4.14.69 with ODROID-HC2. HDD is WD Red 4TB SATA.

@vtalikka vtalikka changed the title Accessing APM causes disc to not mount Accessing APM causes HDD to not mount Dec 20, 2018

@votdev

This comment has been minimized.

Copy link
Collaborator

votdev commented Dec 21, 2018

Please submit more information, e.g. screenshots and syslogs.

@votdev votdev added the 4.x label Dec 21, 2018

@vtalikka

This comment has been minimized.

Copy link

vtalikka commented Dec 22, 2018

@votdev : Can you specify which logs and screenshots should I post?

@votdev

This comment has been minimized.

Copy link
Collaborator

votdev commented Dec 23, 2018

hdparm errors are hard to debug because udev triggers this tool now. So i can only direct you to the blog post https://blog.dachary.org/2016/11/30/logging-udev-events-at-boot-time/ which explains how to debug udev events. This might help to identify the problem.

@vtalikka

This comment has been minimized.

Copy link

vtalikka commented Dec 23, 2018

Thanks! I'll try that once I have time to set my mind to it.

@vtalikka

This comment has been minimized.

Copy link

vtalikka commented Dec 25, 2018

Thanks for the link, I managed to get thorough logs using udev_log="debug". The log file immediately after boot is about 6MB; what should I search for and post here?

@votdev

This comment has been minimized.

Copy link
Collaborator

votdev commented Dec 27, 2018

I don't know, search for any errors.

@donhwy

This comment has been minimized.

Copy link

donhwy commented Jan 3, 2019

Try forcing a log rotate maybe?

@vtalikka

This comment has been minimized.

Copy link

vtalikka commented Jan 4, 2019

Can you clarify what I should achieve by log rotating?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment