Hi, I have a SBC (Odroid HC2), with just one 3TB data disk and an SD-card containing the boot partition.
I make regular backups of said data disk with Duplicati.
Last weekend, the data disk crashed, and I am planning to replace it with a new one (probably SSD while I’m at it).
What would be the best way to go about this? Can I simply replace the now broken disk (shows “missing” in OMV) with the new one, give it the same volume name, and restore my folders? It looks like I cannot delete the “missing” volume from the GUI...
Replace broken disk (single disk setup)
-
- OMV 4.x
- justtim
-
-
Try deleting shares and anything else that reference the missing volume, then delete it.
You will have to create a new filesystem and a new share. Then you can restore the contents.
-
Thanks Adoby, ok, so there is no easy way to replace the existing volume with a new one and keep the volumename?
-
-
You could clone the old drive to the new. But the old is crashed, so...
The UUID must match for OMV to accept the new drive as the old.
-
The UUID must match for OMV to accept the new drive as the old.
If the disk is mounted
"by-id""by-label" should it not be enough to just adjust theidlabel? I would try if it is working.It seems to be also possible to change the UUID if needed
https://askubuntu.com/question…a-disk-to-whatever-i-want -
If the disk is mounted "by-id" should it not be enough to just adjust the id? I would try if it is working.
Where would I adjust the ID? Can you elaborate a on this?
It seems to be also possible to change the UUID if needed
askubuntu.com/questions/132079…a-disk-to-whatever-i-wantThis is an interesting option. I guess I could give this a shot as soon as my new disk arrives, since I have nothing to lose (I'll make a backup of my SD boot card first)
-
-
Where would I adjust the ID? Can you elaborate a on this?
Sorry. I meant label, not ID
On OMV (currently) drives are mounted as "dev-disk-by-label-xxx".
Previously they were mounted as "dev-disk-by-UUID-xxxxx"
-
Sorry. I meant label, not ID
On OMV (currently) drives are mounted as "dev-disk-by-label-xxx".
Previously they were mounted as "dev-disk-by-UUID-xxxxx"
Ok, that is indeed the case, the broken disk is still visible as dev/disk/by-label/volume2.So how would I go about setting the same label for the new disk? That cannot be done if the old disk is still present, and I cannot remove the old disk because the shares (and probably other stuff) still has references to the old disk.
I will try adding the old UUID to the new disk first, to see if that does the trick. If it doesn't, it looks like the only way is to go with @Adoby's suggestion, cleanup all references, remove the old disk and add the new disk.
-
So how would I go about setting the same label for the new disk?
You can boot a linux live distro on your laptop/PC and do this.
OMV will also boot with the new disk and just complain that the other disk is missing. Don't mount the new disk in the GUI of OMV. Don't do anything in the GUI of OMV at this stage.
But you can do the changes from CLI. -
-
You can boot a linux live distro on your laptop/PC and do this.
So, add the new disk to a Linux sytem, format in ext4, change the label to volume2, and add it back in my Odroid? I guess that is worth a shot!
-
Copy your data on the drive, so that the shared folders are found as well.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!