Jump to content
funtoo forums

elektroquark

Members
  • Content Count

    5
  • Joined

  • Last visited

  1. http://pastebin.com/yLKgXwtn Thank you again.
  2. No boot. I checked twice the UUID from your post and from the pastebin text: it's exactly the same in the grub.cfg file. It keeps complaining about the block it's not a valid root device.
  3. I will try this afternoon. Thank you. What's the problem? Is it assigning a different /dev descriptor at boot time? If it boots, and I think it would do because your are linking it "hardcoded", I will need to update GRUB configuration after each kernel update/upgrade/recompiling, wouldn't I? Thank you again.
  4. Hi, Here you have: http://pastebin.com/E0Pw6mLv Thank you.
  5. Hi, New future user of Funtoo here. I have a problem with the very first boot of Funtoo. My machine has several HDDs. I'm now running Mint 17.3 from a 80GB SATA. I'm using it to install Funtoo. With gParted I partitioned a 145GB SAS drive, (not SATA) on a Marvell 63xx controller, like this: sdh1 128MB ext2 /boot sdh2 2GB swap swap sdh3 rest of disk ext4 / The controller can do RAID but it's not configured to do it. It has two identical drives, one with Windows 10 and the other waiting for Funtoo. After first steps installing from Mint, at boot time I get the GRUB2 screen with the Funtoo installation as boot option. Booting from it the kernel is loaded and a bunch of driver modules tested and loaded. But then it stops complaining something like this: _____________________________________________________________________________________________________ !! Block device /dev/sdh3 is not a valid root device... !! Could not find the root block device in . Please specify another value or: press Enter for the same, type "shell" for shell, or "q" to skip... root block device() :: _____________________________________________________________________________________________________ The fstab is this: _____________________________________________________________________________________________________ /dev/sdh1 /boot ext2 noauto,noatime 1 2 /dev/sdh2 none swap sw 0 0 /dev/sdh3 / ext4 noatime 0 1 #/dev/cdrom /mnt/cdrom auto noauto,ro 0 0 _____________________________________________________________________________________________________ Could the kernel be missing the Marvell SAS controller drivers? If so, how is the kernel able to load? TIA.
×
×
  • Create New...