{"action":"opened","issue":{"url":"https://api.github.com/repos/rear/rear/issues/1467","repository_url":"https://api.github.com/repos/rear/rear","labels_url":"https://api.github.com/repos/rear/rear/issues/1467/labels{/name}","comments_url":"https://api.github.com/repos/rear/rear/issues/1467/comments","events_url":"https://api.github.com/repos/rear/rear/issues/1467/events","html_url":"https://github.com/rear/rear/issues/1467","id":254822997,"number":1467,"title":"Problems with bootloader and excluding devices","user":{"login":"malvinas2","id":25912063,"avatar_url":"https://avatars0.githubusercontent.com/u/25912063?v=4","gravatar_id":"","url":"https://api.github.com/users/malvinas2","html_url":"https://github.com/malvinas2","followers_url":"https://api.github.com/users/malvinas2/followers","following_url":"https://api.github.com/users/malvinas2/following{/other_user}","gists_url":"https://api.github.com/users/malvinas2/gists{/gist_id}","starred_url":"https://api.github.com/users/malvinas2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/malvinas2/subscriptions","organizations_url":"https://api.github.com/users/malvinas2/orgs","repos_url":"https://api.github.com/users/malvinas2/repos","events_url":"https://api.github.com/users/malvinas2/events{/privacy}","received_events_url":"https://api.github.com/users/malvinas2/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-09-02T16:52:50Z","updated_at":"2017-09-02T16:52:50Z","closed_at":null,"author_association":"NONE","body":"* rear version: Relax-and-Recover 2.2 / Git\r\n* OS version:  Debian GNU/Linux 8.9 (jessie) with Openmediavault 3.0.87)\r\n* rear configuration files: please see below\r\n* Are you using legacy BIOS or UEFI boot? UEFI \r\n\r\nHello, \r\nplease let me explain two things before describing my problems: \r\n\r\n- I know that ReaR is mostly used within professional environments, but my NAS, serving as media server at home, seems to be a little special, at least every other program I tried (like the 64-bit version of Clonezilla) just throws out error messages during startup. The problem seems to be the combination between 64-bit, boot by UEFI (GRUB2-bootloader) and a M.2-SSD attached via PCIexpress and NVMe. \r\n- I am also aware that the issue-section of github is normally not used to discuss user problems, but I could not found any other forum and the mailing list doesn't seem to be very populated. \r\n\r\n## Starting situation and objective\r\nI have got a self-built NAS Server which boots from a SSD (/dev/nvme0n1) and uses two hard-disks (/dev/sda, /dev/sdb) which form a software raid 1 device (/srv/dev-disk-by-label-OMVDisc). \r\nI want to clone SSD to recover a broken system. \r\n\r\n\r\n## First attempt (creating USB-stick, bootloader not working)\r\nI installed Rear and started with the usage scenario of building a bootable USB stick. \r\n`rear format /dev/sdc`. The USB stick is successfully formated and labeled as `REAR-000`. \r\nThe content of the configuration file is: \r\n`OUTPUT=USB`\r\n`BACKUP=NETFS`\r\n`BACKUP_URL=\"usb:///dev/disk/by-label/REAR-000\"`\r\n`rear format /dev/sdc` doesn't work and gives the following error message: \r\n_ERROR: /dev/disk/by-label/REAR-EFI is not block device. Use `rear format -- --efi <USB_device_file>' for correct format_\r\n\r\nObviously, REAR tries to use the correct bootloader (USING_UEFI_BOOTLOADER=1) and is searching for a label 'REAR-EFI', which does not exist. \r\nAfter modifiying the configuration file \r\n`BACKUP_URL=\"usb:///dev/disk/by-label/REAR-**EFI**\"`\r\nand changing the label `e2label /dev/sdc1 \"REAR-**EFI**\"` the command `rear format /dev/sdc` works. \r\nBut when I try do boot from the created USB stick I get the error message: \r\n`No DEFAULT or UI configuration directive found!`\r\nTrying the same procedure another time resulted in the error message: \r\n`Failed to load COM32 file chain.c32`\r\n`Failed to load COM32 file menu.c32`\r\n\r\n==> Is there any possibility to label the USB Stick \"REAR-EFI\" right from the beginning ? \r\n==> What about the error messages when booting from the stick? What do I have to do to correct this? \r\n\r\n\r\n## Second attempt (creating ISO-file, excluding devices and directories)\r\nI changed the configuration as follows: \r\n`OUTPUT=ISO`\r\n`BACKUP=NETFS`\r\n`OUTPUT_URL=file:///media/usb1`\r\n`#OUTPUT_URL=file:///srv/dev-disk-by-label-OMVDisc/downloads` (this would not work)\r\n`BACKUP_URL=iso://`\r\nAn ISO-file containing the rescue system as well as the backup is successfully created and copied to the USB-Stick. Unetbootin refuses to work on my system because of a missing X-Server, so I copy the iso-file to a Windows-PC and restore the iso-file using Unetbootin for Windows (sic!) on an USB-Stick. \r\n\r\nThe so created USB-Stick boots successfully on the NAS using UEFI. \r\n\r\n==> The boot menu just contains the entries \"Rear without secure boot, Rear with secure boot, Exit, Reboot\", is this correct or is there something missing? \r\n==> I just want the content of the SSD to be included in the backup archive. The content of the two hard disks (forming the RAID1 device) should **not** be included neither the content of any connected USB-device. \r\nWhat do I have to use to achieve this? \r\n`EXCLUDE_RECREATE=( \"${EXCLUDE_RECREATE[@]}\" \"fs:/media/usb1\" )`\r\n`EXCLUDE_RECREATE=( \"${EXCLUDE_RECREATE[@]}\" \"/dev/sdc\" )`\r\nOr should I use `EXCLUDE_BACKUP=()` or `EXCLUDE_MOUNTPOINTS=()` or EXCLUDE_COMPONENTS or .... ? \r\n\r\nHow do I have to address in this context the two hard disks ? \r\nSeparated, something like \r\n`EXCLUDE_RECREATE=( \"${EXCLUDE_RECREATE[@]}\" \"/dev/sda\" \"/dev/sdb\" )`\r\nor the RAID1 as a whole: \r\n`EXCLUDE_RECREATE=( \"${EXCLUDE_RECREATE[@]}\" \"/srv/dev-disk-by-label-OMVDisc\" )` ? \r\n\r\n==> Directories of the SSD to  be cloned can be exluded using the following command, is this right ? \r\n`BACKUP_PROG_EXCLUDE=( \"${BACKUP_PROG_EXCLUDE[@]}\" '/reariso/*' )`\r\n\r\n## USBmount\r\nI didn't further investigate it, but is it possible that REAR interferes with USBmount ? The USB stick has to be unmounted to execute the `usr/sbin/rear -v mkrescue` command, but even after `umount /media/usb0` usbmount tries to mount it again, which confuses then REAR ?!?! \r\n"}}
{"actor":{"display_login":"malvinas2"}}