#2587 Issue closed: USB mount error: /dev/disk/by-label/REAR-0000 [sic!] does not exist (which is true)

Labels: support / question, fixed / solved / done

goodale opened issue at 2021-03-23 17:48:

  • ReaR version ("/usr/sbin/rear -V"): Relax-and-Recover 2.5 / Git

  • OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):

NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
OUTPUT=USB
BACKUP=NETFS
BACKUP_URL=usb:///dev/disk/by-label/REAR-0000

  • Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
    PC

  • System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
    Xeon

  • Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
    BIOS

  • Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
    Local Disk

  • Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT" or "lsblk" as makeshift):

NAME         KNAME      PKNAME    TRAN   TYPE  FSTYPE              SIZE MOUNTPOINT
/dev/loop0   /dev/loop0                  loop  squashfs            9.1M /snap/canonical-livepatch/95
/dev/loop1   /dev/loop1                  loop  squashfs            9.1M /snap/canonical-livepatch/94
/dev/loop2   /dev/loop2                  loop  squashfs           55.4M /snap/core18/1944
/dev/loop3   /dev/loop3                  loop  squashfs           97.8M 
/dev/loop4   /dev/loop4                  loop  squashfs           99.2M /snap/core/10859
/dev/loop6   /dev/loop6                  loop  squashfs           55.5M /snap/core18/1988
/dev/loop7   /dev/loop7                  loop  squashfs           99.2M /snap/core/10908
/dev/sda     /dev/sda             sata   disk                    465.8G 
|-/dev/sda1  /dev/sda1  /dev/sda         part  linux_raid_member 419.1G 
| `-/dev/md0 /dev/md0   /dev/sda1        raid1 ext4                419G /
|-/dev/sda2  /dev/sda2  /dev/sda         part                        1K 
`-/dev/sda5  /dev/sda5  /dev/sda         part  swap               46.7G [SWAP]
/dev/sdb     /dev/sdb             sata   disk                    465.8G 
|-/dev/sdb1  /dev/sdb1  /dev/sdb         part  linux_raid_member 419.1G 
| `-/dev/md0 /dev/md0   /dev/sdb1        raid1 ext4                419G /
|-/dev/sdb2  /dev/sdb2  /dev/sdb         part                        1K 
`-/dev/sdb5  /dev/sdb5  /dev/sdb         part  swap               46.7G [SWAP]
/dev/sdc     /dev/sdc             usb    disk                    465.8G 
`-/dev/sdc1  /dev/sdc1  /dev/sdc         part  ext3              465.8G /media/steve/REAR-000
/dev/sr0     /dev/sr0             sata   rom                      1024M

  • Description of the issue (ideally so that others can reproduce it):
    'No such process error' when trying to create a backup and rescue image

  • Workaround, if any:
    None

  • Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):

steve@rc-dev3:/opt$ sudo rear -v mkrescue
Relax-and-Recover 2.5 / Git
Running rear mkrescue (PID 2218855)
Using log file: /var/log/rear/rear-rc-dev3.log
ERROR: Mount command 'mount -v -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.FxrJFN7vQ7tElVo/outputfs' failed.
Some latest log messages since the last called script 060_mount_NETFS_path.sh:
  2021-03-23 10:59:43.482161534 Including prep/NETFS/default/060_mount_NETFS_path.sh
  mkdir: created directory '/tmp/rear.FxrJFN7vQ7tElVo/outputfs'
  2021-03-23 10:59:43.491181829 Mounting with 'mount -v -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.FxrJFN7vQ7tElVo/outputfs'
  mount: /tmp/rear.FxrJFN7vQ7tElVo/outputfs: special device /dev/disk/by-label/REAR-0000 does not exist.
Aborting due to an error, check /var/log/rear/rear-rc-dev3.log for details
Exiting rear mkrescue (PID 2218855) and its descendant processes ...

goodale commented at 2021-03-23 17:58:

Tried to start over by umount'ing and then formatting. now get this:

steve@rc-dev3:/opt$ sudo rear format /dev/sdc
USB device /dev/sdc is not formatted with ext2/3/4 or btrfs filesystem
Type exactly 'Yes' to format /dev/sdc with ext3 filesystem
(default 'No' timeout 300 seconds)
Yes
ERROR: Failed to create ext3 filesystem on '/dev/sdc1'
Some latest log messages since the last called script 300_format_usb_disk.sh:
  2021-03-23 10:56:56.608741815 Repartitioning '/dev/sdc'
  2021-03-23 10:56:56.611732227 Creating partition table of type 'msdos' on '/dev/sdc'
  2021-03-23 10:56:56.716227586 Creating ReaR data partition up to 100% of '/dev/sdc'
  Warning: The resulting partition is not properly aligned for best performance: 16384s % 65535s != 0s
  2021-03-23 10:56:56.971326201 Setting 'boot' flag on /dev/sdc
  2021-03-23 10:57:02.463741204 Creating ext3 filesystem with label 'REAR-000' on '/dev/sdc1'
  mke2fs 1.45.5 (07-Jan-2020)
  /dev/sdc1 is mounted; will not make a filesystem here!
Aborting due to an error, check /var/log/rear/rear-rc-dev3.log for details
Terminated

goodale commented at 2021-03-23 20:02:

Tried again after a hard reboot: here's the format and mkrescue commands and output. I also upgraded to v2.6 but still failing

steve@rc-dev3:~$ sudo rear format /dev/sda
USB device /dev/sda is not formatted with ext2/3/4 or btrfs filesystem
Type exactly 'Yes' to format /dev/sda with ext3 filesystem
(default 'No' timeout 300 seconds)
Yes

steve@rc-dev3:~$ sudo rear -v mkrescue
Relax-and-Recover 2.6-git.4265.4b43f43.master / 2021-02-23
Running rear mkrescue (PID 19646 date 2021-03-23 13:01:01)
Using log file: /var/log/rear/rear-rc-dev3.log
Running workflow mkrescue on the normal/original system
ERROR: Mount command 'mount  -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.nhAFrchAmk3DJft/outputfs' failed.
Some latest log messages since the last called script 060_mount_NETFS_path.sh:
  2021-03-23 13:01:02.396796814 Including prep/NETFS/default/060_mount_NETFS_path.sh
  2021-03-23 13:01:02.422675643 Mounting with 'mount  -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.nhAFrchAmk3DJft/outputfs'
Aborting due to an error, check /var/log/rear/rear-rc-dev3.log for details
Exiting rear mkrescue (PID 19646) and its descendant processes ...
Running exit tasks
Terminated
steve@rc-dev

jsmeix commented at 2021-03-24 07:32:

@goodale

the first error
i.e. the one in https://github.com/rear/rear/issues/2587#issue-838971802
is

ERROR: Mount command 'mount -v -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.FxrJFN7vQ7tElVo/outputfs' failed.
...
mount: /tmp/rear.FxrJFN7vQ7tElVo/outputfs: special device /dev/disk/by-label/REAR-0000 does not exist.

the second error
i.e. the one in https://github.com/rear/rear/issues/2587#issuecomment-805111028
is

ERROR: Failed to create ext3 filesystem on '/dev/sdc1'
...
mke2fs 1.45.5 (07-Jan-2020)
/dev/sdc1 is mounted; will not make a filesystem here!

the third error
i.e. the one in https://github.com/rear/rear/issues/2587#issuecomment-805199097
is only

ERROR: Mount command 'mount  -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.nhAFrchAmk3DJft/outputfs' failed.

but the actual mount error message is not shown so you
need to check /var/log/rear/rear-rc-dev3.log for details

According to your lsblk output it seems /dev/sda is your system disk
and /dev/sdc is your USB disk
so rear format /dev/sda would format your system disk
which is likely not what you want to do?

goodale commented at 2021-03-24 13:25:

My apologies. let's start from the beginning

here is the output from fdisk -l.
It shows the T7 (500GB USD SSD) as /dev/sda.
This is the device I want to use for the backup and emergency recovery image.
/dev/sdb & /dev/sdc are the server's HDD's setup as Linux SW RAID 1 (/dev/md0).
My goal is to create a recovery image, replace the two HDD's with SSD's
and then restore the image from the T7. OS is Ubuntu 20.04 LTS.

Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: PSSD T7         
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x86e4c2ba

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1  *    16384 976773167 976756784 465.8G 83 Linux

Disk /dev/sdb: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5003ABYX-1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe5d650e0

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1  *         2048 878905343 878903296 419.1G fd Linux raid autodetect
/dev/sdb2       878907390 976771071  97863682  46.7G  5 Extended
/dev/sdb5       878907392 976771071  97863680  46.7G 82 Linux swap / Solaris

Disk /dev/sdc: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5003ABYX-1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe5d65731

Step 1: format /dev/sda, which succeeds:

steve@rc-dev3:$ sudo rear format /dev/sda
USB device /dev/sda is not formatted with ext2/3/4 or btrfs filesystem
Type exactly 'Yes' to format /dev/sda with ext3 filesystem
(default 'No' timeout 300 seconds)
Yes
steve@rc-dev3:$

Step 2: attempt to create the recovery:

steve@rc-dev3:~$ sudo rear -v mkrescue
Relax-and-Recover 2.6-git.4265.4b43f43.master / 2021-02-23
Running rear mkrescue (PID 308653 date 2021-03-24 06:22:04)
Using log file: /var/log/rear/rear-rc-dev3.log
Running workflow mkrescue on the normal/original system
ERROR: Mount command 'mount  -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.4ar53p6X6FGp2NS/outputfs' failed.
Some latest log messages since the last called script 060_mount_NETFS_path.sh:
  2021-03-24 06:22:05.221055473 Including prep/NETFS/default/060_mount_NETFS_path.sh
  2021-03-24 06:22:05.229841194 Mounting with 'mount  -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.4ar53p6X6FGp2NS/outputfs'
Aborting due to an error, check /var/log/rear/rear-rc-dev3.log for details
Exiting rear mkrescue (PID 308653) and its descendant processes ...
Running exit tasks
Terminated

Here is the log contents

021-03-24 06:22:04.997855275 Relax-and-Recover 2.6-git.4265.4b43f43.master / 2021-02-23
2021-03-24 06:22:04.999678620 Running rear mkrescue (PID 308653 date 2021-03-24 06:22:04)
2021-03-24 06:22:05.001293653 Command line options: /usr/sbin/rear -v mkrescue
2021-03-24 06:22:05.002931591 Using log file: /var/log/rear/rear-rc-dev3.log
2021-03-24 06:22:05.004817880 Including /etc/rear/os.conf
2021-03-24 06:22:05.009161900 Including conf/Linux-i386.conf
2021-03-24 06:22:05.011146774 Including conf/GNU/Linux.conf
2021-03-24 06:22:05.033959877 Including conf/Ubuntu.conf
2021-03-24 06:22:05.040090737 Including /etc/rear/local.conf
2021-03-24 06:22:05.044205962 ======================
2021-03-24 06:22:05.045753391 Running 'init' stage
2021-03-24 06:22:05.047323438 ======================
2021-03-24 06:22:05.057629846 Including init/default/005_verify_os_conf.sh
2021-03-24 06:22:05.063163464 Including init/default/010_EFISTUB_check.sh
2021-03-24 06:22:05.068930730 Including init/default/010_set_drlm_env.sh
2021-03-24 06:22:05.074831239 Including init/default/030_update_recovery_system.sh
2021-03-24 06:22:05.080719451 Including init/default/050_check_rear_recover_mode.sh
2021-03-24 06:22:05.083059125 Running workflow mkrescue on the normal/original system
2021-03-24 06:22:05.089642281 Including init/default/950_check_missing_programs.sh
2021-03-24 06:22:05.099279932 Finished running 'init' stage in 0 seconds
2021-03-24 06:22:05.107921588 Using build area '/tmp/rear.4ar53p6X6FGp2NS'
2021-03-24 06:22:05.112998907 Running mkrescue workflow
2021-03-24 06:22:05.115060172 ======================
2021-03-24 06:22:05.117132561 Running 'prep' stage
2021-03-24 06:22:05.119221453 ======================
2021-03-24 06:22:05.130189842 Including prep/default/005_remove_workflow_conf.sh
2021-03-24 06:22:05.139113774 Including prep/default/020_translate_url.sh
2021-03-24 06:22:05.145616568 Including prep/default/030_translate_tape.sh
2021-03-24 06:22:05.155641156 Including prep/default/035_valid_backup_methods.sh
2021-03-24 06:22:05.162252446 Including prep/default/036_valid_output_methods.sh
2021-03-24 06:22:05.168866972 Including prep/default/040_check_backup_and_output_scheme.sh
2021-03-24 06:22:05.182790867 Including prep/NETFS/default/040_inspect_configuration_files.sh
2021-03-24 06:22:05.189359563 Including prep/USB/default/040_set_NETFS_requirements.sh
2021-03-24 06:22:05.195895238 Including prep/NETFS/default/050_check_NETFS_requirements.sh
2021-03-24 06:22:05.203577422 Skipping 'ping' test for host '' in BACKUP_URL 'usb:///dev/disk/by-label/REAR-0000'
2021-03-24 06:22:05.214449932 Including prep/default/050_check_keep_old_output_copy_var.sh
2021-03-24 06:22:05.221055473 Including prep/NETFS/default/060_mount_NETFS_path.sh
2021-03-24 06:22:05.229841194 Mounting with 'mount  -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.4ar53p6X6FGp2NS/outputfs'
2021-03-24 06:22:05.242928104 ERROR: Mount command 'mount  -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.4ar53p6X6FGp2NS/outputfs'
 failed.
2021-03-24 06:22:05.251332325 Exiting rear mkrescue (PID 308653) and its descendant processes ...
2021-03-24 06:22:08.285267701 rear,308653 /usr/sbin/rear -v mkrescue
  `-rear,308912 /usr/sbin/rear -v mkrescue
      `-pstree,308913 -Aplau 308653
2021-03-24 06:22:08.309647000 Running exit tasks
2021-03-24 06:22:08.314751997 Finished rear mkrescue in 4 seconds
2021-03-24 06:22:08.316917218 Removing build area /tmp/rear.4ar53p6X6FGp2NS
2021-03-24 06:22:08.325198654 End of program reached

Here is my local.conf

# Default is to create Relax-and-Recover rescue media as ISO image
# set OUTPUT to change that
# set BACKUP to activate an automated (backup and) restore of your data
# Possible configuration values can be found in /usr/share/rear/conf/default.conf
#
# This file (local.conf) is intended for manual configuration. For configuration
# through packages and other automated means we recommend creating a new
# file named site.conf next to this file and to leave the local.conf as it is. 
# Our packages will never ship with a site.conf
OUTPUT=USB
BACKUP=NETFS
BACKUP_URL=usb:///dev/disk/by-label/REAR-0000

goodale commented at 2021-03-24 13:43:

this may be helpful.

steve@rc-dev3:/var$ sudo rear -v checklayout
Relax-and-Recover 2.6-git.4265.4b43f43.master / 2021-02-23
Running rear checklayout (PID 315390 date 2021-03-24 06:42:44)
Using log file: /var/log/rear/rear-rc-dev3.log.lockless
Running workflow checklayout on the normal/original system
ERROR: No (non-empty) /var/lib/rear/layout/disklayout.conf file (needs to be created before e.g. via 'rear mkrescue/mkbackup')
Some latest log messages since the last called script 110_check_layout_file.sh:
  2021-03-24 06:42:44.361612953 Including layout/precompare/default/110_check_layout_file.sh
Aborting due to an error, check /var/log/rear/rear-rc-dev3.log.lockless for details
Exiting rear checklayout (PID 315390) and its descendant processes ...
Running exit tasks
Terminated

ls -l /var/lib/rear shows no disklayout.conf...

steve@rc-dev3:/var/lib/rear/recovery$ ls -l
total 4
-rw-r--r-- 1 root root 9 Mar 23 10:26 bootdisk

goodale commented at 2021-03-24 13:59:

p.s. i also just tried uninstall and reinstall, thinking there was an issue with the initial installation not creating disklayout.conf. No luck though.. Note: installing from apt repository reverted the version from 2.6 to 2.5 (I had downloaded the 2.6 dpgk and did a manual install yesterday thinking the latest version might fix things)

sudo apt remove rear
sudo apt intall rear
sudo rear -v checklayout

the last command yields the same error as above

jsmeix commented at 2021-03-24 14:01:

@goodale
we really do need a full debug log file

Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files)

that we ask for via our
https://raw.githubusercontent.com/rear/rear/master/.github/ISSUE_TEMPLATE.md
which is shown to you when you click on [New issue] at
https://github.com/rear/rear/issues

I.e. we need your /var/log/rear/rear-*.log file that matches
your rear -D mkrescue call that fails for you.

FYI:
For you "rear mkrescue" fails in its early prep stage
before any disklayout.conf will be created.

goodale commented at 2021-03-24 14:05:

Thank you @jsmeix here is the log file
rear-rc-dev3.log

jsmeix commented at 2021-03-24 14:39:

Your https://github.com/rear/rear/files/6197823/rear-rc-dev3.log
contains the actual error:

+++ mount -v -o rw,noatime /dev/disk/by-label/REAR-0000 /tmp/rear.TkwNW2ajNvQk3IV/outputfs
mount: /tmp/rear.TkwNW2ajNvQk3IV/outputfs: special device /dev/disk/by-label/REAR-0000 does not exist.

Argh!
I found the reason.

Hint:
It is just one little more character in BACKUP_URL, cf.
http://relax-and-recover.org/documentation/getting-started

I think you find it yourself with my hint.
If not I tell you tomorrow - now is "end of office time" for me.

goodale commented at 2021-03-24 16:08:

ah! that resolved the issue. thank you

[Export of Github issue for rear/rear.]