Installing Raspiblitz amd64 image on Digital Ocean - hddCandidate is wrong.

I successfully imported the raspiblitz_amd64 image in Digital Ocean and installed it in a very cheap instance. This can be very useful for some use cases.

When I try to run a FRESH INSTALL, the script selects VDB as hddCandidate, and the correct disk is SDA. sda 8:0 0 600G 0 disk vda 254:0 0 80G 0 disk └─vda1 254:1 0 48.8G 0 part vdb 254:16 0 452K 1 disk

Then I got this error.

Running Format: (ext4) (vdb)
# DATA DRIVE - FORMATTING to EXT4 layout (old)
(standard_in) 1: syntax error
# Unmounting all partitions of this device
# Cleaning /etc/fstab from 2022-05-01-13-34-27-00
# Wiping all partitions (sfdisk/wipefs)
wipefs: /dev/vdb: failed to erase iso9660 magic string at offset 0x00008001: Operation not permitted
Error: Operation not permitted during write on /dev/vdb
# Creating the one big partition
Error: /dev/vdb: unrecognised disk label
# waiting until the partition gets available
# waiting until the partition gets available
# waiting until the partition gets available
# waiting until the partition gets available
# waiting until the partition gets available
# waiting until the partition gets available
# waiting until the partition gets available
# waiting until the partition gets available
# waiting until the partition gets available
# waiting until the partition gets available
# waiting until the partition gets available
# partition failed
FAIL ON FORMATTING THE DRIVE:
partition failed
Please report as issue on the raspiblitz github.

In order to select the right hddCandidate, on controlSetupDialog.sh I commented the line 147 and added hddCandidate="sda" on line 148, so the script goes on smoothly, and format the drive SDA, ask for the passwords,

Here is the code changed 147 # source <(/home/admin/_cache.sh get hddGotMigrationData hddBlocksBitcoin hddBlocksLitecoin hddCandidate) 148 hddCandidate="sda"

Then it fails to mount the disk and the script stops on the Provisioning part. Here is the raspiblitz.log https://pastebin.com/0MjjwJmr

Which file do I need to change in order to mount the disk correctly, or tell the script to use sda as hddCandidate for the entire process?

[motolese]

No way, several different errors, and after restarting this screen! https://imgur.com/a/gzwfOKb

In the log provision did not ran thru - need fresh sd card.

[ktecho]

I think the conclusion here is that the blitz.datadrive.sh needs a complete rewrite.

Probably should apply less logic and offer a simple menu to choose the intended disks or partitions in a menu if the defaults are not met.

Yes, I fully agree. I’m trying to install this in a container inside a Proxmox server, and I cannot make it work because I don’t have /dev/xxx:

Filesystem                       Size  Used Avail Use% Mounted on
/dev/mapper/vg-vm--103--disk--0   40G  9.5G   28G  26% /
/dev/mapper/vg-vm--103--disk--1  590G   56K  560G   1% /mnt/hdd