New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with 1TB SanDisk USB driver rear - v mkrescue #2713
Comments
I changed a lot for output=USB the last 1-2 month so the version from 21 Apr is a bit on the old side. Try using a newer master version please - your issue may have been fixed. |
@epaiser Try the deb package from http://download.opensuse.org/repositories/Archiving:/Backup:/Rear:/Snapshot/xUbuntu_18.04/amd64/ which was build this week. This contains the updated USB format code. |
The latest version solve the problem I have.
But it didn't to work to save the system and restore to a different
machine with different hardware (Supermicro -> ASUS Motherboard).
I will investigate more.
Thank you anyway!!
…On 11/17/2021 2:35 AM, A. Binzxxxxxx wrote:
I changed a lot for output=USB the last 1-2 month so the version from 21
Apr is a bit on the old side. Try using a newer master version please -
your issue may have been fixed.
For the older version the |--efi | in format is correct.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2713 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWQKS2N3STX4EAVCLZTCPCDUMOAQZANCNFSM5IC7ZCOA>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Ernesto Paiser - Senior Controls Engineer
Sigray, Inc.
5750 Imhoff Dr, Concord, CA 94520
United States
***@***.*** ***@***.***>
+1-650-503-3410
--
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error, please notify the
system manager. This message contains confidential information and is
intended only for the individual named. If you are not the named addressee,
you should not disseminate, distribute or copy this email. Please notify
the sender immediately by email if you have received this email by mistake
and delete this email from your system. If you are not the intended
recipient, you are notified that disclosing, copying, distributing or
taking any action in reliance on the contents of this information is
strictly prohibited
|
@epaiser Did you already try to add |
so the recreating on different hardware failure has a different cause. @epaiser E.g. I think it cannot "just work" to switch from a SATA disk to a NVMe disk |
I guess the issue is meanwhile sufficiently solved |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.6-git.4317.be8b6ed.master / 2021-04-21
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
Supermicro:
Product Name: SYS-7049A-T
Product Name: X11DAi-N
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86_64
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
NVMe 256GB
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT"):
When doing:
"rear format /dev/sdd", then "rear -v mkrescue", got:
Then:
After doing:
"rear format -- --efi /dev/sdd ; rear -v mkrescue"
Workaround, if any:
None
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
To paste verbatim text like command output or file content,
include it between a leading and a closing line of three backticks like
The text was updated successfully, but these errors were encountered: