Jump to content

wrong fs type on /dev/loop1 after cache disk issue


georgez

Recommended Posts

Hi,

 

I accidentally removed the power cable from one of my cache disks (I got 2), and after reboot I notice the cache disk was missing, so I checked and reconnected the cable, after the reboot, a lot of the following errors appeared in syslog:

 

Dec 19 10:35:01 unRAID-48T emhttp: shcmd (1377): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20 |& logger
Dec 19 10:35:01 unRAID-48T root: mount: wrong fs type, bad option, bad superblock on /dev/loop1,
Dec 19 10:35:01 unRAID-48T root:        missing codepage or helper program, or other error
Dec 19 10:35:01 unRAID-48T root: 
Dec 19 10:35:01 unRAID-48T root:        In some cases useful info is found in syslog - try
Dec 19 10:35:01 unRAID-48T root:        dmesg | tail or so.
Dec 19 10:35:01 unRAID-48T root: mount error
Dec 19 10:35:01 unRAID-48T emhttp: err: shcmd: shcmd (1377): exit status: 1

I guess something's wrong with my cache disk, but seems like the contents on the cache disk are still fine, except mover seems not working any more.

 

Any suggestions on what to do ?

 

Thank you. 

Link to comment

Is loop1 the docker image?    On the 6.3.5 release it was normally the libvirt image.   On the latest 6.4 release it seems to be the ‘firmware’ image.  At least this is the case on my system - not sure if it is invariant or can vary according to underlying hardware or timings in boot process.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...