June 27, 20197 yr Hi, I moved my unraid to another server and took the opportunity to swap a disk to a bigger one. Since then I cannot get a single docker to work as I am getting i.e. this error root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-krusader' --net='bridge' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'TEMP_FOLDER'='/config/krusader/tmp' -e 'WEBPAGE_TITLE'='Tower' -e 'VNC_PASSWORD'='' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '6080:6080/tcp' -v '/mnt/':'/media':'rw' -v '/mnt/user/appdata/binhex-krusader':'/config':'rw' 'binhex/arch-krusader' 8885c4ce7c6e86f36502688b23f06509361b4051abb63673b4a33875a6829733 /usr/bin/docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/binhex-krusader': mkdir /mnt/user/appdata/binhex-krusader: input/output error. I have tried a new config, no luck. Here's the diagnostic file: https://app.box.com/s/n3ezzuib7g2x91zcg3s7a876747z91qv Any help is greatly appreciated as I am stuck. Cheers, Pim
June 28, 20197 yr Author Cheers mate, you're a legend. I ran xfs_repair and now looking through lost+found folder. What would you say is the cutoff point to replace the disk? It's only a year old. I did chuck it so unfortunately no warranty
July 1, 20197 yr Community Expert Filesystem corruption usually isn't due to a bad disk, and shouldn't be taken as a reason to replace without further evidence. And in this case, SMART for disk8 looks OK. I didn't look at other disks.
Archived
This topic is now archived and is closed to further replies.