I have my appdata, docker.img, and some settings on my cache drive. After the first boot of 6.4.0 I see this in my log. I never had a problem with my cache drive. I see the cache drive settings as well, so I'm at a stumper. Why would my cache drive not mount on 6.4.0 but work fine on 6.3.5?

 

 

 

 

 

Jan 25 21:12:25 SUN root: = sunit=0 swidth=0 blks
Jan 25 21:12:25 SUN root: naming =version 2 bsize=4096 ascii-ci=0 ftype=1
Jan 25 21:12:25 SUN root: log =internal bsize=4096 blocks=476930, version=2
Jan 25 21:12:25 SUN root: = sectsz=512 sunit=0 blks, lazy-count=1
Jan 25 21:12:25 SUN root: realtime =none extsz=4096 blocks=0, rtextents=0
Jan 25 21:12:25 SUN emhttpd: shcmd (170): mkdir -p /mnt/cache
Jan 25 21:12:25 SUN emhttpd: /mnt/cache mount error: Unsupported partition layout
Jan 25 21:12:25 SUN emhttpd: shcmd (171): umount /mnt/cache
Jan 25 21:12:25 SUN root: umount: /mnt/cache: not mounted.
Jan 25 21:12:25 SUN emhttpd: shcmd (171): exit status: 32
Jan 25 21:12:25 SUN emhttpd: shcmd (172): rmdir /mnt/cache
Jan 25 21:12:25 SUN emhttpd: shcmd (173): sync

Edited January 26, 20188 yr by opentoe

14 minutes ago, opentoe said:

Why would my cache drive not mount on 6.4.0 but work fine on 6.3.5?

• If your cache disk has an "incompatible partition" after upgrading, it was probably created in an older version of the Unassigned Devices plugin. UD has been updated so this won't happen again.

  
  This is a one-time fix. You'll need to downgrade to 6.3.5 and move the data off the cache drive, re-format the disk and move the data back.  The procedure is outlined here
   

I did make a backup of my cache drive, so able to just reformat it, then copy the old contents back on.