On Tue, Jul 25, 2017 at 9:00 PM, < [email protected]> wrote:
> Send lfs-support mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.linuxfromscratch.org/listinfo/lfs-support > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of lfs-support digest..." > > > Today's Topics: > > 1. Issue on boot for LFS system (John D. Hefele) > 2. Re: Issue on boot for LFS system (Ken Moffat) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 25 Jul 2017 18:09:43 +0200 > From: "John D. Hefele" <[email protected]> > To: [email protected] > Subject: [lfs-support] Issue on boot for LFS system > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hello lfs support community! > > I have recently went through the majority of the lfs book, and up until > the final step, everything has gone great. At every opportunity I tested > the system, and did not experience and serious issues. However, I am > now having problems with the final step of rebooting the system. > Namely, my > problem is that after the grub menu is loaded, I am greeted by a black > screen filled with text and a message stating: > > VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 > > Before sending this email, I checked FAQ and found this: > > Kernel panic: VFS: unable to mount root fs > There are several reasons why the kernel might be unable to mount > the root filesystem. > - Did you specify the correct partition in /boot/grub/menu.lst? > - Is support for the hard drive enabled in the kernel. For SCSI > this means support for the specific SCSI adapter. > - Is support for the hard drive compiled into the kernel, not > just > as a module. (Modules are stored on the filesystem. If a driver needed > to access the filesystem is stored as a module on that filesystem, well > ... you know ... ;) > - Is support for the filesystem compiled into the kernel. Again, > not a module. Support for ext2 is enabled by default, but others like > ext3, reiser, jfs, and xfs are not. > > To address the first point, I am fairly certain I specified the correct > partition in /boot/grub/grub.cfg (above it is written menu.lst but I > suppose that is a minor detail). I am booting from a uefi system. > Because of this, to set up grub I followed the hint at > http://www.linuxfromscratch.org/hints/downloads/files/lfs-uefi.txt. > > To address the 2nd through 4th points I tried numerous setups of the > kernel. I followed the setup exactly from the hint above, I copied > .config file of my home system, and I even tried enabling all options > through the make allyesconfig command while disabling "support for > uevent > helper". So far, no luck. > > Below is all the relative information I could think of to solve the > problem. Please let me know if I should provide something else. From > here, I have really no idea how to precede. So any suggestions would > be very welcome. > > Cheers, > John David > > This is my grub.cfg file... > > # Begin /boot/grub/grub.cfg > set default=0 > set timeout=5 > > insmod gzio > insmod part_gpt > insmod ext4 #I tried ext2 there also, did not work... > set root=(hd0,gpt4) #I tried this without the gpt, still no result > # hd[x] is the drive of the LFS partion and gpt[y] is the partition > > insmod efi_gop > insmod efi_uga > insmod font > if loadfont /grub/unicode.pf2; then > loadfont /grub/unicode.pf2 > set gfxmode=auto > insmod gfxterm > set gfxpayload=keep > terminal_output gfxterm > fi > > menuentry "GNU/Linux, Linux 4.9.9-lfs-8.0" { > linux /boot/vmlinuz-4.9.9-lfs-8.0; root=/dev/sda4 ro #I tried > sda4 and hda4 here... > } > > Here is my etc/fstab file. As you can see, the there is a uefi > partition. > > # Begin /etc/fstab > > # file system mount-point type options dump fsck > # order > > /dev/sda4 / ext4 defaults 1 1 > /dev/sda3 swap swap pri=1 0 0 > proc /proc proc nosuid,noexec,nodev 0 0 > sysfs /sys sysfs nosuid,noexec,nodev 0 0 > devpts /dev/pts devpts gid=5,mode=620 0 0 > tmpfs /run tmpfs defaults 0 0 > devtmpfs /dev devtmpfs mode=0755,nosuid 0 0 > /dev/sda1 /boot/efi vfat defaults 0 1 > efivarfs /sys/firmware/efi/efivars efivarfs defaults 0 1 > # End /etc/fstab > > > This is from the fdisk -l command. dev/sda4 is my LFS partition > > Disk /dev/loop0: 80.5 MiB, 84393984 bytes, 164832 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 /dev/loop1: 79.5 MiB, 83349504 bytes, 162792 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 /dev/loop2: 79.5 MiB, 83349504 bytes, 162792 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 /dev/sda: 931.5 GiB, 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 > Disklabel type: gpt > Disk identifier: 81486A44-3CDC-49E2-8B1B-E52C0A0596D6 > > Device Start End Sectors Size Type > /dev/sda1 2048 1050623 1048576 512M EFI System > /dev/sda2 1050624 1834608639 1833558016 874.3G Linux filesystem > /dev/sda3 1937008640 1953523711 16515072 7.9G Linux swap > /dev/sda4 1834608640 1937008639 102400000 48.8G Linux filesystem > > And finally, this is from lshw... > striker1 > description: Notebook > product: Inspiron 7559 (0706) > vendor: Dell Inc. > version: 1.2.0 > serial: CWY6KD2 > width: 64 bits > capabilities: smbios-3.0 dmi-3.0 vsyscall32 > configuration: boot=normal chassis=notebook family=Inspiron > sku=0706 uuid=44454C4C-5700-1059-8036-C3C04F4B4432 > *-core > description: Motherboard > product: 0H0CC0 > vendor: Dell Inc. > physical id: 0 > version: A00 > serial: .CWY6KD2.CN4864367J01Z8. > slot: Inspiron > > > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 25 Jul 2017 19:56:51 +0100 > From: Ken Moffat <[email protected]> > To: LFS Support List <[email protected]> > Subject: Re: [lfs-support] Issue on boot for LFS system > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > On Tue, Jul 25, 2017 at 06:09:43PM +0200, John D. Hefele wrote: > > Hello lfs support community! > > > > I have recently went through the majority of the lfs book, and up until > > the final step, everything has gone great. At every opportunity I tested > > the system, and did not experience and serious issues. However, I am > > now having problems with the final step of rebooting the system. Namely, > my > > problem is that after the grub menu is loaded, I am greeted by a black > > screen filled with text and a message stating: > > > > VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 > > > > A black screen with white text is perfectly normal (we don't go in > for fancy boot splash screens, it's more important to be able to > ready any messages. > > Obviously that last error message is not normal. The interesting > thing is that no device seems to exist. > > > Before sending this email, I checked FAQ and found this: > > > > Kernel panic: VFS: unable to mount root fs > > There are several reasons why the kernel might be unable to mount > > the root filesystem. > > - Did you specify the correct partition in /boot/grub/menu.lst? > > So, the FAQ is old - you are right that grub2 uses grub.cfg. At > this point a linux kernel has loaded (I assume your host system > still boots, therefore the failing kernel must be for LFS. > > And that means that your stanza for this kernel in grub.cfg is > probably good enough. > > > - Is support for the hard drive enabled in the kernel. For SCSI > > this means support for the specific SCSI adapter. > > > > - Is support for the hard drive compiled into the kernel, not just > > as a module. (Modules are stored on the filesystem. If a driver needed > > to access the filesystem is stored as a module on that filesystem, well > > ... you know ... ;) > > - Is support for the filesystem compiled into the kernel. Again, > > not a module. Support for ext2 is enabled by default, but others like > > ext3, reiser, jfs, and xfs are not. > > > > To address the first point, I am fairly certain I specified the correct > > partition in /boot/grub/grub.cfg (above it is written menu.lst but I > > suppose that is a minor detail). I am booting from a uefi system. > > Because of this, to set up grub I followed the hint at > > http://www.linuxfromscratch.org/hints/downloads/files/lfs-uefi.txt. > > > > To address the 2nd through 4th points I tried numerous setups of the > > kernel. I followed the setup exactly from the hint above, I copied > > .config file of my home system, and I even tried enabling all options > > through the make allyesconfig command while disabling "support for uevent > > helper". So far, no luck. > > > > [...] > > Below is all the relative information I could think of to solve the > > problem. Please let me know if I should provide something else. From > > here, I have really no idea how to precede. So any suggestions would > > be very welcome. > > > > Cheers, > > John David > > > > > > > Here is my etc/fstab file. As you can see, the there is a uefi partition. > > > > # Begin /etc/fstab > > > > # file system mount-point type options dump fsck > > # order > > > > /dev/sda4 / ext4 defaults 1 1 > > /dev/sda3 swap swap pri=1 0 0 > > proc /proc proc nosuid,noexec,nodev 0 0 > > sysfs /sys sysfs nosuid,noexec,nodev 0 0 > > devpts /dev/pts devpts gid=5,mode=620 0 0 > > tmpfs /run tmpfs defaults 0 0 > > devtmpfs /dev devtmpfs mode=0755,nosuid 0 0 > > /dev/sda1 /boot/efi vfat defaults 0 1 > > efivarfs /sys/firmware/efi/efivars efivarfs defaults 0 1 > > # End /etc/fstab > > > Seems reasonable. > > > > This is from the fdisk -l command. dev/sda4 is my LFS partition > > > > Disk /dev/loop0: 80.5 MiB, 84393984 bytes, 164832 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 /dev/loop1: 79.5 MiB, 83349504 bytes, 162792 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 /dev/loop2: 79.5 MiB, 83349504 bytes, 162792 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 > > > > > > I've no idea why you are showing those, nor what they are. > They don't seem to be related to anything below. > > > Disk /dev/sda: 931.5 GiB, 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 > > Disklabel type: gpt > > Disk identifier: 81486A44-3CDC-49E2-8B1B-E52C0A0596D6 > > > > Device Start End Sectors Size Type > > /dev/sda1 2048 1050623 1048576 512M EFI System > > /dev/sda2 1050624 1834608639 1833558016 874.3G Linux filesystem > > /dev/sda3 1937008640 1953523711 16515072 7.9G Linux swap > > /dev/sda4 1834608640 1937008639 102400000 48.8G Linux filesystem > > > > This confirms that your fstab for sda4 seems reasonable. > > > And finally, this is from lshw... > > striker1 > > description: Notebook > > product: Inspiron 7559 (0706) > > vendor: Dell Inc. > > version: 1.2.0 > > serial: CWY6KD2 > > width: 64 bits > > capabilities: smbios-3.0 dmi-3.0 vsyscall32 > > configuration: boot=normal chassis=notebook family=Inspiron > > sku=0706 uuid=44454C4C-5700-1059-8036-C3C04F4B4432 > > *-core > > description: Motherboard > > product: 0H0CC0 > > vendor: Dell Inc. > > physical id: 0 > > version: A00 > > serial: .CWY6KD2.CN4864367J01Z8. > > slot: Inspiron > > We don't usually bother with lshw - lspci (with some verbosity) is > usually better for tuning the kernel config. In particular, it can > tell you which kernel driver is being used for each item. You may > then need to google for the name of the config option which builds > that driver. > > A less-efficient alternative is to begin by looking at which modules > are loaded and in use (lsmod). I'm a bit surprised that > 'allyesconfig' did not work. > > Both ATA and SATA drives have used /dev/sdX for a few years, and I > don't know anything about your hardware. If it really is SCSI, you > would need to build some SCSI driver. But if it is common SATA or > ATA, the following config options ought to be enough if you can't > get the details of what is in use : > > CONFIG_SCSI > CONFIG_SCSI_DMA > CONFIG_BLK_DEV_SD (other options needed if cdrom is present) > CONFIG_ATA and all options > CONFIG_SATA and all options > > It's probably easiest to start with your current config, then in > menuconfig search for those options using '/' and set them all to > 'y'. > > ĸen > -- > I live in a city. I know sparrows from starlings. After that > everything is a duck as far as I'm concerned. -- Monstrous Regiment > > > ------------------------------ > > Subject: Digest Footer > > -- > http://lists.linuxfromscratch.org/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > > ------------------------------ > > End of lfs-support Digest, Vol 768, Issue 1 > ******************************************* > Hello again, Firstly, thanks for the great reply! I went into my .config file and enabled all of the options quoted from above. The .config file was too big to paste into the email, so below is an excerpt of how I changed the file... # Controllers with non-SFF native interface # CONFIG_SATA_AHCI=y CONFIG_SATA_AHCI_PLATFORM=y CONFIG_SATA_INIC162X=y CONFIG_SATA_ACARD_AHCI=y CONFIG_SATA_SIL24=y CONFIG_ATA_SFF=y # # SFF controllers with custom DMA interface # # CONFIG_PDC_ADMA is not set CONFIG_SATA_QSTOR=y CONFIG_SATA_SX4=y CONFIG_ATA_BMDMA=y # # SATA SFF controllers with BMDMA # CONFIG_ATA_PIIX=y CONFIG_SATA_DWC=y CONFIG_SATA_DWC_OLD_DMA=y CONFIG_SATA_DWC_DEBUG=y CONFIG_SATA_DWC_VDEBUG=y CONFIG_SATA_MV=y CONFIG_SATA_NV=y CONFIG_SATA_PROMISE=y CONFIG_SATA_SIL=y CONFIG_SATA_SIS=y CONFIG_SATA_SVW=y CONFIG_SATA_ULI=y CONFIG_SATA_VIA=y CONFIG_SATA_VITESSE=y I basically just searched every term that had ATA and SATA and put =y next to them (even the ones which were commented out) However, I am still running into the same problem. To double check what type of disk I had, I ran "lshw -class disk -class storage" and found out that I have a SATA controller (I really don't know what a controller is), and an ATA disk. The output is shown below... *-storage description: SATA controller product: Sunrise Point-H SATA Controller [AHCI mode] vendor: Intel Corporation physical id: 17 bus info: pci@0000:00:17.0 version: 31 width: 32 bits clock: 66MHz capabilities: storage msi pm ahci_1.0 bus_master cap_list configuration: driver=ahci latency=0 *-disk description: ATA Disk product: ST1000LM014-1EJ1 vendor: Seagate physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/sda version: DEMG serial: W7735PQF size: 931GiB (1TB) capabilities: gpt-1.00 partitioned partitioned:gpt Also, it may be worth mentioning that when I did enable all kernel options that the start up was very slow (Maybe taking something like 5 minutes), but it froze with a different error.... NMA backtrace for cpu 2 skipped: idling at pc 0xffffff... Kernel panic - not syncing: hung_task: blocked tasks I don't if that means anything changed. Cheers, John D. Hefele
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
