So I had my system boot drive set to a USB drive that resides inside my server on the motherboard. Bare Metal sees this drive and I accidently initiated it which effectively wiped all the boot files.... Any advise on how to go about restoring things the way they were before this issue?
On a side note, I think Bare Metal should provide a description and size of the USB drive that it detects to prevent others from running into this issue.
Thank you anyone that can assist.
On a side note, I think Bare Metal should provide a description and size of the USB drive that it detects to prevent others from running into this issue.
Thank you anyone that can assist.
Share this post:
Responses (5)
-
Accepted Answer
Missed your UUID question. You can try. The new one is not a valid UUID but you have nothing to lose. You can always roll back the changes. The only thing for me is it may confuse initramfs.
I don't think you can set a specific UUID but you can generate a new one. Here is one link.
Note conventional wisdom says you take an exact copy of your USB drive with something like dd, then you perform your recovery on the copy. -
Accepted Answer
-
Accepted Answer
Can I just update fstab from the below UUID=8b4f7f26-5c0d-4ebb-9590-3ba6b56b1182 (which I believe is the previous USB boot disk) to the Disk identifier: 0x0004b331 (the USB boot disk) seen below and is the identifier of sdd? Or is it that I am missing the partition on the disk ssd which would hold the UUID as shown in the fstab?
UUID=8b4f7f26-5c0d-4ebb-9590-3ba6b56b1182 /boot xfs defaults 0 0
to:
UUID=0x0004b331 /boot xfs defaults 0 0
Considering Disk /dev/sdd: 3965 MB, 3965190144 bytes, 7744512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0004b331
Output of fdisk -l /dev/sdd
Disk /dev/sdd: 3965 MB, 3965190144 bytes, 7744512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0004b331
Device Boot Start End Blocks Id System
/dev/sdd1 * 62 7744511 3872225 83 Linux
Output of df -Th
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/clearos-root xfs 5.0G 3.6G 1.5G 72% /
devtmpfs devtmpfs 7.9G 4.0K 7.9G 1% /dev
tmpfs tmpfs 7.9G 68K 7.9G 1% /dev/shm
tmpfs tmpfs 7.9G 815M 7.1G 11% /run
tmpfs tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
/dev/mapper/clearos-home xfs 3.0T 1.2T 1.8T 41% /home
/dev/mapper/clearos-var xfs 20G 9.1G 11G 46% /var
/dev/mapper/clearos-log xfs 8.0G 1.3G 6.7G 16% /var/log
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/991
/dev/sda1 ext4 4.4T 89M 4.2T 1% /mnt/usb_bkup [/dev/sda1 to the left was an old USB drive]
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/0 -
Accepted Answer
I attempted to install grub2 to disk sdd.
Using webmin, here is the structure of directories on the USB drive:
/ mnt / usb / boot / grub2 / grubenv (file)
/ mnt / usb / boot / grub2 / fonts (directory)
/ mnt / usb / boot / grub2 / i386-pc (directory)
/ mnt / usb / boot / grub2 / locale (directory)
I navigated to /boot so see what was there...
dir /boot -l:
total 194776
-rw-r--r-- 1 root root 141116 Jan 5 05:46 config-3.10.0-693.11.6.v7.x86_64
-rw-r--r-- 1 root root 141099 Sep 17 17:24 config-3.10.0-693.2.2.v7.x86_64
-rw------- 1 root root 49089662 May 4 2017 initramfs-0-rescue-346b58d8bb4542eeae3a0b91d86457e9.img
-rw------- 1 root root 20547783 Mar 27 2017 initramfs-3.10.0-327.36.1.v7.x86_64.img
-rw------- 1 root root 20548525 Mar 27 2017 initramfs-3.10.0-327.36.2.v7.x86_64.img
-rw------- 1 root root 20543336 Mar 27 2017 initramfs-3.10.0-327.36.3.v7.x86_64.img
-rw------- 1 root root 21150984 Jan 24 04:56 initramfs-3.10.0-514.26.2.v7.x86_64.img
-rw------- 1 root root 21213129 Jan 8 06:02 initramfs-3.10.0-693.11.6.v7.x86_64.img
-rw------- 1 root root 21217721 Dec 22 15:27 initramfs-3.10.0-693.2.2.v7.x86_64.img
-rw-r--r-- 1 root root 613827 Mar 27 2017 initrd-plymouth.img
-rw-r--r-- 1 root root 293151 Jan 5 05:50 symvers-3.10.0-693.11.6.v7.x86_64.gz
-rw-r--r-- 1 root root 293128 Sep 17 17:28 symvers-3.10.0-693.2.2.v7.x86_64.gz
-rw------- 1 root root 3233751 Jan 5 05:46 System.map-3.10.0-693.11.6.v7.x86_64
-rw------- 1 root root 3230113 Sep 17 17:24 System.map-3.10.0-693.2.2.v7.x86_64
-rwxr-xr-x 1 root root 5395904 May 4 2017 vmlinuz-0-rescue-346b58d8bb4542eeae3a0b91d86457e9
-rwxr-xr-x 1 root root 5889808 Jan 5 05:46 vmlinuz-3.10.0-693.11.6.v7.x86_64
-rwxr-xr-x 1 root root 5878576 Sep 17 17:24 vmlinuz-3.10.0-693.2.2.v7.x86_64 -
Accepted Answer
A bit more information. The system is a RAID 10 with 4 3000.6GB drives (sdb, sdc, sde, sdf), sdg is a 6TB usb drive that I was trying to get working with BareMetal Backup, and the USB boot disk is sdd.
The USB drive that is designated for boot details:
Disk /dev/sdd: 3965 MB, 3965190144 bytes, 7744512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0004b331
Fstab:
/dev/mapper/clearos-root / xfs defaults 0 0
UUID=8b4f7f26-5c0d-4ebb-9590-3ba6b56b1182 /boot xfs defaults 0 0
/dev/mapper/clearos-home /home xfs defaults 0 0
/dev/mapper/clearos-var /var xfs defaults 0 0
/dev/mapper/clearos-log /var/log xfs defaults 0 0
/dev/mapper/clearos-swap swap swap defaults 0 0
fdisk -l:
WARNING: fdisk GPT support is currently new, and therefore in an experimental ph ase. Use at your own discretion.
Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: gpt
Disk identifier: DA670368-CE76-4F9E-9F45-85690C453B3E
# Start End Size Type Name
1 2048 5860532223 2.7T Linux RAID
WARNING: fdisk GPT support is currently new, and therefore in an experimental ph ase. Use at your own discretion.
Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: gpt
Disk identifier: D269EC7E-9B34-4E08-A648-7E38A4F51D38
# Start End Size Type Name
1 2048 5860532223 2.7T Linux RAID
Disk /dev/sdd: 3965 MB, 3965190144 bytes, 7744512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0004b331
Device Boot Start End Blocks Id System
/dev/sdd1 * 62 7744511 3872225 83 Linux
WARNING: fdisk GPT support is currently new, and therefore in an experimental ph ase. Use at your own discretion.
Disk /dev/sde: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: gpt
Disk identifier: 4A2B2617-2142-4675-9702-388EA0DB172A
# Start End Size Type Name
1 2048 5860532223 2.7T Linux RAID
WARNING: fdisk GPT support is currently new, and therefore in an experimental ph ase. Use at your own discretion.
Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: gpt
Disk identifier: 7A55BF9F-C924-4A77-B399-386ED2B01DFE
# Start End Size Type Name
1 2048 5860532223 2.7T Linux RAID
Disk /dev/md127: 6000.9 GB, 6000914464768 bytes, 11720536064 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk /dev/mapper/clearos-root: 5356 MB, 5356126208 bytes, 10461184 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk /dev/mapper/clearos-swap: 2063 MB, 2063597568 bytes, 4030464 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk /dev/mapper/clearos-var: 21.4 GB, 21390950400 bytes, 41779200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk /dev/mapper/clearos-log: 8506 MB, 8506048512 bytes, 16613376 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk /dev/mapper/clearos-home: 3221.1 GB, 3221141585920 bytes, 6291292160 sector s
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
WARNING: fdisk GPT support is currently new, and therefore in an experimental ph ase. Use at your own discretion.
Disk /dev/sdg: 6001.2 GB, 6001175125504 bytes, 11721045167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disk label type: gpt
Disk identifier: 872A9B35-9548-4014-B6AD-4A9C87B3AF8E
# Start End Size Type Name
1 34 262177 128M Microsoft reser Microsoft reserved partiti on
Partition 1 does not start on physical sector boundary.
2 264192 11721043967 5.5T Microsoft basic Basic data partition
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »