Giga12 Posted February 10, 2022 Share Posted February 10, 2022 (edited) I am getting the errors below in my log: Feb 10 06:59:01 Tower emhttpd: shcmd (771): /usr/local/sbin/mount_image '/mnt/disks/Samsung_SSD_850_PRO_1TB_S252NSAG400601K/system/docker/docker.img' /var/lib/docker 40 Feb 10 06:59:01 Tower root: Creating new image file: /mnt/disks/Samsung_SSD_850_PRO_1TB_S252NSAG400601K/system/docker/docker.img size: 40G Feb 10 06:59:01 Tower root: ERROR: failed to zero device '/mnt/disks/Samsung_SSD_850_PRO_1TB_S252NSAG400601K/system/docker/docker.img': Input/output error Feb 10 06:59:01 Tower root: btrfs-progs v5.10 Feb 10 06:59:01 Tower root: See http://btrfs.wiki.kernel.org for more information. Feb 10 06:59:01 Tower root: Feb 10 06:59:01 Tower root: failed to create file system Feb 10 06:59:01 Tower emhttpd: shcmd (771): exit status: 1 My drive space seems fine. I have tried deleting the docker.img. Unmounting and repairing the drive with no luck. tower-diagnostics-20220210-0959.zip Edited February 10, 2022 by Giga12 Quote Link to comment
JorgeB Posted February 10, 2022 Share Posted February 10, 2022 UD device is mounted at: unassigned.devices: Mounting partition 'sdn1' at mountpoint '/mnt/disks/S252NSAG400601K'... And you're trying to create the image in Creating new image file: /mnt/disks/Samsung_SSD_850_PRO_1TB_S252NSAG400601K/ Not sure if it's a UD issue or not, but that's the problem, if you can't why this is happening best to post in the UD support thread. Quote Link to comment
Giga12 Posted February 10, 2022 Author Share Posted February 10, 2022 (edited) I have updated my vDisk location to use /mnt/disks/S252NSAG400601K which seems to have fixed the issue. I am unsure why this has come up now as an issue when I have been using that config for 3-4 years. Update: Not Fully fixed. My docker containers install fine now but they all now error out differently when trying to run Edited February 10, 2022 by Giga12 Quote Link to comment
JorgeB Posted February 10, 2022 Share Posted February 10, 2022 15 minutes ago, Giga12 said: I am unsure why this has come up now as an issue when I have been using that config for 3-4 years. Likely some UD update. 15 minutes ago, Giga12 said: My docker containers install fine now but they all now error out differently when trying to run They might still be referencing the old paths in the settings. Quote Link to comment
Giga12 Posted February 10, 2022 Author Share Posted February 10, 2022 2 hours ago, JorgeB said: UD device is mounted at: unassigned.devices: Mounting partition 'sdn1' at mountpoint '/mnt/disks/S252NSAG400601K'... And you're trying to create the image in Creating new image file: /mnt/disks/Samsung_SSD_850_PRO_1TB_S252NSAG400601K/ Not sure if it's a UD issue or not, but that's the problem, if you can't why this is happening best to post in the UD support thread. What file was this found in? Quote Link to comment
JorgeB Posted February 10, 2022 Share Posted February 10, 2022 I would recommend posting in the UD support thread to see if that change could be reversed, so no changes would be needed and it will likely affect other users, alternatively you need to check the mapping for every docker, if you had for example /mnt/disks/Samsung_SSD_850_PRO_1TB_S252NSAG400601K/apppata/container_name it needs to be changed to /mnt/disks/S252NSAG400601K/apppata/container_name Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.