![]() ![]() I am still curious about the original questions I had - namely, 1. I think my previous attempts to boot by specifying UUID failed for one of various reasons (GRUB not being installed, typos in the UUID, etc). I discovered that the partition with the correct UUID was actually mounted to /dev/sdb2 for some reason! Using root=/dev/sdb2 I booted the system just fine. However, neither of these worked, and both dropped me into a strange command line. I had tried both linux /boot/vmlinuz-linux root=/dev/sda2 and linux /boot/vmlinuz-linux root=/dev/sdc2 to no avail - the first because the drive was showing up as (hd0,gpt2) in grub, and the second because the partition gets labeled as /dev/sdc2 when I boot normally. The exact command I use in grub while attempting to boot is set root=(hd0,gpt2) It doesn't copy the entire disk over like dd, so for example while installing grub I still need to manually create a partition with the bios_grub flag. I created my external backup using Borg, which creates a copy of all the files. ![]() This error also appeared on two separate external HD docks, so I assume it is not a hardware issue. Perhaps because it is a usb connected external HD, do I need to do anything special? I noticed seeing the error usb 2-4: device descriptor read/64, error -71 while booting normally, but since this has no apparent effect on the functionality of the drive, I ignored it. (I did modify /etc/fstab on the external drive so that the drive with the UUID of the root partition should be mounted to /, but to no avail) etc/fstab? Is this something I need to change in order to make sure that root is found? And does it matter whether I change the /etc/fstab file on my internal drive or on the external one. This happens even when I specify root by device uuid. Perhaps the difficulties I'm having are related to just my first question, but when I boot after specifying linux /boot/vmlinuz-linux root=/dev/sda2, I always get some failure relating to the drive specified as root not being found. I found that when using GRUB command line without GRUB installed on my external drive, the external drive was shown as (hd2,gpt1), however after I installed GRUB on the external drive, it came up as (hd0,gpt2).So my question is, is GRUB being loaded from my normal boot drive or from the external drive, and does it matter? This happens whether I manually went and installed GRUB on my external HD or not. However, whether I select this device or my usual drive as the boot device, I am shown the same GRUB menu. In what I assume is the BIOS, I select my external HD as the boot device. However, this is proving a bit more difficult than I expected. To test whether this backup works, i'm trying to boot from it. I have a copy of all the files under / on an external usb-connected harddrive. Repositories with rotated drives are not supported as archive repositories for NAS backup.Edit: I think I solved my own problem - see bottom of question for details.Hardened repositories do not support rotated drives.If you enable the This repository is backed by rotated hard drives setting on an extent, Veeam Backup & Replication will ignore this setting and will work with such repository as with a standard extent. Scale-out backup repositories do not support rotated drives.If you enable the This repository is backed by rotated hard drives setting on the repository, Veeam Backup & Replication will ignore this setting. NFS backup repositories do not support rotated drives.You cannot rescan backup repositories with rotated drives. ![]() You cannot store archive full backups (GFS backups) created with backup jobs or backup copy jobs in backup repositories with rotated drives.On one managed server, you must create only one repository with rotated drives.Limitations for Backup Repositories with Rotated Drivesīackup repositories with rotated drives have the following limitations: When this option is enabled, Veeam Backup & Replication recognizes the backup target as a backup repository with rotated drives and uses a specific algorithm to make sure that the backup chain created on these drives is not broken. To use rotated drives, you must enable the This repository is backed by rotated hard drives option in the advanced settings of the backup repository. This scenario can be helpful if you want to store backups on several external hard drives that you plan to regularly move between different locations. Rotated drives can be detachable USB or eSATA hard drives. A backup repository can use rotated drives. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |