EXT4 : "Remounting filesystem read-only" every 2-3 days

    • OMV 2.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • EXT4 : "Remounting filesystem read-only" every 2-3 days

      Hello!

      I'm running OMV 2.2.1 on an Odroid XU4. The system is installed on the SDCARD, and I use an external hard-drive (USB2, 500GO) as storage. The system is idle most of the time, I generally use it to listen to music or watch movies in the evening.
      It runs perfectly for 4-5 weeks, except that I notice that, since 1-2 weeks, the storage filesystem is remounted in read-only mode every 2 days.

      It happened today, here is the relevant output from dmesg:

      Source Code

      1. [522943.556672] [c1] EXT4-fs error (device sda1): __ext4_journal_start_sb:62: Detected aborted journal
      2. [522943.564383] [c1] EXT4-fs (sda1): Remounting filesystem read-only


      In order to bring the filesystem back in write mode, I need to unmount it, run fsck.ext4. Then, when it is remounted, it is accessible in write mode... until the next time it is remounted in readonly mode...

      I know that there are a lot of chances that my disk is dying, but... how can I diagnose it?
      After the fsck, the hard drive works correctly, I can write big files at good speeds and they do not seem to be corrupted.
      Is there any other reason for this kind of errors?

      Thanks!
    • It might be an unsupported sleep mode of the usb-to-sata controller. Not sure what could fix that though other than trying a different usb-to-sata dock.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.10
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron, you might be right... I'm under the impression that this happen when the drive is woken up by a write request. For example, I experienced this when I wanted to download a file with the 'downloader' function.
      It doesn't seem to happen when I just want to read files from the disk.

      Should I try different settings in "physical drive" from the administration panel (Advanced Power Management, automatic acoustic management)?
      There are several choices. For now, they are disabled, only the spin-down delay is set to 10 minutes.

      The external hard drive is this one from lacie : overclockers.co.uk/b-grade-lac…hard-drive-bg-022-lc.html
    • I've tried setting various values in the options of the physical drive (power management) without any luck : I experience random FS corruption. It seems to happen when the drive needs to restart from sleep mode.

      Previously, I used this same hard drive on my router with OpenWRT. At that time, it was formatted in FAT32, but I've never observed any corruption (but I don't know if FAT32 is smart enough to detect them).

      Is there any solution to this issue?
    • Unfortunately, no...
      I'm still using it, but I regularly have to fsck the filesystem. I didn't see any corruption, but I don't use it for sensible data.
      I tried many things, parameters, commands,... with no luck.
      As ryecoaaron said, it might be an unsupported sleep mode, bug in the driver, in the USB adapter,...

      I plan on buying bigger hard drive, but I don't know if the issue will still be there or not...

      My conclusion : use native Sata... USB has its limitations...
    • thor-ua wrote:

      I'm on 3.0.96 version and use pi3 with OMV. Still have exactly the same issue as JF002 has described
      If you use exactly the same setup (unreliable USB storage powered by an SBC) then most probably you run into the same issue called 'undervoltage'.

      Since you're using 3.0.96 you can simply open a shell and call

      Source Code

      1. sudo raspimon
      (stop with [ctrl]-[c] after a minute). To interpret the results: New approach for Raspberry Pi OMV images
    • Thank you for your information!
      I've red your topic on raspimon and did the test myself with some load (torrents+film vis smb). As far as I can understand I get normal results. I use official raspberry pi power supply which claim up to 2.5A

      Source Code

      1. Time Temp CPU fake/real Health state Vcore
      2. 18:04:05: 60.7'C 1200/1200 MHz 0000000000000000000 1.2813V
      3. 18:04:10: 61.2'C 1200/1200 MHz 0000000000000000000 1.2813V
      4. 18:04:15: 61.8'C 1200/1200 MHz 0000000000000000000 1.2813V
      5. 18:04:20: 61.2'C 1200/1200 MHz 0000000000000000000 1.2813V
      6. 18:04:25: 61.2'C 600/ 600 MHz 0000000000000000000 1.2V
      7. 18:04:30: 60.1'C 600/ 600 MHz 0000000000000000000 1.2V
      8. 18:04:35: 60.1'C 600/ 600 MHz 0000000000000000000 1.2V
      9. 18:04:40: 61.2'C 1200/1200 MHz 0000000000000000000 1.2813V
      10. 18:04:45: 61.2'C 1200/1200 MHz 0000000000000000000 1.2813V
      11. 18:04:50: 60.7'C 1200/1200 MHz 0000000000000000000 1.2813V
      12. 18:04:55: 61.2'C 1200/1200 MHz 0000000000000000000 1.2813V
      13. 18:05:00: 60.7'C 1200/1200 MHz 0000000000000000000 1.2813V
      14. 18:05:06: 61.2'C 1200/1200 MHz 0000000000000000000 1.2813V
      15. 18:05:11: 61.2'C 1200/1200 MHz 0000000000000000000 1.2813V
      16. 18:05:16: 61.2'C 600/ 600 MHz 0000000000000000000 1.2V
      Display All
      I, also, use Y-shaped cable to my hard drive enclosure and power it power it from two USB ports at the same time. I'm going to experiment with additional power adapter for a hard drive.

      The post was edited 1 time, last by thor-ua ().

    • thor-ua wrote:

      As far as I can understand I get normal results
      At least raspimon is not reporting input voltage dropping below 4.65V. What's imporant is what's available at the disk (this is always lower than the input voltage) and many disk brands start to show problems as soon as their voltage drops below 4.75V (this is the minimum allowed by USB specs anyway). So it's perfectly normal that RPi shows no signs of undervoltage (4.65V INPUT) while at the same time a connected disk suffers from this (since VBUS OUTPUT voltage drops below 4.75V).

      The power circuitry on those Raspberry Pis is crap (read comments over there especially from lvrp16), the decision to use Micro USB for DC-IN as well and if you decide to let your RPi power a connected disk you're usually simply asking for troubles while not even being aware of the whole problem (Ohm's law) since the RPi foundation decided to masquerade the problem instead of fixing it.

      Y-cables don't help with voltage drops when connected to the same device (so useless here since all USB ports of a RPi share the same current limitation and the problem is not related to current but voltage drop under load) and it's strongly recommended to NEVER EVER use Y-cables with two different power sources since you can fry your device easily. These things are forbidden by USB specs for a reason.
    • thor-ua wrote:

      HI,
      I'm on 3.0.96 version and use pi3 with OMV. Still have exactly the same issue as JF002 has described. Couldn't find the solution either.

      In my case, the external hard-drive died before I could find a solution for this issue. It was old, it was small, it was slow... I replaced it with 2*4TB on USB3, and they work very well.
      I don't think I had power issue, as the drive was self-powered. But I could imagine that a diyng drive could corrupt the filesystem during its agony...