Page 1 of 4 123 ... LastLast
Results 1 to 10 of 34

Thread: Setup hosed after update. can not boot into server at all

  1. #1
    Join Date
    Sep 2013
    Location
    New York
    Posts
    198

    Question Setup hosed after update. can not boot into server at all

    Hi, here is my issue.

    I have an OpenSuse 13.1 LXDE setup as home server.
    running Xen 4.3 and Samba.
    I am using full BTRFS install.
    that is my system drive is 1T with "/" on BTRFS and Swap partitions on it.
    and second 1T drives holds my "/home" partition.
    booting from "/" partition directly. as far as i can see I have no "/boot" partition anywhere in sight. this is how the OpenSuse set it up on my last install couple of month ago. I was having issues with the drive back than so I got a 1T seagate or somthing and used that as main drive.
    I also have Data drives 1x2T drive with BTRFS
    and 2x3T with multidevice Raid 1 BTRFS partition
    all is mounted in fstab on boot as datashares 1 and 2

    Xen installed and running.
    Samba configured to share the data drives to all for full access.

    all was working fine until 2 days ago.
    I have been moving my media collections and other soft onto the server
    and setting up VMs

    Ubuntu Server for subnzb+sickbeard and others
    and Sophos UTM
    all was working no issues or anything.

    2 days ago I run zypper up. again did not see any issues with updates. no errors or anything strange.

    but after reboot the server never cam back up.

    it boots to POST
    hets to the balck screen where grub prompt usually displayed. you know welcome to grub2 etc. in top left corner, but now I only see a blinking curor there which hold for a sec or two than skips 2 lines down and sits there blinking. no further actions are visible. system is not ping able or reachable (I get there via IPMI so I can see the boot process but this luxury will be gone in the next week or two as I am replacing the MB for a newer one which does not have the IPMI option)

    can I recover from this?

    I booted the server from Recovery CD into XFACE and I can see the drives in Yast/Partitioner . what can I do?

    I need a noob kind of help as I never fixed anything like this before. I would simply reinstall the OS but I have too much stuff loaded there to just loose all.

    also can some one help me in setting up a recovery procedure to prevent this from happening again or ease the recovery.

    thanks.

  2. #2
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    4,029

    Default Re: Setup hosed after update. can not boot into server at all

    Quote Originally Posted by vl1969 View Post
    Hi, here is my issue.

    I have an OpenSuse 13.1 LXDE setup as home server.
    running Xen 4.3 and Samba.
    I am using full BTRFS install.
    that is my system drive is 1T with "/" on BTRFS and Swap partitions on it.
    and second 1T drives holds my "/home" partition.
    booting from "/" partition directly. as far as i can see I have no "/boot" partition anywhere in sight. this is how the OpenSuse set it up on my last install couple of month ago. I was having issues with the drive back than so I got a 1T seagate or somthing and used that as main drive.
    I also have Data drives 1x2T drive with BTRFS
    and 2x3T with multidevice Raid 1 BTRFS partition
    all is mounted in fstab on boot as datashares 1 and 2

    Xen installed and running.
    Samba configured to share the data drives to all for full access.

    all was working fine until 2 days ago.
    I have been moving my media collections and other soft onto the server
    and setting up VMs

    Ubuntu Server for subnzb+sickbeard and others
    and Sophos UTM
    all was working no issues or anything.

    2 days ago I run zypper up. again did not see any issues with updates. no errors or anything strange.

    but after reboot the server never cam back up.

    it boots to POST
    hets to the balck screen where grub prompt usually displayed. you know welcome to grub2 etc. in top left corner, but now I only see a blinking curor there which hold for a sec or two than skips 2 lines down and sits there blinking. no further actions are visible. system is not ping able or reachable (I get there via IPMI so I can see the boot process but this luxury will be gone in the next week or two as I am replacing the MB for a newer one which does not have the IPMI option)

    can I recover from this?

    I booted the server from Recovery CD into XFACE and I can see the drives in Yast/Partitioner . what can I do?

    I need a noob kind of help as I never fixed anything like this before. I would simply reinstall the OS but I have too much stuff loaded there to just loose all.

    also can some one help me in setting up a recovery procedure to prevent this from happening again or ease the recovery.

    thanks.
    Boot from the recovery CD again, drop to a terminal, and give me the output of:
    Code:
    fdisk -l
    Note that that is a lower case L, not a numeral 1.

    You may already know this, but just in case:

    To do that, while in the terminal, sweep and choose the output with your mouse cursor, including the command you issued (ie: All terminal output), then Ctrl-Shift-C will copy it to your clipboard.

    Then post it in a message here. To do that, start your message, then at the upper right side of the forum message editor, right side of the middle row, click on the # sign. That will give you Code tags, with your cursor blinking in between them. Paste the contents of your clipboard there (Ctrl-V).

    We will continue from there.
    "Take a Walk on a Sunny Day, Greet everyone along the way, and Make Somebody Smile, Today"
    Gerry Jack Macks"Walk On A Sunny Day" GerryJackMacks.net

  3. #3
    Join Date
    Sep 2013
    Location
    New York
    Posts
    198

    Default Re: Setup hosed after update. can not boot into server at all

    will try to do it tonight thanks.

  4. #4
    Join Date
    Sep 2013
    Location
    New York
    Posts
    198

    Default Re: Setup hosed after update. can not boot into server at all

    here is the output of fdisdk-l

    as far as I can tell

    /dev/sda is the rescue CD
    /dev/sdb and /dev/sdc are my 3T drives that should be BTRFS RAID 1 volume

    /dev/sdd is my 2T BTRFS disk


    /dev/sde
    and /dev/sdf are the system disks one for /home and one for for "/"


    looking in gparted sde is my boot "/" disk
    and sdf is my /home disk
    strangly enought both disks have swap partion on it.
    I think I defined one on both , can't remeber now
    but sde1 is shown as btrfs with boot/legacy boot flags on it.

    Code:
      linux@linux:~> sulinux:/home/linux # fdisk -l
    
    
    Disk /dev/sda: 2102 MB, 2102394880 bytes, 4106240 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: 0xa19f8ba9
    
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1            4084       12275        4096   ef  EFI (FAT-12/16/32)
    /dev/sda2   *       12276     1232895      610310   83  Linux
    /dev/sda3         1232896     4104192     1435648+  83  Linux
    
    
    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: dos
    Disk identifier: 0x00000000
    
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb4               1           1           0+  ee  GPT
    Partition 4 does not start on physical sector boundary.
    
    
    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: dos
    Disk identifier: 0x00000000
    
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdc4               1           1           0+  ee  GPT
    Partition 4 does not start on physical sector boundary.
    
    
    Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes, 3907029168 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: 0x00000000
    
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdd1            2048  3907028991  1953513472   83  Linux
    /dev/sdd4               1           1           0+  ee  GPT
    
    
    Partition table entries are not in disk order
    
    
    Disk /dev/sde: 1000.2 GB, 1000204886016 bytes, 1953525168 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: dos
    Disk identifier: 0x00000000
    
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sde1   *        2048  1743808511   871903232   83  Linux
    /dev/sde2      1743808512  1953523711   104857600   82  Linux swap / Solaris
    /dev/sde4               1           1           0+  ee  GPT
    Partition 4 does not start on physical sector boundary.
    
    
    Partition table entries are not in disk order
    
    
    Disk /dev/sdf: 1000.2 GB, 1000204886016 bytes, 1953525168 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: 0x00000000
    
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdf1            2048  1743808511   871903232   83  Linux
    /dev/sdf2      1743808512  1953523711   104857600   83  Linux
    /dev/sdf4               1           1           0+  ee  GPT
    
    
    Partition table entries are not in disk order
    linux:/home/linux #

  5. #5
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    4,029

    Default Re: Setup hosed after update. can not boot into server at all

    At first glance:

    sdf1 appears to be a mirror of sde1

    sdf2 appears to be a mirror of sde2

    It is odd for a CD/DVD drive to be sd*, it is normally sr*

    I need to study this a bit more and think on it. But, in the meantime, maybe someone else might spot something significant.
    "Take a Walk on a Sunny Day, Greet everyone along the way, and Make Somebody Smile, Today"
    Gerry Jack Macks"Walk On A Sunny Day" GerryJackMacks.net

  6. #6
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    4,029

    Default Re: Setup hosed after update. can not boot into server at all

    Recovery disk again.

    Code:
    cd /media
    mkdir sde1
    mkdir sdf1
    mkdir sde2
    mkdir sdf2
    Then:
    Code:
    mount /dev/sde1 /media/sde1
    mount /dev/sdf1 /media/sdf1
    mount /dev/sde2 /media/sde2
    mount /dev/sdf2 /media/sdf2
    Then:
    Code:
    ls -l sde1
    ls -l sdf1
    ls -l sde2
    ls -l sdf2
    and post the output here.

    Then,
    Code:
    umount sde1
    umount sdf1
    umount sde2
    umount sdf2
    shutdown now
    "Take a Walk on a Sunny Day, Greet everyone along the way, and Make Somebody Smile, Today"
    Gerry Jack Macks"Walk On A Sunny Day" GerryJackMacks.net

  7. #7

    Default Re: Setup hosed after update. can not boot into server at all

    Quote Originally Posted by Fraser_Bell View Post
    It is odd for a CD/DVD drive to be sd*, it is normally sr*
    Probably he booted the Live system from an USB stick or similar.
    That would indeed show up as /dev/sd*.

    To the original problem, it seems that the BIOS just cannot find/load grub, as not even the boot menu shows up IIUIC.

    As a first try I would just re-install the boot loader (to the MBR) and see if it boots then:
    Boot to the rescue system and do the following:
    Code:
    mount /dev/sde1 /mnt
    mount --bind /dev /mnt/dev
    chroot /mnt
    mount -t proc proc /proc
    mount -t sysfs sysfs /sys
    grub2-mkconfig -o /boot/grub2/grub.cfg
    grub2-install /dev/sdb
    But check first (in the BIOS) which hard disk is actually the first one in your boot order, and use that instead of /dev/sdb in the last line.
    Maybe just changing the boot order (to boot from sde I suppose) would help already, though?

  8. #8
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    4,029

    Default Re: Setup hosed after update. can not boot into server at all

    Quote Originally Posted by wolfi323 View Post
    Probably he booted the Live system from an USB stick or similar.
    That would indeed show up as /dev/sd*.
    I was thinking that since, too.

    To the original problem, it seems that the BIOS just cannot find/load grub, as not even the boot menu shows up IIUIC.

    As a first try I would just re-install the boot loader (to the MBR) and see if it boots then:
    Boot to the rescue system and do the following:
    Code:
    mount /dev/sde1 /mnt
    mount --bind /dev /mnt/dev
    chroot /mnt
    mount -t proc proc /proc
    mount -t sysfs sysfs /sys
    grub2-mkconfig -o /boot/grub2/grub.cfg
    grub2-install /dev/sdb
    But check first (in the BIOS) which hard disk is actually the first one in your boot order, and use that instead of /dev/sdb in the last line.
    Maybe just changing the boot order (to boot from sde I suppose) would help already, though?
    Thanks, Wolfi. You have confirmed what I was thinking, as well. I first want to make certain which is his / partition, then I was thinking of getting Grub re-installed, but also run mkintrd just for certainty.

    And, yes, I was going to suggest putting the disk with the / partition as the first boot disk in the BIOS boot order (which we think is sde, but not certain at this point).

    Therefore, instead of installing Grub to sdb, he would install Grub to sde, correct?

    But, before trying any of that, perhaps he should try first to just change the boot order and see if that is all there is to it, since at this time we are not certain which disk has Grub installed nor if it is MBR or a partition.

    I appreciate your help, here.
    "Take a Walk on a Sunny Day, Greet everyone along the way, and Make Somebody Smile, Today"
    Gerry Jack Macks"Walk On A Sunny Day" GerryJackMacks.net

  9. #9

    Default Re: Setup hosed after update. can not boot into server at all

    Quote Originally Posted by Fraser_Bell View Post
    And, yes, I was going to suggest putting the disk with the / partition as the first boot disk in the BIOS boot order (which we think is sde, but not certain at this point).

    Therefore, instead of installing Grub to sdb, he would install Grub to sde, correct?
    Yes, if sde is first in the boot order, i.e. the boot code is loaded from it, he should install grub to sde.

    But, before trying any of that, perhaps he should try first to just change the boot order and see if that is all there is to it, since at this time we are not certain which disk has Grub installed nor if it is MBR or a partition.
    Yes, and we have no idea from which disk his BIOS loads the boot code. And that is what's going wrong apparently.

    The BIOS does not much more than load the MBR from one disk and calls the code there.

    A generic boot loader would then look for the active partition and call the boot sector there. If it doesn't find it (because of the particular disk layout f.e.), there should be an error message, not just a blinking cursor.

    And if grub couldn't load its files you would get the GRUB> prompt.

    So the most likely reason here that I can imagine is that the BIOS boots from an MBR that doesn't actually contain _any_ boot code.

  10. #10
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    4,029

    Default Re: Setup hosed after update. can not boot into server at all

    Quote Originally Posted by wolfi323 View Post
    Yes, if sde is first in the boot order, i.e. the boot code is loaded from it, he should install grub to sde.


    Yes, and we have no idea from which disk his BIOS loads the boot code. And that is what's going wrong apparently.

    The BIOS does not much more than load the MBR from one disk and calls the code there.

    A generic boot loader would then look for the active partition and call the boot sector there. If it doesn't find it (because of the particular disk layout f.e.), there should be an error message, not just a blinking cursor.

    And if grub couldn't load its files you would get the GRUB> prompt.

    So the most likely reason here that I can imagine is that the BIOS boots from an MBR that doesn't actually contain _any_ boot code.
    I agree that is the most likely reason. I have the feeling BIOS is trying to boot from one of the RAID volumes.

    But, I have also seen exactly the same response he is reporting when Grub is installed to the root partition and the root partition is not marked with the Boot flag.
    "Take a Walk on a Sunny Day, Greet everyone along the way, and Make Somebody Smile, Today"
    Gerry Jack Macks"Walk On A Sunny Day" GerryJackMacks.net

Page 1 of 4 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •