since yesterday I get an "Error writing the content file 'C:/PoolHDDs/dru4/snapraid.content.tmp' in sync(). No such file or directory [2/2]." when I run an sync job.
There haven't been any changes to my hardware and my configuration.
If I comment out this content file in the config I get the error from another content file.
data d1 C:\PoolHDDs\dru1\PoolPart.65588c56-1907-444b-9b26-c59398d071cd
data d2 C:\PoolHDDs\dru2\PoolPart.677664ec-ba56-49d2-b22d-415a50ee33ea
data d3 C:\PoolHDDs\dru3\PoolPart.3f1f47b5-882d-4e05-8494-d583d473c9b3
data d4 C:\PoolHDDs\dru4\PoolPart.eabb4bad-7d98-42f9-88c9-fa305ed085d0
data d5 C:\PoolHDDs\dru5\PoolPart.8b1037c9-d1e9-4c62-b757-7f315b2f0f64
data d6 C:\PoolHDDs\dru6\PoolPart.95958a6f-e966-4e4f-94aa-41d4e87104e7
data d7 C:\PoolHDDs\dru7\PoolPart.4adf669a-6c65-4d5d-ae6e-9752020e006b
data d8 C:\PoolHDDs\dru8\PoolPart.c740e543-1386-4fa5-9139-5df3d2e3d8e3
There are 750GB free on this disk. The content file is about 3GB.
Copying the file did work.
After a sync job the tmp files already exists on all configured disks. They have exact the same size as the content files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would seem like the existing tmp files are preventing new ones from being created.
rename all .tmp files and try sync again. The tmp files should only exist during the sync, not after.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok i think 1 of my disk are dying. This seems to be causing the issues.
I would like to use 1 of my 2 parity disks as a data disk until the new disk arrives. Can I remove the 2. parity disk in the same way as a data disk or can I simply comment it out in the config?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, you can just comment out the last parity (in this case the snapraid.2-parity file) and run sync to be instantly rid of it.
But if you already have a dying data disk, wouldn't that be a situation where you really want a second parity in case something goes wrong during the recovery?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
since yesterday I get an "Error writing the content file 'C:/PoolHDDs/dru4/snapraid.content.tmp' in sync(). No such file or directory [2/2]." when I run an sync job.
There haven't been any changes to my hardware and my configuration.
If I comment out this content file in the config I get the error from another content file.
this is my config file:
parity C:\PoolHDDs\ppu1\snapraid.parity
2-parity C:\PoolHDDs\ppu2\snapraid.2-parity
content C:\snapraid\snapraid.content
content C:\PoolHDDs\dru1\snapraid.content
content C:\PoolHDDs\dru2\snapraid.content
content C:\PoolHDDs\dru3\snapraid.content
content C:\PoolHDDs\dru4\snapraid.content
content C:\PoolHDDs\dru5\snapraid.content
content C:\PoolHDDs\dru6\snapraid.content
content C:\PoolHDDs\dru7\snapraid.content
content C:\PoolHDDs\dru8\snapraid.content
data d1 C:\PoolHDDs\dru1\PoolPart.65588c56-1907-444b-9b26-c59398d071cd
data d2 C:\PoolHDDs\dru2\PoolPart.677664ec-ba56-49d2-b22d-415a50ee33ea
data d3 C:\PoolHDDs\dru3\PoolPart.3f1f47b5-882d-4e05-8494-d583d473c9b3
data d4 C:\PoolHDDs\dru4\PoolPart.eabb4bad-7d98-42f9-88c9-fa305ed085d0
data d5 C:\PoolHDDs\dru5\PoolPart.8b1037c9-d1e9-4c62-b757-7f315b2f0f64
data d6 C:\PoolHDDs\dru6\PoolPart.95958a6f-e966-4e4f-94aa-41d4e87104e7
data d7 C:\PoolHDDs\dru7\PoolPart.4adf669a-6c65-4d5d-ae6e-9752020e006b
data d8 C:\PoolHDDs\dru8\PoolPart.c740e543-1386-4fa5-9139-5df3d2e3d8e3
exclude *.unrecoverable
exclude Thumbs.db
exclude \$RECYCLE.BIN
exclude \System Volume Information
exclude \Program Files\
exclude \Program Files (x86)\
exclude \Windows\
blocksize 64
autosave 500
Please can you help me to sort this out?
Do you have enough space available there? Can you try with the same user in the same folder something like:
copy snapraid.content snapraid.content.tmp
?
There are 750GB free on this disk. The content file is about 3GB.
Copying the file did work.
After a sync job the tmp files already exists on all configured disks. They have exact the same size as the content files.
It would seem like the existing tmp files are preventing new ones from being created.
rename all .tmp files and try sync again. The tmp files should only exist during the sync, not after.
Ok i think 1 of my disk are dying. This seems to be causing the issues.
I would like to use 1 of my 2 parity disks as a data disk until the new disk arrives. Can I remove the 2. parity disk in the same way as a data disk or can I simply comment it out in the config?
Yes, you can just comment out the last parity (in this case the snapraid.2-parity file) and run sync to be instantly rid of it.
But if you already have a dying data disk, wouldn't that be a situation where you really want a second parity in case something goes wrong during the recovery?
Yes I think you are right. I will wait until my new drive arrives.
Thanks all for the help.