[yocto] [genericx86-jethro] core-image-sato - VFS: Cannot open root device "PARTUUID=8316.." or unknown-block(0, 0): error -6
Simon Bolek
simon.bolek at googlemail.com
Sat Jul 23 14:30:57 PDT 2016
One more questions about the Grub2 and EFI system for /dev/sda1
Is it actually possible to boot the system without initrd set?
It is not set during installation process in grub.cfg
It was also not in the FIDO install.sh, but FIDO was not:
parted ${device} mktable gpt
but:
parted /dev/${device} mklabel msdos
and the grub.cfg worked OK:
menuentry "Linux" {
set root=(hd0,1)
linux /vmlinuz root=/dev/sda2 rw quiet
}
So the initramfs you are talking about is actually missing now?
kind regards
Simon :-)
On Sat, Jul 23, 2016 at 8:31 PM, Simon Bolek <simon.bolek at googlemail.com>
wrote:
> On Sat, Jul 23, 2016 at 7:33 PM, Khem Raj <raj.khem at gmail.com> wrote:
>
>> On Sat, Jul 23, 2016 at 9:49 AM, Simon Bolek <simon.bolek at googlemail.com>
>> wrote:
>> > Thanks, sorry that I bother you all the time, but I do not seem to make
>> any
>> > progress :(
>> > Is there anything else I can check?
>> > It seems, on boot time this device is not mounted, only ram0...15.
>>
>> It so seems that driver may be missing in initramfs could be one
>> reason.
>
> You mean in on the boot partition under /grub/i386-pc/ among *.mod files?
> In this case, that would be /dev/sda2.
> Or am should I look for that somewhere else?
>
>
>
>> other reason could
>> be that udev is not settling down for this device. So may be changing
>> the udevadm to wait
>> a bit for devices to mount might help
>>
> Could you tell me where would I do that? I mean, where exactly is the
> udevadm set-up at boot? I cannot find the place. Is it somewhere inside
> /vmlinuz on /dev/sda2 ?
>
> thanks
> s:-)
>
>
>>
>> >
>> > thank you
>> > Simon :-)
>> >
>> >
>> >
>> > On Sat, Jul 23, 2016 at 6:07 PM, Khem Raj <raj.khem at gmail.com> wrote:
>> >>
>> >> On Sat, Jul 23, 2016 at 8:57 AM, Simon Bolek <
>> simon.bolek at googlemail.com>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > Well it is, as far as what
>> >> > parted /dev/sda print
>> >> > says.
>> >> >
>> >> > generated grub.cfg matches that with PARTUUID, so it looks fine.
>> >> >
>> >> > menuentry "Linux" {
>> >> > search --no-floppy --fs-uuid e88ec2c7-3438-4fe3-9033-83eb81957875
>> >> > --set
>> >> > root
>> >> > linux /vmlinuz root=PARTUUID=8316255c-f839-43fa-b2c6-d83bbed80962
>> >> > rw
>> >> > quiet
>> >>
>> >> this seems ok to me.
>> >>
>> >> >
>> >> > }
>> >> >
>> >> > However fdisks -l shows only /dev/sda1, which ist strange.
>> >> >
>> >> > Is there something wrong with install.sh script?
>> >> > Compared to FIDO, it is GPT, not MSDOS. But i did not touch anything
>> >> > there.
>> >> > Maybe you can take a look at it?
>> >> >
>> >> >
>> http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/initrdscripts/files/init-install.sh?h=jethro
>> >> > It always checks the grub version, however in FIDO Grub was also
>> 2.00,
>> >> > so I
>> >> > do not get the IFs.
>> >> >
>> >> > thank you!
>> >> > Simon :-)
>> >> >
>> >> >
>> >> > On Sat, Jul 23, 2016 at 4:52 PM, Khem Raj <raj.khem at gmail.com>
>> wrote:
>> >> >>
>> >> >>
>> >> >> > On Jul 23, 2016, at 5:25 AM, Simon Bolek <
>> simon.bolek at googlemail.com>
>> >> >> > wrote:
>> >> >> >
>> >> >> > Hello!
>> >> >> >
>> >> >> > I am trying to install genericx86 core-image-sato on a atom-pc
>> device
>> >> >> > with 80GB Intel SSD drive.
>> >> >> > I have created an image with
>> >> >> > bitbake core-image-sato
>> >> >> > without changing anything in the kernel via menuconfig, etc.
>> >> >> >
>> >> >> > ps. after installation I had to set /dev/sda1 to bootable with
>> disk
>> >> >>
>> >> >> it seems your rootfs is on /dev/sda3 can you check kernel parameters
>> >> >> what
>> >> >> is it passing for root=
>> >> >>
>> >> >> >
>> >> >> > After installation I have got this ugly error while booting the
>> >> >> > device.
>> >> >> > PLEASE HELP ME!
>> >> >> >
>> >> >> >
>> >> >> > "...
>> >> >> > VFS: Cannot open root device "PARTUUID=8316.." or
>> unknown-block(0,0):
>> >> >> > error -6
>> >> >> > Pease append a correct "root=" boot option; here are the available
>> >> >> > partitions:
>> >> >> > 0100 4096 ram0 (driver?)
>> >> >> > ...
>> >> >> > 010f 4096 ram15 (driver?)
>> >> >> > ..."
>> >> >> >
>> >> >> >
>> >> >> > I noticed that install.sh script is creating GPT
>> >> >> > parted ${device} mktable gpt
>> >> >> > not MSDOS as in previous yocto versions, e.g. fido.
>> >> >> >
>> >> >> > Any hint is more than welcome. The device will just not boot :((((
>> >> >> >
>> >> >> > Here are some details about the device:
>> >> >> >
>> >> >> >
>> >> >> > +++
>> >> >> > blkid says:
>> >> >> > /dev/sda2: UUID="e88ec2c7-3438-4fe3-9033-83eb81957875" TYPE="ext3"
>> >> >> > PARTLABEL="boot" PARTUUID="57f43ab0-6e30-4721-81e2-c565f6c184c8"
>> >> >> > /dev/sda3: UUID="cbb77742-c9fe-4f19-85d7-399af99c3aa8" TYPE="ext3"
>> >> >> > PARTLABEL="root" PARTUUID="8316255c-f839-43fa-b2c6-d83bbed80962"
>> >> >> > /dev/sda4: TYPE="swap" PARTLABEL="swap"
>> >> >> > PARTUUID="15ddbd73-15b3-40a8-97e7-6377048a79eb"
>> >> >> > /dev/sdb: SEC_TYPE="msdos" LABEL="boot" UUID="3C80-C1D7"
>> TYPE="vfat"
>> >> >> > /dev/sda1: PARTLABEL="bios_boot"
>> >> >> > PARTUUID="11cf26d2-2333-4c5b-a876-59d65929085f"
>> >> >> >
>> >> >> > +++
>> >> >> > /etc/fstab says
>> >> >> > # stock fstab - you probably want to override this with a machine
>> >> >> > specific one
>> >> >> >
>> >> >> > /dev/root / auto defaults
>> >> >> > 1 1
>> >> >> > proc /proc proc defaults
>> >> >> > 0 0
>> >> >> > devpts /dev/pts devpts
>> mode=0620,gid=5
>> >> >> > 0 0
>> >> >> > tmpfs /run tmpfs
>> >> >> > mode=0755,nodev,nosuid,strictatime 0 0
>> >> >> > tmpfs /var/volatile tmpfs defaults
>> >> >> > 0 0
>> >> >> >
>> >> >> > # uncomment this if your device has a SD/MMC/Transflash slot
>> >> >> > #/dev/mmcblk0p1 /media/card auto
>> >> >> > defaults,sync,noauto 0 0
>> >> >> >
>> >> >> > /dev/sda2 / ext3 rw
>> >> >> > 0 1
>> >> >> > /dev/disk/by-partuuid/15ddbd73-15b3-40a8-97e7-6377048a79eb
>> >> >> > swap swap defaults 0 0
>> >> >> > UUID=e88ec2c7-3438-4fe3-9033-83eb81957875 /boot
>> >> >> > ext3 defaults 1 2
>> >> >> >
>> >> >> >
>> >> >> > +++
>> >> >> > fdisk -l says
>> >> >> > Disk /dev/sda: 80.0 GB, 80026361856 bytes
>> >> >> > 255 heads, 63 sectors/track, 9729 cylinders
>> >> >> > Units = cylinders of 16065 * 512 = 8225280 bytes
>> >> >> >
>> >> >> > Device Boot Start End Blocks Id System
>> >> >> > /dev/sda1 * 1 9730 78150743+ ee EFI GPT
>> >> >> >
>> >> >> > +++
>> >> >> > parted /dev/sda says
>> >> >> > Model: ATA INTEL SSDSA2M080 (scsi)
>> >> >> > Disk /dev/sda: 80.0GB
>> >> >> > Sector size (logical/physical): 512B/512B
>> >> >> > Partition Table: gpt
>> >> >> > Disk Flags: pmbr_boot
>> >> >> >
>> >> >> > Number Start End Size File system Name Flags
>> >> >> > 1 1049kB 2097kB 1049kB bios_boot
>> bios_grub
>> >> >> > 2 2097kB 19.9MB 17.8MB ext3 boot
>> >> >> > 3 22.0MB 76.0GB 76.0GB ext3 root
>> >> >> > 4 76.0GB 80.0GB 4001MB linux-swap(v1) swap
>> >> >> >
>> >> >> > +++
>> >> >> > lspci says
>> >> >> > Device: 00:1f.2
>> >> >> > Class: IDE interface
>> >> >> > Vendor: Intel Corporation
>> >> >> > Device: NM10/ICH7 Family SATA Controller [IDE mode]
>> >> >> > SVendor: Intel Corporation
>> >> >> > SDevice: Device 464c
>> >> >> > Rev: 01
>> >> >> > ProgIf: 8a
>> >> >> > Driver: ata_piix
>> >> >> > Module: ata_piix
>> >> >> >
>> >> >> >
>> >> >> > thank you
>> >> >> > Simon :-)
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >
>> >
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160723/9a38f638/attachment.html>
More information about the yocto
mailing list