#StackBounty: #boot #grub2 #system-installation #boot-repair #startup-disk-creator Stuck in a rabbit hole of Ubuntu install problems

Bounty: 50

I’m trying to install Ubuntu overwriting Windows on a Lenovo ideapad 320 (151IAP). I’m booting off a usb stick created using startup disk creator and an 18.04 image.

This will be a long post, because I’ve tried quite a few different things, but my hypothesis was that I have a working install of ubuntu and I just need to get it to boot properly; I’m not so sure that’s the case anymore. Here is my latest boot-repair output.

Update: I tried booting from grub using these instructions and got errors “can’t find /root in /etc/fstab” and “mounting /dev on /root/dev failed: No such file or directory” and same with run. Also, I saw that the /home/dustan/ directory is empty. I’m not really sure how the directory system is supposed to look after a proper install, so correct me if I’m wrong: this seems to me to be evidence against my hypothesis that I only need to repair grub. I tried making the usb stick using mkusb instead of the default startup disk creator; it still hangs on installing grub.

Here’s the full story:

The first problem I ran into was the installer hanging on “configuring hardware”. I eventually figured out how to disable secure boot and fast boot, per the advice given here, and the installer no longer hangs there.

Instead it hangs at Grub2, so I followed the advice given here (after several failed attempts) to specify the Ubuntu partition (sda2) separate from the boot partition (sda1). It still hung on Grub2 (didn’t bypass it, so I’m not really sure what that answer was actually getting at).

In both the configuring hardware and the Grub2 hang cases, I have given the computer literally hours to install properly.

When I look at the log in the installer, it shows repeated instances of “invalid report id data”, associated to using the touchpad. There is indeed a known problem with this touchpad and Ubuntu’s drivers, but the touchpad has been working in spite of these errors, and I figure if I can ever actually get Ubuntu working I can likely deal with the driver problem later. And unfortunately these errors are probably obscuring any actual crippling errors.

So after many attempts to get that to work properly, I finally decided to attempt to repair Grub.

Before I list boot-repair errors, I forgot to mention another thing that I tried while installing in the midst of the above; once I figured out how to modify the boot line, I tried noacpi, nolapic, irqpoll, and noapic (I was somewhat using this as a reference, but I still had no idea what I was actually doing).

If I follow the recommended repair in boot-repair, it hangs without giving any feedback.

If I disable SecureBoot under advanced options in boot-repair and then run the recommended repair, it will set itself to purge grub, and then it says “Please open a terminal and type the following commands:”

sudo chroot "/mnt/boot-sav/sda2" dpkg --configure -a
sudo chroot "/mnt/boot-sav/sda2" apt-get install -fy
sudo chroot "/mnt/boot-sav/sda2" apt-get purge -y grub*-common grub-common:i386 shim-signed

Running the first command gives:

ubuntu@ubuntu:~$ sudo chroot "/mnt/boot-sav/sda2" dpkg --configure -a
Setting up grub-efi-amd64-signed (1.93+2.02-2ubuntu8) ...
Installing for x86_64-efi platform.
grub-install: error: efibootmgr failed to register the boot entry: Unknown error -1.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 grub-efi-amd64-signed
ubuntu@ubuntu:~$

I didn’t expect the second command to work, but I tried it anyway, and it hung after this:

ubuntu@ubuntu:~$ sudo chroot "/mnt/boot-sav/sda2" apt-get install -fy
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 43 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up grub-efi-amd64-signed (1.93+2.02-2ubuntu8) ...
Installing for x86_64-efi platform.

Trying the terminal method here,
the instructions for a separate boot partition are kind of vague, but here was my interpretation:

ubuntu@ubuntu:~$ sudo mkdir /mnt/ubuntu
ubuntu@ubuntu:~$ sudo mkdir /mnt/ubuntu/boot
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt/ubuntu/boot
ubuntu@ubuntu:~$ sudo grub-install --boot-directory=/mnt/ubuntu/boot /dev/sda
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
grub-install: error: will not proceed with blocklists.
ubuntu@ubuntu:~$ sudo umount /mnt/ubuntu/boot

Another terminal method.

ubuntu@ubuntu:~$ sudo mount /dev/sda2 /mnt
ubuntu@ubuntu:~$ sudo mount --bind /dev /mnt/dev && sudo mount --bind /dev/pts /mnt/dev/pts && sudo mount --bind /proc /mnt/proc && sudo mount --bind /sys /mnt/sys
ubuntu@ubuntu:~$ sudo chroot /mnt
root@ubuntu:/# grub-install /dev/sda
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
root@ubuntu:/# exit
exit
ubuntu@ubuntu:~$ sudo umount /mnt/sys && sudo umount /mnt/proc && sudo umount /mnt/dev/pts && sudo umount /mnt/dev && sudo umount /mnt

Trying again with sda1.

ubuntu@ubuntu:~$ sudo mount /dev/sda2 /mnt
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt/boot
ubuntu@ubuntu:~$ sudo mount --bind /dev /mnt/dev && sudo mount --bind /dev/pts /mnt/dev/pts && sudo mount --bind /proc /mnt/proc && sudo mount --bind /sys /mnt/sys
ubuntu@ubuntu:~$ sudo chroot /mnt
root@ubuntu:/# grub-install /dev/sda
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
root@ubuntu:/# exit
exit
ubuntu@ubuntu:~$ sudo umount /mnt/sys && sudo umount /mnt/proc && sudo umount /mnt/dev/pts && sudo umount /mnt/dev && sudo umount /mnt/boot && sudo umount /mnt

One more.

ubuntu@ubuntu:~$ sudo mount /dev/sda2 /mnt
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt/boot
ubuntu@ubuntu:~$ sudo mkdir -p /mnt/boot/efi
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt/boot/efi
ubuntu@ubuntu:~$ sudo mount --bind /dev /mnt/dev
ubuntu@ubuntu:~$ sudo mount --bind /proc /mnt/proc
ubuntu@ubuntu:~$ sudo mount --bind /sys /mnt/sys
ubuntu@ubuntu:~$ sudo chroot /mnt
root@ubuntu:/# apt-get install grub-efi-amd64
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. 
root@ubuntu:/# sudo dpkg --configure -a
Setting up grub-efi-amd64-signed (1.93+2.02-2ubuntu8) ...
Installing for x86_64-efi platform.
grub-install: error: efibootmgr failed to register the boot entry: Unknown error -1.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 grub-efi-amd64-signed
root@ubuntu:/# exit
exit
ubuntu@ubuntu:~$ sudo umount /mnt/dev
ubuntu@ubuntu:~$ sudo umount /mnt/proc
ubuntu@ubuntu:~$ sudo umount /mnt/sys
ubuntu@ubuntu:~$ sudo umount /mnt/boot/efi
ubuntu@ubuntu:~$ sudo umount /mnt/boot
ubuntu@ubuntu:~$ sudo umount /mnt


Get this bounty!!!

#StackBounty: #macos #boot #macbook-pro #reinstall Macbook Pro Late 2011 ran once but will not run again after reinstalling El Capitan OS

Bounty: 50

Over the weekend, I wiped my drive and reinstalled my Mac’s OS using the MacOS Utilities.

Everything went fine with the reinstall, I was able to run the new OS (El Capitan) and even download Chrome.

I closed the lid on my mac (while machine still on) and went to sleep. The next morning, I was not able to turn the machine on again.

At first, I thought it was the battery, so I charged the battery for 2 hours and tried again. Nothing. No sound, no chime, no indications of any kind that the machine is running or trying to run.

I did notice the breath light was solid, however, after I reset NVRAM and PRAM, the breath light went off. More importantly, the mac still wouldn’t turn on.

Not sure what’s going on, one day it was good and next day no life.

Please help!


Get this bounty!!!

#StackBounty: #arch-linux #mount #boot #usb #grub2 Virtualbox VMDK to bootable usb stick not working

Bounty: 50

I used VirtualBox to set up a small Arch Linux 64 bit x86 machine. Everything is running fine installed on the 8GB big virutal hard disk in the VMDK format.

cfdisk shows that I created two partitions:

  • Type: Primary, Type: Linux (ext4), Bootable, First Partition, Size: 7.5G
  • Type: Primary, Type: Swap, Solaris, Bootable, Second Partition, Size: 0.5G

I heavily customized Arch Linux and now want to make real bootable media out of it.

1. How could I create a bootable media without the complicated archiso installation process, but directly using a drive image that I create somehow?

In fact, I tried already creating my bootable media. I used Ubuntu to convert my os.vmdk to /dev/sdc using the command qemu-img convert os.vmdk -O raw /dev/sdc

Once completed, I rebooted to the PC’s boot menu but the pendrive was not showing up. I turned off secure boot and enabled Legace Boot Support. Nothing helped. Hence, I entered the Grub command line of my Ubuntu installation and entered

set root=(hd1,msdos2) # hd1 is my usb stick, msdos1 is swap, msdos2 is bootable
configfile /boot/grub/grub.cfg # in order to load the usb's grub

2. Some strange things happened then

  1. I put the stick into my laptop -> USB 2.0 port (I have got a USB 3.0 stick) -> Booting… -> Graphical Arch Linux Splash Screen -> Emergency Shell stating something like Can't run fsck. Error: Can't find drive with UUID=... (However, the UUID is absolutely correct. I changed that on Ubuntu and within Arch itself in /etc/fstab! When I do blkid on the emergency shell, the USB drive is simply not there. Instead I get my internal SSD on /dev/sda. I even do not find any usb drive in /dev/* and dmesg states nothing as well!)
  2. I put the stick into my laptop -> USB 3.0 port -> The grub command line is not detecting the drive. There is only hd0 but not hd1. However I sometimes boot from my external hard drive connected via usb 3 using the bios boot menu.
  3. I put the stick into my workstation PC on a USB 3.0 port -> Not in BIOS boot menu, started via grub and configfile command -> It booted whereas it did not boot on the USB 3.0 port on my laptop -> and then the same emergency shell as in 1.
  4. I put the stick into my workstation PC on a USB 2.0 port -> Started via GRUB -> It boots successfully without any issues.

I have no clue, what I should do!? I basically just want to make an image out of my existing virtual Arch Linux that I can transfer to any device by simply copying it without a complicated Arch install.

Any help is appreciated.


Get this bounty!!!

#StackBounty: #pi-3 #networking #boot #dhcp Issues with PXE boot with RPi 3B – no TFTP RRQ made

Bounty: 100

I’ve been running into issues trying to get a RPi 3B PXE booting – the Pi doesn’t appear to make any TFTP request once it receives a DHCP response, but instead remakes the BOOTP request. This might indicate that it thinks the response is invalid in some way?

I have a DHCP server on 192.168.2.1 (Kea DHCP), and a TFTP server on a different host (192.168.2.2). I can manually pull files from the TFTP server, and see that in the TFTP log. I’m aware that I’ve got to set option 60 to PXEClient, option 67 to the TFTP address and option 43 should contain Raspberry Pi Boot. Using dhcpdump -i eth0.2 -h b8:27:eb:bf:db:dd, this is the DHCP response being sent. Any obvious issues that would cause the Pi to reject it?

  TIME: 2018-04-03 18:10:15.501    
    IP: 0.0.0.0 (b8:27:eb:bf:db:dd) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)                                                                                                                                                                      
    OP: 1 (BOOTPREQUEST)          
 HTYPE: 1 (Ethernet)                  
  HLEN: 6                   
  HOPS: 0            
   XID: 26f30339                    
  SECS: 0             
 FLAGS: 0                  
CIADDR: 0.0.0.0           
YIADDR: 0.0.0.0           
SIADDR: 0.0.0.0                          
GIADDR: 0.0.0.0
CHADDR: b8:27:eb:bf:db:dd:00:00:00:00:00:00:00:00:00:00
 SNAME: .
 FNAME: .
OPTION:  53 (  1) DHCP message type         1 (DHCPDISCOVER)
OPTION:  55 ( 12) Parameter Request List     43 (Vendor specific info)
                                             60 (Vendor class identifier)
                                             67 (Bootfile name)
                                            128 (???)
                                            129 (???)
                                            130 (???)
                                            131 (???)
                                            132 (???)
                                            133 (???)
                                            134 (???)
                                            135 (???)
                                             66 (TFTP server name)

OPTION:  93 (  2) Client System             0000             ..
OPTION:  94 (  3) Client NDI                010201           ...
OPTION:  97 ( 17) UUID/GUID                 0044444444444444 .DDDDDDD
                                            4444444444444444 DDDDDDDD
                                            44               D
OPTION:  60 ( 32) Vendor class identifier   PXEClient:Arch:00000:UNDI:002001
---------------------------------------------------------------------------

  TIME: 2018-04-03 18:10:15.502
    IP: 192.168.2.1 (0:4:23:64:7d:c2) > 192.168.2.19 (b8:27:eb:bf:db:dd)
    OP: 2 (BOOTPREPLY)
 HTYPE: 1 (Ethernet)
  HLEN: 6
  HOPS: 0
   XID: 26f30339
  SECS: 0
 FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 192.168.2.19
SIADDR: 192.168.2.2
GIADDR: 0.0.0.0
CHADDR: b8:27:eb:bf:db:dd:00:00:00:00:00:00:00:00:00:00
 SNAME: .
 FNAME: .
OPTION:   1 (  4) Subnet mask               255.255.255.0
OPTION:   3 (  4) Routers                   192.168.2.1
OPTION:   6 (  4) DNS server                192.168.2.1
OPTION:  43 ( 20) Vendor specific info      0112526173706265 ..Raspbe
                                            7272792050692042 rry Pi B
                                            6f6f74ff         oot.
OPTION:  51 (  4) IP address leasetime      4000 (1h6m40s)
OPTION:  53 (  1) DHCP message type         2 (DHCPOFFER)
OPTION:  54 (  4) Server identifier         192.168.2.1
OPTION:  60 (  9) Vendor class identifier   PXEClient
OPTION:  66 ( 11) TFTP server name          192.168.2.2
OPTION:  67 ( 12) Bootfile name             bootcode.bin


Get this bounty!!!

#StackBounty: #16.04 #boot #grub2 #ubuntu-minimal Xenial LTS 16.04 Minimal – Can not get console to show with messages during boot up

Bounty: 50

I have new install of Xenial LTS 16.04 minimal(mini.iso)…which I installed bare min. system(no desktop, etc).

I would like boot messages…. a normal grub boot up with the console showing boot message. Instead, I just get a blank screen until it is done booting and I have to manually pull up a tty.

I modified my /etc/default/grub with:

root@laptop:/home/one# cat /etc/default/grub 
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="text"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

Ran update-grub, and verified what looks correct on /boot/grub/grub.cfg:

root@laptop:/home/one# cat /etc/default/grub 
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="text"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
root@laptop:/home/one# 
root@laptop:/home/one# mount /dev/sda1 /boot/
mount: /dev/sda1 is already mounted or /boot busy
       /dev/sda1 is already mounted on /boot
root@laptop:/home/one# mount /dev/sda1 /boot/^C
root@laptop:/home/one# cat /boot/grub/grub.cfg 
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function recordfail {
  set recordfail=1
  if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

terminal_input console
terminal_output console
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
    set gfxpayload="${1}"
    if [ "${1}" = "keep" ]; then
        set vt_handoff=vt.handoff=7
    else
        set vt_handoff=
    fi
}
if [ "${recordfail}" != 1 ]; then
  if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
      if [ ${match} = 0 ]; then
        set linux_gfx_mode=keep
      else
        set linux_gfx_mode=text
      fi
    else
      set linux_gfx_mode=text
    fi
  else
    set linux_gfx_mode=keep
  fi
else
  set linux_gfx_mode=text
fi
export linux_gfx_mode

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

but still not having success…no console and no console with messages during boot up.

Any ideas?


Get this bounty!!!

#StackBounty: #boot #cpu #motherboard #power-supply Breadboarded new build not starting – swapped everything

Bounty: 50

Ok, this is long and very puzzling. I’ve built a couple of systems and am a computer engineer so I thought I understood these things, but I am stumped at what to try next.

Short story: breadboarded brand new motherboard with brand new CPU does not POST, boot or beep. And I’ve tried everything, including replacing every component including PSU and clearing CMOS.

Long story:

It started with what supposed to be a high-end gaming rig. i7, water cooling, M2 etc. After putting everything together it didn’t boot up, so I started to remove components, even tried with a spare i5 I had. Fans spin up, MB LEDs light up, but no boot or POST.

Breadboarded (put only motherboard, CPU, fan and memory together outside of chassi) but still nothing. Attached a chassi speaker, but no beeps, not even without memory.

Returned motherboard (Asus Prime H270-PRO), came back with one bent pin fixed (but they couldn’t tell me if that was on the board or in the socket) but with “OK working” from them. They even upgrade BIOS.

Full of hope, put back the i7 (7700). Still the same, fan and LEDs turn on, but no boot, POST or beep. Swapped to the i5 (6500). Same thing.

Tried another PSU (from my day-to-day computer, so I know it’s working). Still the same.

Gave up, got another motherboard, and just to be sure, a brand new Celeron G3900, in case the two other CPUs got fried by the first board. Breadbording this motherboard directly with the Celeron, attached the ATX and CPU-power lines from my new PSU, outside of chassi.

NOTHING! Still not even a beep…

The new board is Gigabyte GA-Z270P-D3. It spins up the fan, rew’s it a few times, settles on a moderate speed for a few seconds, then turns off. Repeats this sequence over and over.

Tried my other, working, PSU, still same. Cleared CMOS, still the same.

So it seems like no combination of two motherboards, two PSUs and three CPUs doesn’t even get to POST…

Is it possible that the problem with the first motherboard (bent pin?) fried my to CPUs and broke the PSU so that it in turn broke the other motherboard?

I haven’t tried the i7 or i5 in the second mobo, since I’m afraid that they could damage this board if they are bad, I wouldn’t think so, but I’m starting to doubt my senses here.

Question 1: What does the cycling of the fan speed on the GA-270P indicate? Malfunctioning fan header? Tried one of the other original fans, so it isn’t that.

Question 2: So, is there a scenario where the two CPUs were fried by the bent pin (assuming it was in the CPU socket)? And could that have broken my new PSU so that it in turn broke also the new motherboard?

Question 3: Can I safely put one of the first CPUs in the second board without risking that board to go bad too (assuming it is not bad already)?

Question 4: Am I missing something else, really fundamental?


Get this bounty!!!

#StackBounty: #boot #dual-boot #grub2 #fstab How can I copy /home and / to new partitions on the same drive which I can boot into for t…

Bounty: 100

I’m running kubuntu 16.04. I messed up UEFI (long ago), so it boots without it, but my Windows 10 partition won’t boot. I don’t care about that at the moment.

root is 30GB on sda4 home is 50GB on sda5.

All that works fine.

I copied root to root2 and home to home2 using rsync. I want to use these new partitions to experiment with upgrading kubuntu while leaving my main system intact.

Later, I want to make another copy of root and home just for backup (in other partitions I have set aside) and I will want that to be bootable as well.

root2 is 30GB on sda6 and home2 is 50GB on sda7.

I modified /etc/fstab on root2 to reflect the new partition LABELs.

When I try to boot using root2 (from my grub menu), I get into an ash shell from busybox and have to reboot to get out of it, so I did something wrong in grub or Linux and it looks like it can’t find where or what to boot.

It displays some sort of traceback, but I don’t understand it and I don’t see it complaining about anything.

I asked almost the same question a few years ago, but never figured it out.

It was suggested in that question that I needed to chroot into the new root partition and run update-grub because I don’t have a separate boot partition. I gave that a quick try and found that I don’t know how to do that successfully.

What steps should I take to resolve this?


Details:

Root entry in grub (displayed by grub-customizer)

(This is the part that works as is.)

recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  a184c235-bbb7-4e0b-86ab-ab8f5d4a2941
else
  search --no-floppy --fs-uuid --set=root a184c235-bbb7-4e0b-86ab-ab8f5d4a2941
fi
        linux   /boot/vmlinuz-4.4.0-112-generic root=UUID=a184c235-bbb7-4e0b-86ab-ab8f5d4a2941 ro  quiet splash $vt_handoff
initrd  /boot/initrd.img-4.4.0-112-generic

/etc/fstab

bigbird@sananda:/etc$ cat fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda4 during installation
##UUID=a184c235-bbb7-4e0b-86ab-ab8f5d4a2941 /               ext4    errors=remount-ro 0       1
# /home was on /dev/sda5 during installation
##UUID=c81a6925-0631-484c-88d5-245e2e042652 /home           ext4    defaults        0       2
# swap was on /dev/sda10 during installation
##UUID=3ef9528c-1927-40fd-8729-33506d440101 none            swap    sw              0       0
## automount dataspace - JJP
##UUID=eb1774a1-2a44-4f03-8562-26b6339170f0 /media/dataspace  ext4    auto,rw,suid,exec,async,atime 0 1

LABEL=root /               ext4    errors=remount-ro 0       1
# /home was on /dev/sda5 during installation
LABEL=home /home           ext4    defaults        0       2
# swap was on /dev/sda10 during installation
UUID=3ef9528c-1927-40fd-8729-33506d440101 none            swap    sw              0       0
## automount dataspace - JJP
LABEL=dataspace /media/dataspace  ext4    auto,rw,suid,exec,async,atime 0 1

New stuff:

(I did a kernel update in root after I copied it to root2. That’s why the versions here are slightly older.
Once it boots, I’ll fix that.)

insmod part_gpt
insmod ext2
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6  caf3cb64-a51a-4298-bf34-5f97fa3b1308
else
  search --no-floppy --fs-uuid --set=root caf3cb64-a51a-4298-bf34-5f97fa3b1308
fi
linux /boot/vmlinuz-4.4.0-104-generic root=UUID=caf3cb64-a51a-4298-bf34-5f97fa3b1308 ro quiet splash $vt_handoff
initrd /boot/initrd.img-4.4.0-104-generic

/etc/fstab (on sda6)

bigbird@sananda:/media/work/etc$ cat fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / on /dev/sda6
##UUID=caf3cb64-a51a-4298-bf34-5f97fa3b1308 /               ext4    errors=remount-ro 0       1
# /home on /dev/sda7
##UUID=a75b6be1-5336-4eaf-92db-da1393b3d412 /home           ext4    defaults        0       2
# swap was on /dev/sda10 during installation
##UUID=3ef9528c-1927-40fd-8729-33506d440101 none            swap    sw              0       0
## automount dataspace - JJP
##UUID=eb1774a1-2a44-4f03-8562-26b6339170f0 /media/dataspace  ext4    auto,rw,suid,exec,async,atime 0 1

LABEL=root2 /               ext4    errors=remount-ro 0       1
# /home on /dev/sda7
LABEL=home2 /home           ext4    defaults        0       2
# swap was on /dev/sda10 during installation
UUID=3ef9528c-1927-40fd-8729-33506d440101 none            swap    sw              0       0
## automount dataspace - JJP
LABEL=dataspace /media/dataspace  ext4    auto,rw,suid,exec,async,atime 0 1
bigbird@sananda:/media/work/etc$

bigbird@sananda:~/pq$ ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 11 Jan 11 21:43 dataspace -> ../../sda12
lrwxrwxrwx 1 root root 10 Jan 11 21:43 ESP -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 11 21:43 home -> ../../sda5
lrwxrwxrwx 1 root root 10 Jan 11 21:43 home2 -> ../../sda7
lrwxrwxrwx 1 root root 10 Jan 11 21:43 home_bak -> ../../sda9
lrwxrwxrwx 1 root root 10 Jan 11 21:43 root -> ../../sda4
lrwxrwxrwx 1 root root 10 Jan 11 21:43 root2 -> ../../sda6
lrwxrwxrwx 1 root root 10 Jan 11 21:43 root_bak -> ../../sda8
lrwxrwxrwx 1 root root 11 Jan 11 21:43 winbak -> ../../sda11
lrwxrwxrwx 1 root root 10 Jan 11 21:43 Windows10 -> ../../sda3
bigbird@sananda:~/pq$

bigbird@sananda:~/pq$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 11 Jan 11 21:23 3ef9528c-1927-40fd-8729-33506d440101 -> ../../sda10
lrwxrwxrwx 1 root root 10 Jan 11 21:23 4630B96A30B9619B -> ../../sda3
lrwxrwxrwx 1 root root 10 Jan 11 21:23 52B7-E591 -> ../../sda1
lrwxrwxrwx 1 root root 11 Jan 11 21:23 7E8C3007301FA4AD -> ../../sda11
lrwxrwxrwx 1 root root 10 Jan 11 21:23 8f034ecf-5d98-4753-80d1-8099cf3bb641 -> ../../sda9
lrwxrwxrwx 1 root root 10 Jan 11 21:23 a184c235-bbb7-4e0b-86ab-ab8f5d4a2941 -> ../../sda4
lrwxrwxrwx 1 root root 10 Jan 11 21:23 a75b6be1-5336-4eaf-92db-da1393b3d412 -> ../../sda7
lrwxrwxrwx 1 root root 10 Jan 11 21:23 c81a6925-0631-484c-88d5-245e2e042652 -> ../../sda5
lrwxrwxrwx 1 root root 10 Jan 11 21:23 caf3cb64-a51a-4298-bf34-5f97fa3b1308 -> ../../sda6
lrwxrwxrwx 1 root root 10 Jan 11 21:23 cce6b9f2-1dcc-4a53-b15b-73c595c2f6f5 -> ../../sda8
lrwxrwxrwx 1 root root 11 Jan 11 21:23 eb1774a1-2a44-4f03-8562-26b6339170f0 -> ../../sda12


Get this bounty!!!

#StackBounty: #boot #dual-boot #opensuse #software-updates openSuse stuck in "start job" and won't finish booting

Bounty: 50

My openSuse Tumbleweed installation has somehow stopped booting at all. The startup process goes through normally, but then it says A start job is running for Hold until boot process finishes up (7 min / no limit) and that’s it. No matter how much I wait there seems to be no way for it to finish whatever it’s doing. Using Ctrl+Alt+F1 or any other combination only brings me to the same problem. The only thing that seems to work is the old REISUB key sequence to reboot the whole thing.

As asked here’s my hardware configuration:

  • ASUS PRIME X370-PRO motherboard with lastest BIOS update
  • Ryzen 5 1500X processor running at stock clock speed
  • Nvidia GTX 1060 3GB
  • Kingston HyperX 2133Mhz 8gb RAM memory

The Nvidia card is running the propietary software, which is working well pre-update (even though it was hard to get it running)

I’m on kernel version 4.15.0-1-default, which gets updated when I run sudo zypper dup.

EDIT: I’ve rolled back my installation to a point before updating the system (using snapper), and it works fine. Then I tried to update again, and it brought me to the same problem. What can I do besides leaving my system outdated?


Get this bounty!!!

#StackBounty: #boot #dual-boot #opensuse #software-updates openSuse stuck in "start job" and won't finish booting

Bounty: 50

My openSuse Tumbleweed installation has somehow stopped booting at all. The startup process goes through normally, but then it says A start job is running for Hold until boot process finishes up (7 min / no limit) and that’s it. No matter how much I wait there seems to be no way for it to finish whatever it’s doing. Using Ctrl+Alt+F1 or any other combination only brings me to the same problem. The only thing that seems to work is the old REISUB key sequence to reboot the whole thing.

As asked here’s my hardware configuration:

  • ASUS PRIME X370-PRO motherboard with lastest BIOS update
  • Ryzen 5 1500X processor running at stock clock speed
  • Nvidia GTX 1060 3GB
  • Kingston HyperX 2133Mhz 8gb RAM memory

The Nvidia card is running the propietary software, which is working well pre-update (even though it was hard to get it running)

I’m on kernel version 4.15.0-1-default, which gets updated when I run sudo zypper dup.

EDIT: I’ve rolled back my installation to a point before updating the system (using snapper), and it works fine. Then I tried to update again, and it brought me to the same problem. What can I do besides leaving my system outdated?


Get this bounty!!!