Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Shrink Array - docker/vm no longer starting

Featured Replies

Hi all,

I have managed to break at least Docker and VM.

 

I followed the parity protected shrink array process. Wanted to remove Disk 2, so all that was remaining was Parity and Disk 1.

Once cleared and drive removed (Disk 2). Changed back settings.

Docker and VM fail to start, possibly to do with that they where on Disk 2 (but yes, did copy all files over to Disk 1).

Docker settings are mapped to /mnt/user/system/docker/docker.img and it is there, but something else must need to be changed? (Could it be mapped to /disk2/ somewhere?

 

What have I missed?

(Diag attached)

 

Also, Log has errors (attached) appears to be to do with cache?

 

Thanks in advance

System Log.htm server-diagnostics-20190719-2339.zip

  • Community Expert

The syslog is saying thet both the docker image file and the VM libvirt.img file are corrupt which explains why you do not have Docker or VMS running .  It sounds as if these were not copied successfully.

 

the docker image is easy enough to recover from by stopping the Docker Service; deleting the docker.img file; restarting the Docker service to create a new empty docker.img file and then using the Previous Apps section on the Apps tab to restore your docker containers with their settings intact.

 

the corrupt libvirt.img file for the VMs May be a bit trickier.    Do you have a backup of this file or copies of the XML for your VMS to avoid having to recreate their settings manually?

  • Author

thanks for the reply

 

Parity is still what it was prior to disk removal, is this any help?

  • Community Expert
2 minutes ago, saur said:

thanks for the reply

 

Parity is still what it was prior to disk removal, is this any help?

Unfortunately not.    Parity will just be reflecting the corrupt image files as it is not aware of file systems - just of raw disk sectors.

  • Author

thanks again

 

docker - the img file is just docker, if I reinstall my dockers from apps will they grab all the settings from each of the previous docker installs?

 

VMs - I had two VMs one being a “dual boot” bare metal. The other was just a base win10 with plex server. 

 

No back ups as I’m still getting comfortable with unraid and havent got any unreplaceable data on there. 

 

Edited by saur

Archived

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.