i tried to install netrunner 15 in my productive envirement.
/dev/sda is my normal HDD with my whole data storing and a Gentoo Linux partition.
/dev/sdb is my new SDD where i want to install netrunner.
After my decision in the install process to use sdb, the installer formats correctly my SDD and stores the complete Data.
But!!! at the end of the install process i was able to see a message “grub install at /dev/sda”.
After reboot nothing happens any more, but this could
I think this is a bug, But where to report? Is it an UBUNTU-installer problem?
It isn’t a bug in particular that it tries to install grub on /dev/sda but it is definitely a bug that it doesn’t boot afterwards.
Btw. a short tip if you want to choose where to install grub in the installer choose manual partitioning and you will get a dropdownbox where you can choose where to install it.
To rescue the system now just boot from a live system and reinstall grub from your gentoo install. I am sure you as a gentoo user knows how to chroot into it and reinstall grub. If it’s grub2 it should also detect your netrunner 15 install and show it in the boot menu.
As for why grub did not show up. Can you provide the log that has been stored in /var/log/installer on the netrunner partition.
first, you are right, i can repair my system for myself, but i remember my first steps with linux and it is better for a newbie that the install process works correctly, before he fall back to some bad OS like… you know
Is that ok to paste the system.log parts directly to this post? I know some boards where people try to kill me when i do this
I think there is a command to force /dev/sda. Don’t know if this is neccessary.
And at least: It is possible that the non-boot problems result from a wrong parameter in my bios settings. I have to change some things in my BIOS settings like AHCI-mode of the SATA-Port… My old SSD works with IDE better, my new one not…
Here is the part of the syslog:
Feb 19 19:48:43 netrunner os-prober: No volume groups found
Feb 19 19:48:43 netrunner os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2
Feb 19 19:48:44 netrunner kernel: [ 1478.687500] EXT4-fs (sda2): unable to read superblock
Feb 19 19:48:44 netrunner kernel: [ 1478.689136] EXT4-fs (sda2): unable to read superblock
Feb 19 19:48:44 netrunner kernel: [ 1478.690761] EXT4-fs (sda2): unable to read superblock
Feb 19 19:48:44 netrunner kernel: [ 1478.692534] FAT-fs (sda2): bogus number of reserved sectors
Feb 19 19:48:44 netrunner kernel: [ 1478.692537] FAT-fs (sda2): Can’t find a valid FAT filesystem
Feb 19 19:48:44 netrunner kernel: [ 1479.002369] isofs_fill_super: bread failed, dev=sda2, iso_blknum=16, block=32
Feb 19 19:48:44 netrunner kernel: [ 1479.004258] SQUASHFS error: Can’t find a SQUASHFS superblock on sda2
Feb 19 19:48:44 netrunner kernel: [ 1479.010295] XFS (sda2): Invalid superblock magic number
Feb 19 19:48:44 netrunner kernel: [ 1479.013052] FAT-fs (sda2): bogus number of reserved sectors
Feb 19 19:48:44 netrunner kernel: [ 1479.013062] FAT-fs (sda2): Can’t find a valid FAT filesystem
Feb 19 19:48:44 netrunner kernel: [ 1479.023061] MINIX-fs: unable to read superblock
Feb 19 19:48:44 netrunner kernel: [ 1479.025059] attempt to access beyond end of device
Feb 19 19:48:44 netrunner kernel: [ 1479.025063] sda2: rw=16, want=3, limit=2
Feb 19 19:48:44 netrunner kernel: [ 1479.025065] hfsplus: unable to find HFS+ superblock
Feb 19 19:48:44 netrunner kernel: [ 1479.027364] qnx4: no qnx4 filesystem (no root dir).
Feb 19 19:48:44 netrunner kernel: [ 1479.030513] You didn’t specify the type of your ufs filesystem
Feb 19 19:48:44 netrunner kernel: [ 1479.030513]
Feb 19 19:48:44 netrunner kernel: [ 1479.030513] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep …
Feb 19 19:48:44 netrunner kernel: [ 1479.030513]
Feb 19 19:48:44 netrunner kernel: [ 1479.030513] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Feb 19 19:48:44 netrunner kernel: [ 1479.033276] hfs: can’t find a HFS filesystem on dev sda2
Feb 19 19:48:44 netrunner os-prober: debug: /dev/sda5: is active swap
Feb 19 19:48:44 netrunner grub-installer: info: Installing grub on ‘/dev/sda’
Feb 19 19:48:44 netrunner grub-installer: info: grub-install does not support --no-floppy
Feb 19 19:48:44 netrunner grub-installer: info: Running chroot /target grub-install --force “/dev/sda”
My system installing works with IDE-Mode. The installer finishes without errors.
After rebooting nothing happens. Only the message “starting operating system” (i don’t know the exakt message because i have a german system environment) and grub was NOT starting.
After this i changed the SATA-Mode, removed the power cable from SDA and made a fresh install. That works.
Ok, i think, we close this discussion here because it is not easy to remember the exact steps, but my conclusion: It was not possible to install the grub bootloader at SDB when SDA is connected.
[quote=“Suseberlin, post:5, topic:3007”]
but my conclusion: It was not possible to install the grub bootloader at SDB when SDA is connected.
Thanks for your support!
Suse
[/quote]O but you can , you must be in the “manual partitioning” mode of the installer however .
when you get to the partitioning part of the install you check “manual” and then next ,on the screen you get to then their is a drop-down box at the bottom that lets you chose where to install grub to .
if you are like me ,and have other installs , and one that controls grub already and you do not want the current grub in /dev/sda getting mucked with you can even install grub to the partition that the install went to ,like /dev/sdb1
your curent grub will pick up the new install when you run “sudo update-grub” from in it’s installed OS,or you can add a “menu entry” to chain load the grub install in /dev/sdb1 by adding it to the /etc/grub.d/40_custom in the main install … and then running “sudo update-grub”
it would look something like this
menuentry 'Kubuntu-14.10' {
set root='(hd0,msdos5)'
configfile /boot/grub/grub.cfg
}
this one points to /dev/sda5 …sda(hd0) 5(msdos5) …
