I’m just started using a Start9 server and am inexperienced with networking issues. I got it up and running and have Bitcoin Core, Electrs, and Mempool running successfully. I accomplished one backup to my home computer but have since moved the Start9 to a new location and want to back up to a dedicated SSD. I successfully formatted the backup drive to EXT4 and the Start9 can see the drive. When I attempt to backup, it tries for a while but then concludes with the following error message: “Failed: Filesystem I/O Error: /media/embassy/tmp/(52numbers and letters)/.os-backup.cbor.tmp”. Does anyone have a suggestion on what I might try?
It sounds like you are doing everything correctly. ext4 is the correct file system to use. I would try plugging the drive into a different port, switching cables, etc. to see if it changes. If that doesn’t work you might try reformatting the disk.
Ok, thank you. I initially tried using the USB-C port but the disk did not show up so then I plugged it into one of the old USB ports and it did show. I’ll try a different port.
1 Like
I think there’s a part to that error that you’ve not added, that should come right after .os-backup.cbor.tmp and tell us what the actual error was.
There is nothing after .os-backup.cbor.tmp in the error message. The backup now works for bitcoin core and electrs but not for mempool. I did change ports and restart the server. Is it necessary to backup the mempool?
It doesn’t quite make sense that somewhat randomly some services backup and others are interrupted by an error. You might want to keep troubleshooting, and maybe try another disk or interface/case/cable.
Other than that… things like Bitcoin, Electrs and Mempool only back up your configuration and for the most part don’t contain anything important that can’t be set up again in the time as starting fresh.
Where backups make a lot of sense is where either the configuration is very specific to you and you need to maintain it, where there are files involved with things like Nextcloud or where you have lightning channels with things like LND and CLN.
1 Like
I get a similar error i.e.:
RPC ERROR: Filesystem I/O Error /media/embassy/tmp/(random characters)/EmbasyBackups/cryps: Permision denied os error 13)
I am trying to push the backup to my NAS (using the credentials of the root user on the NAS).
The filesystem type on my NAS is Ext4.
The contents of the tmp folder seems to be owned by root:
start9@yummy-clams:/media/embassy/tmp$ ls -la
total 0
drwxr-xr-x 8 root root 160 Jan 11 06:47 .
drwxr-xr-x 1 root root 100 Jan 11 06:29 ..
drwxr-xr-x 2 root root 40 Jan 11 06:34 C6XM6Q54OYMEUZBKO56FR7FLRIJLBIEBSM37QS7H4FBEY6JLM2NA
drwxr-xr-x 2 root root 40 Jan 11 06:29 E3RNS3F3QI4CPNNQVCSNYORWLN7Q2ENU3BZWRJXFYL6JHCDWHRRQ
drwxr-xr-x 2 root root 40 Jan 11 06:38 LFRBUAQ4YUMNDKUXSWTM64SAVIZLJD2QPDW75LG7V63JJAPAM73Q
drwxr-xr-x 2 root root 40 Jan 11 06:47 QKMZAUSABU7F73YE6VFBHTHQLZYBLJDNSFT3CCQYLLNQNS2OTGQQ
drwxr-xr-x 2 root root 40 Jan 11 06:36 QW3NRKJBWPT7WRI7S2QFH5DAWZC2I4S6TTA2BA6JMT5FUHJI6XBA
drwxr-xr-x 2 root root 40 Jan 11 06:43 U3NCBKPZR75QPE7AC4QUH6NYNGP5J4DZBPNOWG5G3A5FHPGKTR5Q
Is the backup executing as start9 user via the GUI perhaps?
Error 23 is always username and password incorrect, or directory/samba share permissions set incorrectly.
Username and password, you’d resolve easily. Permissions, and how they should be on the NAS side is something we probably can’t help with and you’ll have to experiment with. But nothing to do with any Start9 user. The user is on your NAS, and it is the one that writes to your disks on the NAS, and whether than should be root or a smb user, depends on your setup.
This synology guide is a good starting point, even if not using synology.
https://docs.start9.com/0.3.5.x/device-guides/synology/backup-synology
You are correct. It is ownership on the NAS side.
I fixed it with:
chmod -R 777 /mnt/backupstart9
1 Like