Hi Viktor,I believe the reason for that is because your "usb_path1_fs_path0" is referring to sda1... but your sda1 label = null... One you put a label on that, then it won't complain on startup any longer.
I'm still trying to make sense out of all this, so thank you very much for providing this. Knowing that it's also referring to "usb_path2_fs_path0=sdb1" is very interesting.
Code:usb_path1_fs_path0=sda1 usb_path2_fs_path0=sdb1 usb_path_sda1_label= usb_path_sda2_label=Data usb_path_sdb1_label=rtr_swap
As I said yesterday, this morning I've been testing your quick beta (v1.39b1) and all seems to be working fine. I've done two different backups and modifying some BACKUPMON paths in order to detail testing of paths management. Backup files have been created as expected:
I've just seen an warning during the backup (tar: invalid option -- '2'). May be I'm wrong, but I think this warning was already appearing in previous version (v1.38) too...
Code:
[Primary Backup Commencing]...
Messages:
STATUS: External drive (USB) mounted successfully as: /XXXXXXXXXXXXXXXXXX/
STATUS: Finished backing up JFFS to /XXXXXXXXXXXXXXXXXX/GT-AX6000/Sun/jffs-20231119-095141.tar.gz.
STATUS: Finished backing up NVRAM to /XXXXXXXXXXXXXXXXXX/GT-AX6000/Sun/nvram-20231119-095141.cfg.
STATUS: Finished copying routerfw.txt to /XXXXXXXXXXXXXXX/GT-AX6000/Sun/routerfw-20231119-095141.txt.
STATUS: Starting backup of EXT Drive on Sun Nov 19 09:51:45 CET 2023. Please stand by...
tar: invalid option -- '2'
BusyBox v1.25.1 (2023-08-21 15:34:18 EDT) multi-call binary.
Usage: tar -[cxtzjhvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
z (De)compress using gzip
j (De)compress using bzip2
O Extract to stdout
h Follow symlinks
X File with names to exclude
T File with names to include
STATUS: Finished backing up EXT Drive in 0 sec to /XXXXXXXXXXXXXXXXXX/GT-AX6000/Sun/ -20231119-095141.tar.gz.
STATUS: Finished copying backupmon.sh script to /XXXXXXXXXXXXXXXXXX/GT-AX6000.
STATUS: Finished copying backupmon.cfg file to /XXXXXXXXXXXXXXXXXX/GT-AX6000.
STATUS: Finished copying reference nvram.txt extract to /XXXXXXXXXXXXXXXXXX/GT-AX6000.
STATUS: Finished copying restoration instructions.txt file to /XXXXXXXXXXXXXXXXXX/GT-AX6000.
STATUS: Settling for 10 seconds...
On the other hand, yesterday you wrote "I believe the reason for that is because your "usb_path1_fs_path0" is referring to sda1... but your sda1 label = null... One you put a label on that, then it won't complain on startup any longer", Sorry but I even can't figure how I have an sda1 device ... I've managed all of that by using my router webUI... Although it seems that partition is showed only by nvram show command, and not by blkid:
Code:
RT-AX6000:/tmp/home/root# blkid
/dev/sda2: LABEL="Data" UUID="CE2A3E342A3E19C3"
/dev/sdb1: LABEL="rtr_swap" UUID="6ee644d7-de49-4ef3-962a-311a40ebd725"
Edited:
May be I have the responsible... Windows... This disk was formatted in Windows, then connected to router and enabled as SMB drive... may be this is the "partition blank name" problem...
Code:
Disk /dev/sda: 4294967295 sectors, 2047G
Logical sector size: 512
Disk identifier (GUID): 800cea48-20f4-4c4e-8631-daade6f7b784
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7813969886
Number Start (sector) End (sector) Size Code Name
1 34 32767 15.9M 0700 Microsoft reserved partition
2 32768 7813965823 3725G 0700 Basic data partition
Anyway, I would be pleased if you, or anyone, can tell me how to label that partition -if possible- and I'll try it. If not, no problem. All is running fine with your quick 1.39b1 version.
Thanks for all your support.
Last edited: