Profile Details

Toggle Sidebar
Recent updates
  • Tony Ellis wrote:

    On the documentation front find the CentOS and Red Hat Customer Portal (free)sites very useful... OK I see what you did with the USB drive, hmm...

    To ensure the maximum chances for recovery - keep things very simple here and minimize the number of "points of failure"...

    LVM - unless you intend to grow/resize partitions in the future - it's just an added layer of complication that makes recovery harder. Don't use here...

    RAID and boot drive - Again keep this simple here... If using RAID - then RAID 1 with Version 0.9 - grub on both drives. The beauty of this is that you can see the contents of each drive with no RAID drivers at all with any linux distribution that supports the file-system (ext4 xfs etc).

    Lately with Professional Quality small SSD drives being inexpensive have started just putting the system on an SSD and data on RAID 6 spinning drives. RAID 6 can be grown, then grow the fs - so no requirement for LVM. All things such as configuration files, vital var partition data (eg mail) etc are backed up onto a different system...


    Tony, I reinstalled the system already but I do like your recommendations... I may actually go back and re-install once again based on your recommendation.

    Question, with re to the adding of grub to both drives... are you manually partitioning the drives in the RAID or are you letting the installation partition for you? I found that allowing the installation to partition the biosboot partition it only partitions one of the drives in the raid. This is the situation I am in right now... only one of the drives in the RAID has the biosboot and I need to figure out how to mirror the biosboot to all the drives in the RAID so that if anyone of them fail then the system will still boot (I elected not to use the usb drive for the boot as I have previously done) . See attached image of my fdisk. I am thinking I can create the 2 missing partitions on the other 3 drives then dd the contents of these boot partitions to the newly created partitions. Make sense? Is this the way I should do this?

    Thanks again for your help!

  • Nick Howitt wrote:

    I've no idea if this will help - SuperGRUB2. I also bumped into this blog. I guess you've searched the internet so there is little point in me searching as well. I don't particularly know GRUB2 and have no experience of RAID and, I would guess you are using LVN as well.


    Thanks Nick... I tried SuperGRUB2 and no luck... It has something to do with Grub not seeing the Raid - I see all the individual drives in the raid from the Grub command prompt GRUB > ls....

    I resorted to reinstall....

  • Tony Ellis wrote:

    It is not clear what exactly your USB boot drive contained. Was it just /boot - or was it the entire operating system and the RAID 10 is just a data drive?
    Grub2 is not your only concern - you will also need to build an initramfs with all the correct drivers including those for your disk controllers, the mdadm drivers and a correct mdadm configuration file.


    Tony, the USB drive was the designated boot MBR drive that was used to load the OS which is on a RAID 10 software configuration.

    I cannot believe there is such a lack of documentation on this or maybe I am not searching in the right places... seems as if I should be able to use a rescue disk to fully load the OS but that has not happened....

    I am resorting to reinstalling an out of the box ClearOS install back to a RAID 10 and then loading grub to all drives so that if one fails the system will still boot. This was the reason that I elected to use a USB drive for the boot drive as one of the drives in the RAID failed previously - this drive happened to hold the boot and the OS could not load so I had to reinstall.

    Guess this is what is meant by 3rd time's a charm.

  • Stuck at Grub Prompt - Grub not seeing Raid10 MD127

    Stuck at Grub Prompt on boot...

    I accidentally overwrote my usb boot drive - this was the only drive that booted into the Raid 10 ClearOS 7.4. The raid is software through the clearos install. During install I elected to install the boot to the usb drive only.

    I have tried all last night and all today to get Grub2 to recognize the RAID using the rescue disk but just do not know enough about it and am beat down to the point of about to reinstall but would prefer to not have to reconfigure everything... I do have everything backed up (home; var/usr, etc.) so that is the good news.

    I am sure this is a simple fix through adjusting some of the GRUB config files and / or fstab. Anyone able to assist by pointing me in the right direction?

    Let me know.

    Thanks,
    Al

  • 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

  • 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

  • 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

  • Accidentally Overwrote System USB Boot Drive

    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.

  • Al Catoe
    Al Catoe unlocked the badge Bookworm
    Bookworm
    Loves reading the forums.
  • How to remove "Ready" Detected USB-Storage Devices

    Guys I need some help please - paying customer here...

    I accidentally selected my 3GB usb boot (grub) drive thinking it was my large 5TB usb drive.... This is because BM does not show my 5TB usb drive. How can I make BM not use my 3GB usb boot drive - meaning make this drive say NOT READY? I already uninstalled and reinstalled BM and it still says "READY".

    I need to know how to make sure my system will boot from this 3GB usb boot drive again... any commands to use to ensure this? The 3GB usb boot drive is /dev/sdd1.

    I also need to know how I can make BM see my 5TB usb drive so I can use it. This drive is /dev/sda.

    Any help would be greatly appreciated before my system reboots unexpectedly.