Menu

Error writing the content file

Help
2018-05-29
2018-05-29
  • Webmaster33

    Webmaster33 - 2018-05-29

    I use OpenMediaVault server v3.0.99 (Erasmus) with Snapraid plugin for OpenMediaVault v3.7.3 installed (using snapraid v11.2 ). Debian GNU/Linux v8.10 (jessie).
    Using union filesystems plugin for OpenMediaVault v3.1.17 to merge the 4 data disks.
    Using 500GB to 1000GB hdds 4 data 2 parity (aka RAID6 mode).
    Parity drives are both 1000 GB.
    All data drives have at least 9 Gb free space.

    I execute
    snapraid sync
    then stops with the following error:

    1%, 13808 MB, 107 MB/s, CPU 13%, 2:04 ETA
    Autosaving...
    Saving state to /srv/dev-disk-by-label-SR1D1/snapraid.content...
    Saving state to /srv/dev-disk-by-label-SR2D2/snapraid.content...
    Saving state to /srv/dev-disk-by-label-SR3D3/snapraid.content...
    Saving state to /srv/dev-disk-by-label-SR4D4/snapraid.content...
    Error writing the content file '/srv/dev-disk-by-label-SR3D3/snapraid.content.tmp' in sync(). Input/output error.
    

    I can not find anything about it on Google.

    Any idea how to fix it?

     
  • Leifi Plomeros

    Leifi Plomeros - 2018-05-29

    I suspect a simple workaround would be to remove the content file located in SR3D3 from snapraid config file.
    It doesn't solve the problem that something is preventing snapraid from writing to SR3D3 but it should fix the problem that you can't sync.

     
  • UhClem

    UhClem - 2018-05-29

    The most likely cause of an "Error writing the content file ..." would be running out of space. BUT, that would have resulted in the error message specifying "No space left on device". Yours says "Input/output error".

    Getting that error message when writing to an [S]ATA disk is quite unusual, and likely indicates a (serious?) hard drive problem. What does SMART say about your SR3D3 drive?

    --Uh Clem

     

Log in to post a comment.