Cannot open root device error 6 - Исправление ошибок и поиск оптимальных решений проблем

Ставлю Gentoo, скомпилировал ядро через genkernel, установил grub, перезагрузился. Получаю ошибки:

Gentoo: cannot open root device sda3 or unknown-block(0,0): error -6
Please append a correct «root=» boot option; here are the available partitions:Kernel panic — not syncing: VFS: Unable to mount root fs on unknown-block(0,0)CPU: 0 PID: 1 comm swapper/0 Not tained 3.10.17-gentoo …

fdisk /dev/sda:

/dev/sda1 2048 67583 32768 83 Linux
/dev/sda2 67584 1116159 524288 83 Linux
/dev/sda3 1116160 16777215 7830528 83 Linux

/etc/fstab:

/dev/sda1 /boot ext2 defaults,noatime 1 2
/dev/sda3 / ext3 noatime 0 1/dev/sda2 none swap sw 0 0

задан 9 ноя 2013 в 9:47

grub тут абсолютно не при делах. Не хватает либо драйвера контроллера или ФС, либо ядру неверно передан параметр root, о чем оно и глаголет =) Разметку диска бы увидеть.

ответ дан 12 ноя 2013 в 11:31

GRUB куда ставил — на девайс или на раздел в девайсе? И есть ли там ещё системы, кроме? В общем, проблема в том, что GRUB путается с разделами, и не может найти загрузчика системы. Тем более, что это sda3! Можно всё поправить и с любого лайв-диска, но это вот, я думаю, поможет вам точно: http://www.supergrubdisk.org/

ответ дан 9 ноя 2013 в 20:11

Anton ReshinAnton Reshin

4184 серебряных знака9 бронзовых знаков

Источник

View previous topic :: View next topic

Author

Message

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Sat Nov 17, 2012 5:09 pm Post subject: [SOLVED] VFS: Cannot open root device «(null)» or

Hi,

I am in a situation very similar to the one of this post.: https://forums.gentoo.org/viewtopic-t-941980.html

Here are differences

boot is /dev/sdb1 (ext2)

root is /dev/sdb7 (ext3)

/boot/grub/grub.conf is

Code:

default 0

timeout 55

splashimage=(hd1,0)/boot/grub/splash.xpm.gz

title Gentoo Linux

root (hd1,0)

kernel /boot/kernel root=/dev/ram0 real_root=/dev/sdb7 rootfstype=ext3

initrd /boot/initramfs

title Gentoo Linux old kernel

root (hd1,0)

kernel /boot/kernel.old root=/dev/ram0 real_root=/dev/sdb7 rootfstype=ext3

initrd /boot/initramfs.old

I made the following changes to genkernel.conf

Code:

OLDCONFIG=»yes»

MENUCONFIG=»yes»

CLEAN=»no»

MRPROPER=»no»

MOUNTBOOT=»yes»

SYMLINK=»yes»

MAKEOPTS=»-j5″

I run

Code:

genkernel all

Code:

grub-install —no-floppy /dev/sda

At boot I receive this message

Quote:

VFS: Cannot open root device «(null)» or unknown-block(0,0): error -6 please append a correct «root=» boot option; here are the available partions: Kernel panic — not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

What can I do ?

Thanks for help

Last edited by augustin2 on Mon Nov 19, 2012 9:17 am; edited 1 time in total

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

Posted: Sat Nov 17, 2012 5:24 pm Post subject:

augustin2,

Your message

printk:

is from the kernel, so grub worked, read your grub.conf and loaded a kernel. Thats the good news.

Code:

unknown-block(0,0)

tells that the kernel cannot communicate with your hard drive at all, so nothing in the root file system matters yet, since the kernel cannot read it.

Something that you need to read the HDD is missing from your kernel.

In general terms thats the Partition Table driver SCSI Disk Driver or your Low Level Chipset driver.

As you used genkernel all, it should just work, as genkernel builds a fully modular kernel with almost every driver in the initramfs.

The «almost all» here is important — the one you need might be missing.

Show us the output of

Code:

lspci -k

and tell us how you partitioned your drives. The output of

Code:

fdisk -l

will do nicely.

With the above information we can tell you how to help genkernel make a kernel that will work for you.

Oh! if you are installing in a virtual machine, we need to know which one too. Answer no if you don’t know what a virtual machine is.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-

those that do backups

those that have never had a hard drive fail.

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Sat Nov 17, 2012 5:59 pm Post subject:

Thanks a lot. Here are the requested results

Code:

(chroot) Gentoo-2012 / # lspci -k

00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)

Subsystem: Giga-byte Technology Device 5000

00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)

Kernel driver in use: pcieport

00:05.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 3 (rev 11)

Kernel driver in use: pcieport

00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)

00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)

00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)

00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)

00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)

00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)

00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)

Subsystem: Giga-byte Technology Device 5004

Kernel driver in use: uhci_hcd

00:1a.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)

Subsystem: Giga-byte Technology Device 5004

Kernel driver in use: uhci_hcd

00:1a.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)

Subsystem: Giga-byte Technology Device 5004

Kernel driver in use: uhci_hcd

00:1a.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)

Subsystem: Giga-byte Technology Device 5006

Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)

Subsystem: Giga-byte Technology Device a102

Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)

Kernel driver in use: pcieport

00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06)

Kernel driver in use: pcieport

00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 06)

Kernel driver in use: pcieport

00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)

Kernel driver in use: pcieport

00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 (rev 06)

Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)

Subsystem: Giga-byte Technology Device 5004

Kernel driver in use: uhci_hcd

00:1d.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)

Subsystem: Giga-byte Technology Device 5004

Kernel driver in use: uhci_hcd

00:1d.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)

Subsystem: Giga-byte Technology Device 5004

Kernel driver in use: uhci_hcd

00:1d.3 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)

Subsystem: Giga-byte Technology Device 5004

Kernel driver in use: uhci_hcd

00:1d.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)

Subsystem: Giga-byte Technology Device 5006

Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)

00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)

Subsystem: Giga-byte Technology Device 5001

00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)

Subsystem: Giga-byte Technology Device b002

Kernel driver in use: ata_piix

00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)

Subsystem: Giga-byte Technology Device 5001

Kernel driver in use: i801_smbus

00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)

Subsystem: Giga-byte Technology Device b002

Kernel driver in use: ata_piix

02:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 GT] (rev a1)

Subsystem: Giga-byte Technology Device 344c

Kernel driver in use: nouveau

04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)

Subsystem: Giga-byte Technology Device 5007

Kernel driver in use: xhci_hcd

05:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)

Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard

Kernel driver in use: ahci

05:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)

Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard

Kernel driver in use: pata_jmicron

06:00.0 IDE interface: Marvell Technology Group Ltd. Device 91a3 (rev 11)

Subsystem: Giga-byte Technology Device b000

Kernel driver in use: ahci

07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)

Subsystem: Giga-byte Technology GA-EP45-DS5/GA-EG45M-DS2H Motherboard

Kernel driver in use: r8169

08:02.0 Network controller: Atheros Communications Inc. AR922X Wireless Network Adapter (rev 01)

Subsystem: D-Link System Inc Device 3a78

Kernel driver in use: ath9k

08:03.0 IDE interface: Integrated Technology Express, Inc. IT8213 IDE Controller

Subsystem: Giga-byte Technology GA-EG45M-DS2H Mainboard

Kernel driver in use: pata_it8213

08:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

Subsystem: Giga-byte Technology GA-EP45-DS5/GA-EG45M-DS2H Motherboard

3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

3f:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)

Subsystem: Giga-byte Technology Device 5000

(chroot) Gentoo-2012 / #

Code:

(chroot) Gentoo-2012 / # fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes

255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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 identifier: 0x000097bf

Device Boot Start End Blocks Id System

/dev/sda4 * 2107390 1953520064 975706337+ 5 Extended

/dev/sda5 1023693993 1953520064 464913036 83 Linux

/dev/sda6 2107392 25546751 11719680 82 Linux swap / Solaris

/dev/sda7 25548800 444978487 209714844 83 Linux

/dev/sda8 444981248 502207810 28613281+ 83 Linux

/dev/sda9 502210560 1023692981 260741211 83 Linux

Partition table entries are not in disk order

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes

255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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 identifier: 0x000da3c5

Device Boot Start End Blocks Id System

/dev/sdb1 63 55006559 27503248+ 83 Linux

/dev/sdb2 55006621 1953520064 949256722 5 Extended

/dev/sdb5 1023886773 1953520064 464816646 83 Linux

/dev/sdb6 55006623 140857919 42925648+ 83 Linux

/dev/sdb7 * 140859392 580525407 219833008 83 Linux

/dev/sdb8 580540968 1023886709 221672871 83 Linux

Partition table entries are not in disk order

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Sat Nov 17, 2012 6:04 pm Post subject:

I dont use a virtual machine

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

Posted: Sat Nov 17, 2012 6:15 pm Post subject:

augustin2,

What a selection of disk interfaces:-

Code:

00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)

Subsystem: Giga-byte Technology Device b002

Kernel driver in use: ata_piix

00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)

Subsystem: Giga-byte Technology Device b002

Kernel driver in use: ata_piix

05:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)

Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard

Kernel driver in use: ahci

05:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)

Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard

Kernel driver in use: pata_jmicron

06:00.0 IDE interface: Marvell Technology Group Ltd. Device 91a3 (rev 11)

Subsystem: Giga-byte Technology Device b000

Kernel driver in use: ahci

08:03.0 IDE interface: Integrated Technology Express, Inc. IT8213 IDE Controller

Subsystem: Giga-byte Technology GA-EG45M-DS2H Mainboard

Kernel driver in use: pata_it8213

Genkernel certainly includes ahci the ata_piix drivers but I’m ot sure about pata_jmicron and pata_it8213, so if your HDD was connected to one of there controllers, it might not work.

Your fdisk -k shows that your have MSDOS Partition Tables on your drives. genkernel builds that too.

I suspect your HDDs are connected to a controller that genkernel does not build the low level driver for.

Rerun genkernel from inside the chroot but this time give it the menuconfig option. That will have either — or — in front.

Genkernel will pause in menuconfig to allow you to check and make changes to the kernel configuration.

Make sure that the pata_jmicron and pata_it8213 options are on. If not set them as <*>. Press / to use search.

Save your menuconfig changes as you exit, then genkernel will carry on with the build.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-

those that do backups

those that have never had a hard drive fail.

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Sun Nov 18, 2012 8:33 am Post subject:

hi ,

I have almost found and set all the kernel drivers that are marked above as «in use» exept for i801_smbus that I cannot find anywhere with the search tool. but the result remains the same. May be the message has a bit evolved and is like this

Quote:

VFS: Cannot open root device «/dev/ram0» or unknown-block(0,0): error -6 please append a correct «root=» boot option; here are the available partions: Kernel panic — not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

cach0rr0
Bodhisattva

Joined: 13 Nov 2008
Posts: 4123
Location: Houston, Republic of Texas

Posted: Sun Nov 18, 2012 9:36 am Post subject:

augustin2 wrote:

hi ,

Quote:

i801_smbus should not be necessary for booting

one thing I noticed:

Code:

title Gentoo Linux

root (hd1,0)

kernel /boot/kernel root=/dev/ram0 real_root=/dev/sdb7 rootfstype=ext3

initrd /boot/initramfs

can you please:

-make sure your boot partition is mounted

-show us the output of ls -alh /boot/

If the initramfs is loading at all, then root=/dev/ram0 should *not* be invalid.

I am wondering if there is even any file named ‘/boot/initramfs’
_________________
Lost configuring your system?

dump lspci -n here | see Pappy’s guide | Link Stash

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Sun Nov 18, 2012 10:26 am Post subject:

Hi, thanks

Quote:

one thing I noticed:

Code:

title Gentoo Linux

root (hd1,0)

kernel /boot/kernel root=/dev/ram0 real_root=/dev/sdb7 rootfstype=ext3

initrd /boot/initramfs

can you please:

-make sure your boot partition is mounted

-show us the output of ls -alh /boot/

If the initramfs is loading at all, then root=/dev/ram0 should *not* be invalid.

I am wondering if there is even any file named ‘/boot/initramfs’

Before answering, and to make things as clear as possible to everybody, please let me sum up how I work

1- I am using a live DVD so I can communicate easyly with the forum

At each cycle, after booting and chrooting

2 — I copy the previous successful compilation like this

Code:

cp /etc/kernels/kernel-config-x86_64-3.5.7-gentoo /usr/src/linux/.config

3- assuming a genkernel.conf as this

Quote:

OLDCONFIG=»yes»

MENUCONFIG=»yes»

CLEAN=»no»

MRPROPER=»no»

MOUNTBOOT=»yes»

SYMLINK=»yes»

MAKEOPTS=»-j5″

I run

Code:

genkernel all

Normally the SYMLINK=»yes» provides for an updating of the symlinks in boot dir

Finaly I run

Code:

grub-install —no-floppy /dev/sda

Now the answer to your request

Quote:

(chroot) Gentoo-2012 / # ls -alh /boot/

total 15M

drwxr-xr-x 4 root root 4.0K Nov 18 10:28 .

drwxr-xr-x 21 root root 4.0K Nov 17 15:14 ..

-rw-r—r— 1 root root 0 Nov 7 05:47 .keep

lrwxrwxrwx 1 root root 40 Nov 18 10:28 System.map -> System.map-genkernel-x86_64-3.5.7-gentoo

-rw-r—r— 1 root root 1.8M Nov 18 10:28 System.map-genkernel-x86_64-3.5.7-gentoo

-rw-r—r— 1 root root 1.8M Nov 18 09:49 System.map-genkernel-x86_64-3.5.7-gentoo.old

lrwxrwxrwx 1 root root 44 Nov 18 10:28 System.map.old -> System.map-genkernel-x86_64-3.5.7-gentoo.old

lrwxrwxrwx 1 root root 1 Nov 17 16:06 boot -> .

drwxr-xr-x 2 root root 4.0K Nov 18 10:28 grub

lrwxrwxrwx 1 root root 39 Nov 18 10:28 initramfs -> initramfs-genkernel-x86_64-3.5.7-gentoo

-rw-r—r— 1 root root 1.5M Nov 18 10:28 initramfs-genkernel-x86_64-3.5.7-gentoo

-rw-r—r— 1 root root 1.5M Nov 18 09:49 initramfs-genkernel-x86_64-3.5.7-gentoo.old

lrwxrwxrwx 1 root root 43 Nov 18 10:28 initramfs.old -> initramfs-genkernel-x86_64-3.5.7-gentoo.old

lrwxrwxrwx 1 root root 36 Nov 18 10:28 kernel -> kernel-genkernel-x86_64-3.5.7-gentoo

-rw-r—r— 1 root root 4.1M Nov 18 10:28 kernel-genkernel-x86_64-3.5.7-gentoo

-rw-r—r— 1 root root 4.1M Nov 18 09:49 kernel-genkernel-x86_64-3.5.7-gentoo.old

lrwxrwxrwx 1 root root 40 Nov 18 10:28 kernel.old -> kernel-genkernel-x86_64-3.5.7-gentoo.old

drwx—— 2 root root 16K Nov 17 15:05 lost+found

(chroot) Gentoo-2012 / # ls -a /etc/kernels

and to be more accurate and introduce a new question

Quote:

(chroot) Gentoo-2012 / # cat /boot/grub/grub.conf

default 0

timeout 55

splashimage=(hd1,0)/boot/grub/splash.xpm.gz

title Gentoo Linux

root (hd1,0)

kernel /boot/kernel root=/dev/ram0 init=/linuxrc real_root=/dev/sdb7 rootfstype=ext3

initrd /boot/initramfs

title Gentoo Linux old kernel

root (hd1,0)

kernel /boot/kernel.old root=/dev/ram0 init=/linuxrc real_root=/dev/sdb7 rootfstype=ext3

initrd /boot/initramfs.old

I noticed in the handbook something like

Quote:

ernel /boot/kernel-genkernel-x86-2.6.34-gentoo-r1 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda3

thus I added init=/linuxrc but I hesitated with ramdisk=8192 because I was not sure it was relevant to my hardware.

I am going to test it now.

BillWho
Veteran
Veteran

Joined: 03 Mar 2012
Posts: 1600
Location: US

Posted: Sun Nov 18, 2012 2:11 pm Post subject:

augustin2,

Everything appears to be spot-on with your setup. One thing I noticed that might be a real long shot is the boot flag is set for your root partition:

Code:

/dev/sdb7 * 140859392 580525407 219833008 83 Linux

Try changing to /dev/sdb1 just to leave no stone unturned :wink:
_________________
Good luck :wink:

Since installing gentoo, my life has become one long emerge

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

Posted: Sun Nov 18, 2012 2:20 pm Post subject:

augustin2,

Code:

VFS: Cannot open root device «/dev/ram0» or unknown-block(0,0)

Suggested that you don’t have one or more of the following in your kernel.

Initramfs support.

DEVTMPFS

mount DEVTMPFS at boot. (Uppercase indicates a kernel symbol name that you can find with the search)

/dev/ram0 is where grub puts your initramfs so that the kernel can find it.

Check the above, if its still broken, use wgetpaste to put your kernel .config file onto a pastebin site.

BillWho,

A missing but required boot flag usually gives an Operating System not Found error from the BIOS.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-

those that do backups

those that have never had a hard drive fail.

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Sun Nov 18, 2012 4:44 pm Post subject:

BillWho wrote:

augustin2,

Everything appears to be spot-on with your setup. One thing I noticed that might be a real long shot is the boot flag is set for your root partition:

Code:

/dev/sdb7 * 140859392 580525407 219833008 83 Linux

Try changing to /dev/sdb1 just to leave no stone unturned :wink:

I did so but there is no change

I even restarted from scratch with sdb1 bootable and did a first genkernel all (using config from /usr/share/genkernel/arch/x86_64-kernel-config ) that worked fine.

But after that, using the .config that I got from Pappy’s seeds and improve all along this discussion only the old config runs and for the new I got the same message.

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Sun Nov 18, 2012 4:46 pm Post subject:

NeddySeagoon wrote:

augustin2,

Code:

VFS: Cannot open root device «/dev/ram0» or unknown-block(0,0)

Suggested that you don’t have one or more of the following in your kernel.

Initramfs support.

DEVTMPFS

mount DEVTMPFS at boot. (Uppercase indicates a kernel symbol name that you can find with the search)

/dev/ram0 is where grub puts your initramfs so that the kernel can find it.

Check the above, if its still broken, use wgetpaste to put your kernel .config file onto a pastebin site.

BillWho,

A missing but required boot flag usually gives an Operating System not Found error from the BIOS.

Ok I see that. Thanks.

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

Posted: Sun Nov 18, 2012 4:49 pm Post subject:

augustin2, Pappys Seeds does not contain any hardware drivers — you follow the instructions to add your own. Seeds based kernels also do not use an initramfs, so the grub.conf needs to be changed too. _________________ Regards, NeddySeagoon Computer users fall into two groups:- those that do backups those that have never had a hard drive fail.

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Sun Nov 18, 2012 5:54 pm Post subject:

NeddySeagoon wrote:

augustin2,

Pappys Seeds does not contain any hardware drivers — you follow the instructions to add your own.

Seeds based kernels also do not use an initramfs, so the grub.conf needs to be changed too.

I am afraid I don’t understand what to do.

As I used menuconfig to improve the seed adding the drivers for hardware, I wonder why it shouldn’t work.

I had a look at this .config and it seems that the DEVTMPFS was set.

Here is this .config after my adding of many drivers http://bpaste.net/show/58821/

If I must do differently could you please give me some hints.

BillWho
Veteran
Veteran

Joined: 03 Mar 2012
Posts: 1600
Location: US

Posted: Sun Nov 18, 2012 6:48 pm Post subject:

augustin2, In General setup # CONFIG_BLK_DEV_INITRD is not set Set [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support _________________ Good luck Since installing gentoo, my life has become one long emerge

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

Posted: Sun Nov 18, 2012 6:55 pm Post subject:

augustin2,

Code:

CONFIG_DEVTMPFS=y

# CONFIG_DEVTMPFS_MOUNT is not set

You need the second option there too.

Code:

CONFIG_MSDOS_PARTITION=y

is good. That enable the kernel to read your partition tables.

Code:

# CONFIG_IDE is not set

is good, that turns off obsolete disk drivers.

Code:

# CONFIG_SYSFS_DEPRECATED is not set

is good. Setting that option prevents udev from working.

Code:

CONFIG_SCSI=y

CONFIG_SCSI_PROC_FS=y

CONFIG_BLK_DEV_SD=y

CONFIG_BLK_DEV_SR=yC

ONFIG_CHR_DEV_SG=y

CONFIG_SCSI_MULTI_LUN=y

CONFIG_ATA=y

are all good. The last one is important — it allows you to boot without using an initrd.

Code:

# CONFIG_SATA_AHCI is not set

# CONFIG_SATA_AHCI_PLATFORM is not set

You need the first one for your

Code:

Kernel driver in use: ahci

You may need the second one too. On my systems the _PLATFORM setting seems to be BIOS dependent, but its harmless to set it on.

Code:

CONFIG_ATA_PIIX=y

is correct for Kernel driver in use: ata_piix

Code:

CONFIG_PATA_IT8213=y

CONFIG_PATA_JMICRON=y

is correct for pata_it8213 and pata_jmicron

Code:

CONFIG_EXT3_FS=y

is good for your root filesystem.

In grub.conf you had

Code:

title Gentoo Linux

root (hd1,0)

kernel /boot/kernel root=/dev/ram0 init=/linuxrc real_root=/dev/sdb7 rootfstype=ext3

initrd /boot/initramfs

but with a seed you don’t have an initrd, so don’t try to load it and don’t try to use it.

Code:

title Gentoo Linux

root (hd1,0)

kernel /boot/kernel root=/dev/sdb7 rootfstype=ext3

is all you need.

Provided your sdb is not attached to an ahci controller, the changes to grub.conf to not use an initrd should get you going.

If your sdb is attached to an ahci controller, you need to add the AHCI options to your kernel too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-

those that do backups

those that have never had a hard drive fail.

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Mon Nov 19, 2012 7:32 am Post subject:

Thank you very much for your help guys, I really appreciate it. But now it’s a forking path that is in front of me. Which way to chose is a kind of dilemna.

Eventually, I havel tried BillWho s’ suggestion that seemed a little bit faster. NeddySeagoon I must confess I dont really imagine what using or not using an initrd implies but it tells me that I have to read more about this and I preciously keep you suggestion at hand.

After trying BillWho s’ suggestion, I think I went one step farther but I have a new message :

Quote:

Loading modules

::scanning for scsi_wait_scan …………………..scsci_wait_scan loaded

::scanning for fuse ………….. …………………..fuse loaded

Hint : use parameter scandelay …………….if you need waiting here

activating mdev

determining root device

!! Block device /dev/sdb7 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 a shell or q to skip

Hum !

Last edited by augustin2 on Mon Nov 19, 2012 9:16 am; edited 1 time in total

augustin2
Apprentice

Joined: 16 Mar 2012
Posts: 244
Location: France

Posted: Mon Nov 19, 2012 9:15 am Post subject:

I have got it !

Thanks to you all guys, I am now entering the Gentoo wonderland.

Here is what I did:

Quote:

CONFIG_DEVTMPFS=»y»

CONFIG_DEVTMPFS_MOUNT=»y»

CONFIG_SATA_AHCI=»y»

CONFIG_SATA_AHCI_PLATEFORM=»y»

and both

Quote:

title Gentoo Linux

root (hd1,0)

kernel /boot/kernel boot=/dev/sdb7 rootfstype=ext3

initrd /boot/initramfs

and

Quote:

title Gentoo Linux

root (hd1,0)

kernel /boot/kernel initrd=/dev/ram0 real_root=/dev/sdb7 rootfstype=ext3

initrd /boot/initramfs

works .

Cheers !

Display posts from previous:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Источник

Was using w54 today for some debug. I had created some /usr/local/bin and lib directories to test out patches, and had done a bunch of boot tests.

I then wanted to clean up, so I kicked off the jenkins job to update the system to the latest openpower.xyz image (1048-b08d68fa39b9d4, https://openpower.xyz/job/openbmc-build/1048/)

The update seemed to go ok, but then it got stuck in an endless reboot.

We’ve seen this elsewhere, not sure if we had an issue tracking it or not.

Oct 20 21:14:13 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:13] "POST /upload/image HTTP/1.1" 200 169 6.302470
Oct 20 21:14:13 witherspoon systemd[1]: Started SSH Per-Connection Server (9.41.165.103:47084).
Oct 20 21:14:13 witherspoon dropbear[8153]: Failed loading /var/lib/dropbear/dropbear_rsa_host_key
Oct 20 21:14:13 witherspoon dropbear[8153]: Failed loading /etc/dropbear/dropbear_dss_host_key
Oct 20 21:14:13 witherspoon dropbear[8153]: Failed loading /etc/dropbear/dropbear_ecdsa_host_key
Oct 20 21:14:13 witherspoon dropbear[8153]: Child connection from ::ffff:9.41.165.103:47084
Oct 20 21:14:13 witherspoon dropbear[8153]: PAM password auth succeeded for 'root' from ::ffff:9.41.165.103:47084
Oct 20 21:14:14 witherspoon systemd[1]: Started SSH Per-Connection Server (9.41.165.103:47088).
Oct 20 21:14:15 witherspoon dropbear[8158]: Failed loading /var/lib/dropbear/dropbear_rsa_host_key
Oct 20 21:14:15 witherspoon dropbear[8158]: Failed loading /etc/dropbear/dropbear_dss_host_key
Oct 20 21:14:15 witherspoon dropbear[8158]: Failed loading /etc/dropbear/dropbear_ecdsa_host_key
Oct 20 21:14:15 witherspoon dropbear[8158]: Child connection from ::ffff:9.41.165.103:47088
Oct 20 21:14:15 witherspoon dropbear[8158]: PAM password auth succeeded for 'root' from ::ffff:9.41.165.103:47088
Oct 20 21:14:16 witherspoon systemd[1]: Started SSH Per-Connection Server (9.41.165.103:47096).
Oct 20 21:14:16 witherspoon dropbear[8165]: Failed loading /var/lib/dropbear/dropbear_rsa_host_key
Oct 20 21:14:16 witherspoon dropbear[8165]: Failed loading /etc/dropbear/dropbear_dss_host_key
Oct 20 21:14:16 witherspoon dropbear[8165]: Failed loading /etc/dropbear/dropbear_ecdsa_host_key
Oct 20 21:14:16 witherspoon dropbear[8165]: Child connection from ::ffff:9.41.165.103:47096
Oct 20 21:14:17 witherspoon dropbear[8165]: PAM password auth succeeded for 'root' from ::ffff:9.41.165.103:47096
Oct 20 21:14:18 witherspoon systemd[1]: Started SSH Per-Connection Server (9.41.165.103:47102).
Oct 20 21:14:18 witherspoon dropbear[8169]: Failed loading /var/lib/dropbear/dropbear_rsa_host_key
Oct 20 21:14:18 witherspoon dropbear[8169]: Failed loading /etc/dropbear/dropbear_dss_host_key
Oct 20 21:14:18 witherspoon dropbear[8169]: Failed loading /etc/dropbear/dropbear_ecdsa_host_key
Oct 20 21:14:18 witherspoon dropbear[8169]: Child connection from ::ffff:9.41.165.103:47102
Oct 20 21:14:19 witherspoon dropbear[8169]: PAM password auth succeeded for 'root' from ::ffff:9.41.165.103:47102
Oct 20 21:14:20 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:20] "POST /login HTTP/1.1" 200 320 0.065773
Oct 20 21:14:20 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:20] "GET /xyz/openbmc_project/software/bcd6d72f/attr/Activation HTTP/1.1" 200 226 0.130296
Oct 20 21:14:21 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:21] "POST /login HTTP/1.1" 200 320 0.035208
Oct 20 21:14:21 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:21] "GET /xyz/openbmc_project/software/bcd6d72f HTTP/1.1" 200 672 0.124216
Oct 20 21:14:21 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:21] "POST /login HTTP/1.1" 200 320 0.033600
Oct 20 21:14:22 witherspoon systemd[1]: Starting Set U-Boot environment variable...
Oct 20 21:14:22 witherspoon systemd[1]: Starting Set U-Boot environment variable...
Oct 20 21:14:22 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:22] "PUT /xyz/openbmc_project/software/bcd6d72f/attr/Priority HTTP/1.1" 200 169 1.170608
Oct 20 21:14:22 witherspoon systemd[1]: Starting Updates the u-boot variable to point BMC version to bcd6d72f...
Oct 20 21:14:22 witherspoon systemd[1]: Starting Set U-Boot environment variable...
Oct 20 21:14:23 witherspoon systemd[1]: Started Set U-Boot environment variable.
Oct 20 21:14:23 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:23] "POST /login HTTP/1.1" 200 320 0.032887
Oct 20 21:14:24 witherspoon systemd[1]: Started Set U-Boot environment variable.
Oct 20 21:14:24 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:24] "PUT /xyz/openbmc_project/control/host0/power_restore_policy/attr/PowerRestorePolicy HTTP/1.1" 200 169 0.369353
Oct 20 21:14:24 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:24] "POST /login HTTP/1.1" 200 320 0.033274
Oct 20 21:14:24 witherspoon systemd[1]: Started Set U-Boot environment variable.
Oct 20 21:14:24 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:24] "GET /xyz/openbmc_project/control/host0/power_restore_policy/attr/PowerRestorePolicy HTTP/1.1" 200 230 0.052356
Oct 20 21:14:25 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:25] "POST /login HTTP/1.1" 200 320 0.156727
Oct 20 21:14:25 witherspoon phosphor-gevent[1175]: ::60a9:5f76:8e91:f402%1995090716 - - [2017-10-20 21:14:25] "GET /xyz/openbmc_project/state/enumerate HTTP/1.1" 200 1016 0.464077
         Stopping Phosphor sysfs LED controller...
[  OK  ] Removed slice system-avsbusx2denable.slice.
         Stopping Network IPMI daemon...
[  OK  ] Removed slice system-fsix2dscan.slice.
         Stopping Phosphor sysfs LED controller...
         Stopping Phosphor Hwmon Poller...
[  OK  ] Removed slice system-vcs_workaround.slice.
         Stopping SSH Per-Connection Server (9.41.165.103:47096)...
         Stopping Phosphor sysfs LED controller...
[  OK  ] Removed slice system-powerx2dworkarounds.slice.
[  OK  ] Stopped target Power0 Host Off.
         Stopping Phosphor Hwmon Poller...
         Stopping Phosphor Hwmon Poller...
[  OK  ] Removed slice system-vrmx2dcontrol.slice.
[  OK  ] Removed slice system-openpowerx2ddebugx2dcollectorx2dwatchdog.slice.
         Stopping Phosphor Hwmon Poller...
         Stopping SSH Per-Connection Server (9.41.165.103:47028)...
[  OK  ] Stopped target Stop Host0.
[  OK  ] Removed slice system-opx2dresetx2dchassisx2don.slice.
[  OK  ] Removed slice system-vcs_off.slice.
[  OK  ] Stopped target Timers.
         Stopping Phosphor sysfs LED controller...
[  OK  ] Removed slice system-mboxdx2dreload.slice.
[  OK  ] Removed slice system-phosphorx2dresetx2dhostx2dcheck.slice.
         Stopping Phosphor Hwmon Poller...
[  OK  ] Removed slice system-avsbusx2ddisable.slice.
[  OK  ] Stopped Phosphor MSL Verification.
[  OK  ] Removed slice system-opx2dpowerx2dstart.slice.
[  OK  ] Stopped Assert bmc_booted LED.
[  OK  ] Stopped Wait for /xyz/openbmc_project/led/groups/bmc_booted.
[  OK  ] Stopped Wait for /org/openbmc/control/chassis0.
[  OK  ] Removed slice system-start_host.slice.
[  OK  ] Stopped target Chassis0 (Power Off).
[  OK  ] Stopped Power off mode bind ir35221 device driver devs.
[  OK  ] Stopped target Power0 Off.
[  OK  ] Stopped Stop Power0.
[  OK  ] Removed slice system-opx2dpowerx2dstop.slice.
[  OK  ] Removed slice system-phosphorx2dgpiox2dmonitor.slice.
[  OK  ] Removed slice system-obmcx2dflashx2dbmcx2dsetenv.slice.
         Stopping Phosphor sysfs LED controller...
[  OK  ] Removed slice system-ir35221x2doffx2dbind.slice.
         Stopping Phosphor sysfs LED controller...
[  OK  ] Stopped target System Time Synchronized.
[  OK  ] Stopped Wait for /xyz/openbmc_project/network/config.
[  OK  ] Removed slice system-phosphorx2dfanx2dcontrolx2dinit.slice.
[  OK  ] Stopped target Poweri Off.
[  OK  ] Stopped target Poweri Off (Pre).
[  OK  ] Stopped target Hosti (Stopped).
[  OK  ] Stopped target Hosti (Stopping).
[  OK  ] Removed slice system-opx2doccx2ddisable.slice.
         Stopping SSH Per-Connection Server (9.41.165.103:47084)...
[  OK  ] Stopped Wait for /org/openbmc/HostIpmi/1.
         Stopping Phosphor sysfs LED controller...
[  OK  ] Stopped Wait for /xyz/openbmc_project/control/host0.
[  OK  ] Removed slice system-obmcx2dsyncx2dinventoryx2ditem.slice.
[  OK  ] Removed slice system-opx2dwaitx2dpowerx2don.slice.
         Stopping Phosphor Hwmon Poller...
[  OK  ] Removed slice system-ir35221x2donx2dbind.slice.
[  OK  ] Removed slice system-obmcx2denablex2dhostx2dwatchdog.slice.
[  OK  ] Removed slice system-phosphorx2dwatchdog.slice.
         Stopping SSH Per-Connection Server (9.41.165.103:47102)...
         Stopping Phosphor DBUS Browser...
[  OK  ] Removed slice system-obmcx2dledx2dgroupx2dstart.slice.
[  OK  ] Removed slice system-vcs_on.slice.
[  OK  ] Removed slice system-pciex2dslotx2ddetect.slice.
[  OK  ] Removed slice system-ucd_disable_vcs.slice.
         Stopping Phosphor sysfs LED controller...
[  OK  ] Removed slice system-phosphorx2dfanx2dpresencex2dtach.slice.
         Stopping Phosphor sysfs LED controller...
[  OK  ] Removed slice system-mapperx2dsubtreex2dremove.slice.
[  OK  ] Removed slice system-phosphorx2dfanx2dmonitor.slice.
         Stopping Phosphor Webserver...
[  OK  ] Stopped Wait for /xyz/openbmc_project/watchdog/host0.
         Stopping Phosphor Hwmon Poller...
[  OK  ] Stopped target Stop Hosti (Pre).
         Stopping SSH Per-Connection Server (9.3.62.215:55242)...
[  OK  ] Removed slice system-phosphorx2dmax31785x2dmsl.slice.
[  OK  ] Removed slice system-opx2dresetx2dchassisx2drunning.slice.
[  OK  ] Removed slice system-fsix2dbind.slice.
[  OK  ] Stopped Assert power_on LED.
[  OK  ] Removed slice         Stopping Serial Getty on ttyS4...
[12530.850000] watchdog: watchdog0: watchdog did not stop!
[  OK  ] Stopped Phosphor Dump core monitor..
[  OK  ] Stopped Hardware RNG Entropy Gatherer Daemon.
[  OK  ] Stopped System Logging Service.
[  OK  ] Stopped Phosphor Console Muxer listening on device /dev/ttyVUART0.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Kernel Logging Service.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Avahi mDNS/DNS-SD Stack.
[  OK  ] Stopped Phosphor Sensor Manager.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Phosphor BMC0 Control.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Phosphor User Manager.
[  OK  ] Stopped Phosphor Network Manager.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Phosphor IPMI BT DBus Bridge.
[  OK  ] Stopped Phosphor Settings Daemon.
[  OK  ] Stopped Phosphor Log Manager.
[  OK  ] Stopped Phosphor Chassis0 Control.
[  OK  ] Stopped Phosphor Download Manager.
[  OK  ] Stopped Phosphor Inventory Manager.
[  OK  ] Stopped Phosphor Download Manager.
[  OK  ] Stopped Phosphor sysfs LED controller.
[  OK  ] Stopped Phosphor Dump Manager.
[  OK  ] Stopped Lightweight SLP Server.
[  OK  ] Stopped Serial Getty on ttyS4.
[  OK  ] Stopped Phosphor Hwmon Poller.
[  OK  ] Stopped Phosphor Hwmon Poller.
[  OK  ] Stopped Phosphor Hwmon Poller.
[  OK  ] Stopped Phosphor Hwmon Poller.
[  OK  ] Stopped Phosphor Webserver.
[  OK  ] Stopped Phoshpor System Manager.
[  OK  ] Stopped Phosphor Network Manager.
[  OK  ] Stopped Phosphor DBus Monitor.
[  OK  ] Stopped FRU Fault monitor service.
[  OK  ] Stopped Phosphor BMC Code Update.
[  OK  ] Stopped Phosphor MBOX Daemon.
[  OK  ] Stopped Phosphor GPIO 0 Presence.
[  OK  ] Stopped Phosphor GPIO 1 Presence.
[  OK  ] Stopped OpenPOWER OCC controller.
[  OK  ] Stopped Phosphor DNS Settings Cache Manager.
[  OK  ] Stopped Phosphor Version Software Manager.
[  OK  ] Stopped Phosphor BMC State Manager.
[  OK  ] Stopped Phosphor Power Button0.
[  OK  ] Stopped Phosphor Power0 Control.
[  OK  ] Stopped Phosphor Reset Button0.
[  OK  ] Stopped Phosphor Chassis State Manager.
[  OK  ] Stopped Witherspoon Power Supply 0 Monitor.
[  OK  ] Stopped Witherspoon Power Supply 1 Monitor.
[  OK  ] Stopped Phosphor Host State Manager.
[  OK  ] Stopped Phosphor Time Manager daemon.
[  OK  ] Stopped Witherspoon Fan Watchdog Daemon.
[  OK  ] Stopped SSH Per-Connection Server (9.3.62.215:55242).
[  OK  ] Stopped Phosphor Host Console SSH Per-Connection (9.3.62.215:53802).
[  OK  ] Stopped Phosphor DBUS Browser.
[  OK  ] Stopped Network IPMI daemon.
[  OK  ] Stopped Phosphor Inband IPMI.
[  OK  ] Stopped Phosphor Hwmon Poller.
[  OK  ] Stopped Phosphor Hwmon Poller.
[  OK  ] Stopped Phosphor Hwmon Poller.
[  OK  ] Stopped Phosphor Hwmon Poller.
[  OK  ] Stopped SSH Per-Connection Server (9.41.165.103:47028).
[  OK  ] Stopped SSH Per-Connection Server (9.41.165.103:47084).
[  OK  ] Stopped SSH Per-Connection Server (9.41.165.103:47088).
[  OK  ] Stopped SSH Per-Connection Server (9.41.165.103:47096).
[  OK  ] Stopped SSH Per-Connection Server (9.41.165.103:47102).
[  OK  ] Stopped Updates the u-boot variable to point BMC version to bcd6d72f.
[  OK  ] Removed slice system-obmcx2dflashx2dbmcx2dupdateubootvars.slice.
[  OK  ] Stopped Wait for /org/openbmc/settings/host0.
         Stopping Phosphor Settings Manager...
[  OK  ] Stopped Clear one time boot overrides.
[  OK  ] Stopped Wait for /xyz/openbmc_project/control/host0/boot.
[  OK  ] Stopped Wait for /xyz/openbmc_project/control/host0/restriction_mode.
[  OK  ] Stopped Wait for /xyz/openbmc_project/control/host0/boot/one_time.
[  OK  ] Stopped Wait for /xyz/openbmc_projeu2026ontrol/host0/power_restore_policy.
[  OK  ] Removed slice system-obmcx2dconsolex2dssh.slice.
[  OK  ] Removed slice system-dropbear.slice.
[  OK  ] Stopped Wait for /xyz/openbmc_project/state/host0.
[  OK  ] Stopped Wait for /xyz/openbmc_project/time/sync_method.
[  OK  ] Stopped Wait for /xyz/openbmc_project/time/owner.
[  OK  ] Stopped Wait for /xyz/openbmc_project/control/host0/auto_reboot.
[  OK  ] Stopped Wait for /xyz/openbmc_projeu2026tory/system/chassis/power_supply1.
[  OK  ] Removed slice system-witherspoonx2dpowerx2dsupplyx2dmonitor.slice.
[  OK  ] Stopped Wait for /xyz/openbmc_projeu2026tory/system/chassis/power_supply0.
[  OK  ] Stopped Wait for /org/openbmc/control/power0.
[  OK  ] Removed slice system-org.openbmc.buttons.reset.slice.
[  OK  ] Removed slice system-org.openbmc.control.Power.slice.
[  OK  ] Removed slice system-org.openbmc.buttons.Power.slice.
[  OK  ] Stopped Wait for /org/openbmc/managers/System.
         Stopping OpenBMC Software Update Manager...
[  OK  ] Stopped Wait for /org/openbmc/NetworkManager/Interface.
[  OK  ] Stopped Wait for /xyz/openbmc_project/inventory.
         Stopping Phosphor Inventory Manager...
[  OK  ] Removed slice system-phosphorx2dgpiox2dpresence.slice.
[  OK  ] Stopped Check PNOR UBI format.
         Stopping OpenPower Software Update Manager...
[  OK  ] Stopped Wait for /org/openbmc/managers/Download.
[  OK  ] Stopped Wait for /org/openbmc/control/bmc0.
[  OK  ] Stopped Wait for /xyz/openbmc_project/led/groups.
         Stopping Phosphor LED Group Management Daemon...
[  OK  ] Removed slice system-mapperx2dwait.slice.
[  OK  ] Stopped target Webserver (pre).
[  OK  ] Removed slice system-xyz.openbmc_project.Hwmon.slice.
         Stopping Permit User Sessions...
[  OK  ] Removed slice system-serialx2dgetty.slice.
[  OK  ] Removed slice system-org.openbmc.control.Chassis.slice.
[  OK  ] Removed slice system-org.openbmc.control.Bmc.slice.
[  OK  ] Removed slice system-xyz.openbmc_project.led.controller.slice.
[  OK  ] Removed slice system-obmcx2dconsole.slice.
[  OK  ] Stopped Phosphor Inventory Manager.
[  OK  ] Stopped Phosphor LED Group Management Daemon.
[  OK  ] Stopped Phosphor Settings Manager.
[  OK  ] Stopped OpenBMC Software Update Manager.
[  OK  ] Stopped OpenPower Software Update Manager.
[  OK  ] Stopped Permit User Sessions.
[  OK  ] Stopped target Network.
         Stopping Network Service...
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Phosphor Object Mapper.
         Stopping Phosphor DBus Service Discovery Manager...
[  OK  ] Stopped Network Service.
[  OK  ] Stopped Phosphor DBus Service Discovery Manager.
         Stopping D-Bus System Message Bus...
[  OK  ] Stopped D-Bus System Message Bus.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Slices.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped Forward Password Requests to Wall Directory Watch.
[  OK  ] Stopped Dispatch Password Requests to Console Directory Watch.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Closed Phosphor DBUS Browser socket.
[  OK  ] Closed dropbear.socket.
[  OK  ] Closed Phosphor Host Console SSH Per-Connection socket.
[  OK  ] Closed Syslog Socket.
[  OK  ] Closed Phosphor Webserver socket.
[  OK  ] Closed phosphor-ipmi-net.socket.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Stopped target System Initialization.
         Stopping Load/Save Random Seed...
         Stopping Network Time Synchronization...
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped Flush Journal to Persistent Storage.
[  OK  ] Stopped target Local File Systems.
         Unmounting /media/rofs-765c626c...
         Unmounting /usr/local/share/pnor...
         Unmounting /var/volatile...
         Unmounting /media/pnor-rw-8764baa3...
         Unmounting /home...
[12544.310000] UBIFS (ubi8:3): un-mount UBI device 8
[12544.310000] UBIFS (ubi8:3): background thread "ubifs_bgt8_3" stops
         Unmounting /media/pnor-ro-7a9ef57c...
         Unmounting /etc/machine-id...
         Unmounting /media/pnor-rw-7a9ef57c...
         Unmounting /media/rofs-bcd6d72f...
         Unmounting /media/pnor-prsv...
         Unmounting /media/pnor-ro-8764baa3...
         Unmounting Temporary Directory...
[12544.550000] UBIFS (ubi8:4): un-mount UBI device 8
[12544.550000] UBIFS (ubi8:4): background thread "ubifs_bgt8_4" stops
[12544.550000] UBIFS (ubi8:5): un-mount UBI device 8
[12544.550000] UBIFS (ubi8:5): background thread "ubifs_bgt8_5" stops
[12544.650000] UBIFS (ubi8:2): un-mount UBI device 8
[12544.650000] UBIFS (ubi8:2): background thread "ubifs_bgt8_2" stops
[  OK  ] Unmounted /media/rofs-765c626c.
[  OK  ] Unmounted /usr/local/share/pnor.
[  OK  ] Unmounted /var/volatile.
[  OK  ] Unmounted /media/pnor-rw-8764baa3.
[FAILED] Failed unmounting /home.
[  OK  ] Unmounted /media/pnor-ro-7a9ef57c.
[FAILED] Failed unmounting /etc/machine-id.
[  OK  ] Unmounted /media/pnor-rw-7a9ef57c.
[  OK  ] Unmounted /media/rofs-bcd6d72f.
[  OK  ] Unmounted /media/pnor-prsv.
[  OK  ] Unmounted Temporary Directory.
[  OK  ] Unmounted /media/pnor-ro-8764baa3.
[  OK  ] Stopped target Swap.
         Unmounting /etc...
         Unmounting /var...
         Unmounting /usr/local...
         Unmounting /media...
[  OK  ] Unmounted /etc.
[  OK  ] Unmounted /var.
[  OK  ] Unmounted /usr/local.
[  OK  ] Unmounted /media.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Reached target Shutdown.
[12546.740000] watchdog: watchdog0: watchdog did not stop!
[12546.740000] systemd-shutdow: 45 output lines suppressed due to ratelimiting
[12547.160000] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[12547.490000] systemd-journald[539]: Received SIGTERM from PID 1 (systemd-shutdow).
[12547.490000] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[12547.490000] systemd-shutdown[1]: Hardware watchdog 'aspeed_wdt', version 0
[12547.490000] systemd-shutdown[1]: Unmounting file systems.
[12547.490000] systemd-shutdown[1]: Remounting '/home' read-only with options ''.
[12547.490000] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" stops
[12547.670000] systemd-shutdown[1]: Unmounting /home.
[12547.670000] UBIFS (ubi0:2): un-mount UBI device 0
[12547.670000] systemd-shutdown[1]: Remounting '/etc/machine-id' read-only with options 'mode=755'.
[12547.670000] systemd-shutdown[1]: Unmounting /etc/machine-id.
[12547.670000] systemd-shutdown[1]: Remounting '/' read-only with options ''.
[12547.670000] systemd-shutdown[1]: Remounting '/' read-only with options ''.
[12547.860000] reboot: Restarting system


U-Boot 2016.07 (Aug 29 2017 - 21:30:45 +0000)

       Watchdog enabled
DRAM:  496 MiB
Flash: 32 MiB
In:    serial
Out:   serial
Err:   serial
Net:   aspeednic#0
Hit any key to stop autoboot:  0 
ubi0: attaching mtd1
ubi0: scanning is finished

. done
ubi0: attached mtd1 (name "mtd=2", size 31 MiB)
ubi0: PEB size: 65536 bytes (64 KiB), LEB size: 65408 bytes
ubi0: min./max. I/O unit sizes: 1/1, sub-page size 1
ubi0: VID header offset: 64 (aligned 64), data offset: 128
ubi0: good PEBs: 504, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 4, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 177/153, WL threshold: 4096, image sequence number: 1358235831
ubi0: available PEBs: 48, total reserved PEBs: 456, PEBs reserved for bad PEB handling: 0
Read 0 bytes from volume kernel-bcd6d72f to 80800000
No size specified -> Using max size (2114676)
## Loading kernel from FIT Image at 80800000 ...
   Using 'conf@1' configuration
   Trying 'kernel@1' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x8080012c
     Data Size:    2078664 Bytes = 2 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x80001000
     Entry Point:  0x80001000
     Hash algo:    sha1
     Hash value:   d5f53074beb20733cec4d4a75171f99c18255068
   Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 80800000 ...
   Using 'conf@1' configuration
   Trying 'fdt@1' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x809fb9e8
     Data Size:    34115 Bytes = 33.3 KiB
     Architecture: ARM
     Hash algo:    sha1
     Hash value:   82f97a3ec535e66f3c0c3c14e1cd76c1c5a31f89
   Verifying Hash Integrity ... sha1+ OK
   Booting using the fdt blob at 0x809fb9e8
   Loading Kernel Image ... OK
   Loading Device Tree to 9eb7a000, end 9eb85542 ... OK

Starting kernel ...
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.10.17-1af701e56cd6bd5399b517e276d479482b702839 (fspcibld@tulpok01p4) (gcc version 6.2.0 (GCC) ) #1 Thu Oct 19 03:45:32 UTC 2017
[    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] OF: fdt:Machine model: Witherspoon BMC
[    0.000000] Memory policy: Data cache writeback
[    0.000000] SOC Rev: 04030303
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 109600
[    0.000000] Kernel command line: console=ttyS4,115200n8 ubi.mtd=obmc-ubi,0,0,0 ubi.mtd=alt-obmc-ubi,0,0,4 ro rootfstype=squashfs ubi.block=4,0 root=/dev/ubiblock0_0
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 431968K/442368K available (4077K kernel code, 281K rwdata, 1188K rodata, 284K init, 111K bss, 10400K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0x9f800000 - 0xff800000   (1536 MB)
[    0.000000]     lowmem  : 0x80000000 - 0x9f000000   ( 496 MB)
[    0.000000]       .text : 0x80008000 - 0x804037a0   (4078 kB)
[    0.000000]       .init : 0x80587000 - 0x805ce000   ( 284 kB)
[    0.000000]       .data : 0x805ce000 - 0x806147a8   ( 282 kB)
[    0.000000]        .bss : 0x806147a8 - 0x80630658   ( 112 kB)
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] i2c controller registered, irq 16
[    0.000000] clocksource: moxart_timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 77222644334 ns
[    0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 21474836475000000ns
[    0.090000] Calibrating delay loop... 789.70 BogoMIPS (lpj=3948544)
[    0.090000] pid_max: default: 32768 minimum: 301
[    0.090000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090000] CPU: Testing write buffer coherency: ok
[    0.090000] ftrace: allocating 14995 entries in 44 pages
[    0.120000] Setting up static identity map for 0x80008200 - 0x8000825c
[    0.120000] devtmpfs: initialized
[    0.140000] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.140000] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.140000] pinctrl core: initialized pinctrl subsystem
[    0.140000] NET: Registered protocol family 16
[    0.140000] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.220000] usbcore: registered new interface driver usbfs
[    0.220000] usbcore: registered new interface driver hub
[    0.220000] usbcore: registered new device driver usb
[    0.230000] clocksource: Switched to clocksource moxart_timer
[    0.250000] NET: Registered protocol family 2
[    0.250000] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.250000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.250000] TCP: Hash tables configured (established 4096 bind 4096)
[    0.250000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.250000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.250000] NET: Registered protocol family 1
[    0.250000] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[    0.250000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.250000] jffs2: version 2.2. (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.250000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.250000] io scheduler noop registered
[    0.250000] io scheduler deadline registered
[    0.250000] io scheduler cfq registered (default)
[    0.270000] ipmi-bt-host 1e789140.ibt: Found bt bmc device
[    0.270000] ipmi-bt-host 1e789140.ibt: Using IRQ 22
[    0.270000] Serial: 8250/16550 driver, 6 ports, IRQ sharing enabled
[    0.300000] 1e787000.vuart: ttyS5 at MMIO 0x1e787000 (irq = 22, base_baud = 1500000) is a 16550A
[    0.300000] 1e783000.serial: ttyS0 at MMIO 0x1e783000 (irq = 23, base_baud = 1500000) is a 16550A
[    0.300000] 1e78d000.serial: ttyS1 at MMIO 0x1e78d000 (irq = 24, base_baud = 1500000) is a 16550A
[    0.300000] 1e784000.serial: ttyS4 at MMIO 0x1e784000 (irq = 25, base_baud = 1500000) is a 16550A
[    0.650000] console [ttyS4] enabled
[    0.790000] timeriomem_rng 1e6e2078.hwrng: 32bits from 0xf00e2078 @ 1us
[    0.810000] random: fast init done
[    0.850000] brd: module loaded
[    0.870000] loop: module loaded
[    0.870000] aspeed-lpc-ctrl 1e789080.lpc-ctrl: Loaded at 0x98000000 (0x04000000)
[    0.880000] aspeed-smc 1e620000.flash-controller: Using IRQ 18
[    0.880000] aspeed-smc 1e620000.flash-controller: DMA support disabled.
[    0.900000] aspeed-smc 1e620000.flash-controller: mx25l25635e (32768 Kbytes)
[    0.900000] aspeed-smc 1e620000.flash-controller: CE0 window [ 0x20000000 - 0x22000000 ] 32MB
[    0.900000] aspeed-smc 1e620000.flash-controller: CE1 window [ 0x22000000 - 0x2a000000 ] 128MB
[    0.920000] 3 ofpart partitions found on MTD device bmc
[    0.920000] Creating 3 MTD partitions on "bmc":
[    0.920000] 0x000000000000-0x000000060000 : "u-boot"
[    0.920000] 0x000000060000-0x000000080000 : "u-boot-env"
[    0.960000] random: crng init done
[    0.960000] 0x000000080000-0x000002000000 : "obmc-ubi"
[    0.970000] aspeed-smc 1e620000.flash-controller: mx25l25635e (32768 Kbytes)
[    0.980000] aspeed-smc 1e620000.flash-controller: CE1 window [ 0x22000000 - 0x24000000 ] 32MB
[    0.980000] aspeed-smc 1e620000.flash-controller: CE2 window [ 0x24000000 - 0x2c000000 ] 128MB
[    1.000000] 3 ofpart partitions found on MTD device alt-bmc
[    1.000000] Creating 3 MTD partitions on "alt-bmc":
[    1.010000] 0x000000000000-0x000000060000 : "alt-u-boot"
[    1.010000] 0x000000060000-0x000000080000 : "alt-u-boot-env"
[    1.030000] 0x000000080000-0x000002000000 : "alt-obmc-ubi"
[    1.040000] aspeed-smc 1e630000.flash-controller: mx66l1g45g (131072 Kbytes)
[    1.050000] aspeed-smc 1e630000.flash-controller: CE0 window resized to 120MB (AST2500 HW quirk)
[    1.050000] aspeed-smc 1e630000.flash-controller: CE0 window [ 0x30000000 - 0x37800000 ] 120MB
[    1.070000] aspeed-smc 1e630000.flash-controller: CE0 window too small for chip 128MB
[    1.070000] aspeed-smc 1e630000.flash-controller: CE1 window [ 0x37800000 - 0x38000000 ] 8MB
[    1.840000] libphy: Fixed MDIO Bus: probed
[    1.840000] ftgmac100 1e660000.ethernet: Read MAC address 70:e2:84:14:23:e1 from chip
[    1.840000] ftgmac100 1e660000.ethernet: Using NCSI interface
[    1.840000] ftgmac100 1e660000.ethernet eth0: irq 20, mapped at f0060000
[    1.840000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.840000] ehci-platform: EHCI generic platform driver
[    2.050000] i2c /dev entries driver
[    2.050000] aspeed-i2c-bus 1e78a0c0.i2c-bus: i2c bus 2 registered, irq 26
[    2.050000] aspeed-i2c-bus 1e78a100.i2c-bus: i2c bus 3 registered, irq 27
[    2.050000] aspeed-i2c-bus 1e78a140.i2c-bus: i2c bus 4 registered, irq 28
[    2.050000] aspeed-i2c-bus 1e78a180.i2c-bus: i2c bus 5 registered, irq 29
[    2.050000] aspeed-i2c-bus 1e78a380.i2c-bus: i2c bus 9 registered, irq 30
[    2.050000] aspeed-i2c-bus 1e78a3c0.i2c-bus: i2c bus 10 registered, irq 31
[    2.050000] rtc-rv8803 11-0032: Voltage low, temperature compensation stopped.
[    2.050000] rtc-rv8803 11-0032: An alarm maybe have been missed.
[    2.160000] rtc-rv8803 11-0032: rtc core: registered rx8900 as rtc0
[    2.170000] at24 11-0051: 8192 byte 24c64 EEPROM, writable, 1 bytes/write
[    2.170000] aspeed-i2c-bus 1e78a400.i2c-bus: i2c bus 11 registered, irq 32
[    2.170000] aspeed-i2c-bus 1e78a440.i2c-bus: i2c bus 12 registered, irq 33
[    2.170000] aspeed-i2c-bus 1e78a480.i2c-bus: i2c bus 13 registered, irq 34
[    2.170000] Driver for 1-wire Dallas network protocol.
[    2.170000] lm75 9-004a: hwmon0: sensor 'tmp275'
[    3.900000] ucd9000 11-0064: Device ID UCD90160|2.3.4.0000|110603
[    4.600000] leds-pca955x 3-0060: leds-pca955x: Using pca9552 16-bit LED driver at slave address 0x60
[    4.610000] leds-pca955x 3-0060: gpios 238...253
[    4.620000] leds-pca955x 11-0060: leds-pca955x: Using pca9552 16-bit LED driver at slave address 0x60
[    4.630000] leds-pca955x 11-0060: gpios 222...237
[    4.640000] usbcore: registered new interface driver usbhid
[    4.640000] usbhid: USB HID core driver
[    4.700000] NET: Registered protocol family 10
[    4.700000] Segment Routing with IPv6
[    4.710000] NET: Registered protocol family 17
[    4.710000] 8021q: 802.1Q VLAN Support v1.8
[    4.730000] input: gpio-keys-polled as /devices/platform/gpio-keys-polled/input/input1
[    4.750000] ubi0: default fastmap pool size: 25
[    4.760000] ubi0: default fastmap WL pool size: 12
[    4.760000] ubi0: attaching mtd3
[    4.770000] ubi0: scanning is finished
[    4.790000] ubi0: attached mtd3 (name "obmc-ubi", size 31 MiB)
[    4.790000] ubi0: PEB size: 65536 bytes (64 KiB), LEB size: 65408 bytes
[    4.810000] ubi0: min./max. I/O unit sizes: 1/256, sub-page size 1
[    4.810000] ubi0: VID header offset: 64 (aligned 64), data offset: 128
[    4.810000] ubi0: good PEBs: 504, bad PEBs: 0, corrupted PEBs: 0
[    4.810000] ubi0: user volume: 4, internal volumes: 1, max. volumes count: 128
[    4.840000] ubi0: max/mean erase counter: 177/153, WL threshold: 4096, image sequence number: 1358235831
[    4.840000] ubi0: available PEBs: 46, total reserved PEBs: 458, PEBs reserved for bad PEB handling: 0
[    4.840000] ubi0: background thread "ubi_bgt0d" started, PID 507
[    4.840000] ubi4: default fastmap pool size: 25
[    4.840000] ubi4: default fastmap WL pool size: 12
[    4.870000] ubi4: attaching mtd7
[    4.910000] ubi4: scanning is finished
[    4.950000] ubi4: attached mtd7 (name "alt-obmc-ubi", size 31 MiB)
[    4.950000] ubi4: PEB size: 65536 bytes (64 KiB), LEB size: 65408 bytes
[    4.950000] ubi4: min./max. I/O unit sizes: 1/256, sub-page size 1
[    4.950000] ubi4: VID header offset: 64 (aligned 64), data offset: 128
[    4.950000] ubi4: good PEBs: 504, bad PEBs: 0, corrupted PEBs: 0
[    5.000000] ubi4: user volume: 4, internal volumes: 1, max. volumes count: 128
[    5.000000] ubi4: max/mean erase counter: 153/123, WL threshold: 4096, image sequence number: 1358235831
[    5.000000] ubi4: available PEBs: 46, total reserved PEBs: 458, PEBs reserved for bad PEB handling: 0
[    5.000000] ubi4: background thread "ubi_bgt4d" started, PID 513
[   15.310000] block ubiblock4_0: created from ubi4:0(rofs-bcd6d72f)
[   15.310000] console [netcon0] enabled
[   15.310000] netconsole: network logging started
[   15.310000] input: gpio-keys as /devices/platform/gpio-keys/input/input2
[   15.310000] rtc-rv8803 11-0032: setting system clock to 2017-10-20 21:15:15 UTC (1508534115)
[   15.310000] VFS: Cannot open root device "ubiblock0_0" or unknown-block(0,0): error -6
[   15.310000] Please append a correct "root=" boot option; here are the available partitions:
[   15.310000] 0100            4096 ram0 
[   15.310000]  (driver?)
[   15.310000] 0101            4096 ram1 
[   15.310000]  (driver?)
[   15.310000] 0102            4096 ram2 
[   15.310000]  (driver?)
[   15.310000] 0103            4096 ram3 
[   15.310000]  (driver?)
[   15.410000] 0104            4096 ram4 
[   15.410000]  (driver?)
[   15.410000] 0105            4096 ram5 
[   15.410000]  (driver?)
[   15.410000] 0106            4096 ram6 
[   15.410000]  (driver?)
[   15.410000] 0107            4096 ram7 
[   15.410000]  (driver?)
[   15.410000] 0108            4096 ram8 
[   15.410000]  (driver?)
[   15.410000] 0109            4096 ram9 
[   15.410000]  (driver?)
[   15.410000] 010a            4096 ram10 
[   15.410000]  (driver?)
[   15.410000] 010b            4096 ram11 
[   15.410000]  (driver?)
[   15.410000] 010c            4096 ram12 
[   15.410000]  (driver?)
[   15.470000] 010d            4096 ram13 
[   15.470000]  (driver?)
[   15.470000] 010e            4096 ram14 
[   15.470000]  (driver?)
[   15.470000] 010f            4096 ram15 
[   15.470000]  (driver?)
[   15.470000] 1f00           32768 mtdblock0 
[   15.470000]  (driver?)
[   15.470000] 1f01             384 mtdblock1 
[   15.470000]  (driver?)
[   15.470000] 1f02             128 mtdblock2 
[   15.470000]  (driver?)
[   15.470000] 1f03           32256 mtdblock3 
[   15.470000]  (driver?)
[   15.470000] 1f04           32768 mtdblock4 
[   15.470000]  (driver?)
[   15.470000] 1f05             384 mtdblock5 
[   15.470000]  (driver?)
[   15.470000] 1f06             128 mtdblock6 
[   15.470000]  (driver?)
[   15.530000] 1f07           32256 mtdblock7 
[   15.530000]  (driver?)
[   15.530000] 1f08          131072 mtdblock8 
[   15.530000]  (driver?)
[   15.530000] fe00           14860 ubiblock4_0 
[   15.530000]  (driver?)
[   15.530000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   15.530000] CPU: 0 PID: 1 Comm: swapper Not tainted 4.10.17-1af701e56cd6bd5399b517e276d479482b702839 #1
[   15.530000] Hardware name: ASpeed SoC
[   15.530000] [<80010080>] (unwind_backtrace) from [<8000d934>] (show_stack+0x20/0x24)
[   15.530000] [<8000d934>] (show_stack) from [<801dbf2c>] (dump_stack+0x20/0x28)
[   15.530000] [<801dbf2c>] (dump_stack) from [<800a4a40>] (panic+0xc8/0x264)
[   15.530000] [<800a4a40>] (panic) from [<805884f8>] (mount_block_root+0x214/0x300)
[   15.530000] [<805884f8>] (mount_block_root) from [<80588740>] (mount_root+0x60/0x7c)
[   15.530000] [<80588740>] (mount_root) from [<805888c8>] (prepare_namespace+0x16c/0x1d0)
[   15.530000] [<805888c8>] (prepare_namespace) from [<805880b0>] (kernel_init_freeable+0x184/0x1cc)
[   15.530000] [<805880b0>] (kernel_init_freeable) from [<803fdc60>] (kernel_init+0x18/0x104)
[   15.530000] [<803fdc60>] (kernel_init) from [<8000a5e8>] (ret_from_fork+0x14/0x2c)


U-Boot 2016.07 (Aug 29 2017 - 21:30:45 +0000)

Источник

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

gwi: Level 2; Posts: 96; Joined: Mon Jun 04, 2012 4:20 pm

[SOLVED] Mint 15: kernel panic, cannot open root device

Hello,

Yesterday I decided to upgrade from Mint 13 to Mint 15, by performing a fresh install from the live DVD (actually live USB), including recreation and formatting of the partitions.
Installation went well, until I rebooted. The system halted with a kernel panic. With «quiet splash» removed from the kernel command line, I saw the following:

Code: Select all

BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.

VFS: Cannot open root device " sda2" or unknown-block(0,0): error -6
Please append a correct " root="  boot option; here are the available partitions:
Kernal panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.5.0-17-generic #28-Ubuntu

The live DVD is booting and working properly.
I tried Boot-repair without success.
I tried adding the kernel command line parameters edd=on, edd=off, nolapic, raid=noautodetect in various combinations, all with same result.
I tried reinstalling, again formatting all partitions. Same result.

I started using Linux in 2006 (Ubuntu Dapper Drake), and switched to Mint last year (because I don’ t like Unity). I never had a problem like this when upgrading.
I never changed my partitioning scheme, which has a separate root and boot partition. I now tried reinstalling Mint 15 using a single root parition, without a separate boot partition: same result.

blkid shows:

Code: Select all

/dev/sda1: UUID="9d2c562d-b148-4703-8096-eac97392daca" TYPE="ext4"

The Grub menu entry in grub.cfg is:

Code: Select all

menuentry 'Linux Mint 15 Cinnamon 64-bit, 3.8.0-19-generic.efi.signed (/dev/sda1)' --class linuxmint --class gnu-linux --class gnu --class os {
	recordfail
	gfxmode $linux_gfx_mode
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  9d2c562d-b148-4703-8096-eac97392daca
	else
	  search --no-floppy --fs-uuid --set=root 9d2c562d-b148-4703-8096-eac97392daca
	fi
	linux	/boot/vmlinuz-3.8.0-19-generic.efi.signed root=/dev/sda1 ro persistent  quiet splash $vt_handoff
}

Motherboard is an Asus M2N SLI DeLuxe, with an AMD Athlon X2 4800+. I am installing Mint 15 Cinnamon 64-bit. /dev/sda is an Intel 320 series SSD.

What is going wrong here? How can I get my system up and running with Mint 15?

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

Regards,

George

Linux Mint 20.3 Unsa Cinnamon 64-bit, Asus Vanguard B85, Intel Core i7 4770S

gwi: Level 2; Posts: 96; Joined: Mon Jun 04, 2012 4:20 pm

Re: Mint 15: kernel panic, cannot open root device

Post

by gwi » Thu Jun 27, 2013 5:04 pm

Yes, there is an initrd line, but only in a submenu » Previous Linux versions»:

Code: Select all

submenu "Previous Linux versions" {
menuentry 'Linux Mint 15 Cinnamon 64-bit, 3.8.0-19-generic (/dev/sda1)' --class linuxmint --class gnu-linux --class gnu --class os {
	recordfail
	gfxmode $linux_gfx_mode
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  9d2c562d-b148-4703-8096-eac97392daca
	else
	  search --no-floppy --fs-uuid --set=root 9d2c562d-b148-4703-8096-eac97392daca
	fi
	linux	/boot/vmlinuz-3.8.0-19-generic root=UUID=9d2c562d-b148-4703-8096-eac97392daca ro persistent  quiet splash $vt_handoff
	initrd	/boot/initrd.img-3.8.0-19-generic
}

The result of fdisk -l is:

Code: Select all

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 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 identifier: 0x0008a038

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     4999167     2498560   83  Linux
/dev/sda3         5001214   153999359    74499073    5  Extended
/dev/sda5         5001216   129998847    62498816   83  Linux
/dev/sda6       130000896   145999871     7999488   83  Linux
/dev/sda7       146001920   153999359     3998720   83  Linux

Regards,

George

Linux Mint 20.3 Unsa Cinnamon 64-bit, Asus Vanguard B85, Intel Core i7 4770S

WharfRat: Level 21; Posts: 13834; Joined: Thu Apr 07, 2011 8:15 pm

Re: Mint 15: kernel panic, cannot open root device

Post

by WharfRat » Thu Jun 27, 2013 5:14 pm

gwi,

Did you use manual partitioning

Also I don’t see a swap — did you set one up

Do you know what these partitions are

Code: Select all

/dev/sda5         5001216   129998847    62498816   83  Linux
/dev/sda6       130000896   145999871     7999488   83  Linux
/dev/sda7       146001920   153999359     3998720   83  Linux

gwi: Level 2; Posts: 96; Joined: Mon Jun 04, 2012 4:20 pm

Re: Mint 15: kernel panic, cannot open root device

Post

by gwi » Fri Jun 28, 2013 2:22 am

sda5 = /home
sda6 = /usr
sda7 = /var

sda is an SSD, swap is on an HDD as /dev/sdb1.

This setup has been the same since april 2011, and survived several distribution upgrades. Begore that, the partitioning scheme was the same, but then without the SSD.

All partitions are there. If I boot from the live DVD I can mount them. Nothing wrong there it seems. It’s just that on boot the system can’t find the root partition. That in itself is strange, because the Grub menu is shown. That menu is in /boot/grub, which is on the same partition as /.

Edit:
I just did a reinstall, letting the installer partition the drive. Same result.
On first boot the system freezes with a black screen, without any kind of cursor. I waited over 3 minutes, nothing happened.
ctrl-alt-F1 — F10: nothing
ctrl-als-backspace: nothing
cltr-alt-del: nothing
alt-sysrq-b: nothing

Every following boot ends with a kernel panic.

So the partitioning schema by itself does not seem to have any effect on what is happening.

Last edited by gwi on Fri Jun 28, 2013 5:17 am, edited 1 time in total.

Regards,

George

Linux Mint 20.3 Unsa Cinnamon 64-bit, Asus Vanguard B85, Intel Core i7 4770S

eanfrid

Re: Mint 15: kernel panic, cannot open root device

Post

by eanfrid » Fri Jun 28, 2013 3:51 am

Code: Select all

VFS: Cannot open root device " sda2" or unknown-block(0,0): error -6

According to your partition scheme, there is no more «sda2».

Why did you choose to install an EFI/signed kernel ? On a 80GB SSD with a MBR partitioning scheme

gwi: Level 2; Posts: 96; Joined: Mon Jun 04, 2012 4:20 pm

Re: Mint 15: kernel panic, cannot open root device

Post

by gwi » Fri Jun 28, 2013 10:14 am

eanfrid wrote:
Code: Select all
VFS: Cannot open root device " sda2" or unknown-block(0,0): error -6
According to your partition scheme, there is no more «sda2».

In the partition scheme I posted, there is no longer an sda2, because I did a reinstall without a separate /boot partition to check if that would solve the problem. There was an sda2 on my first attempt.

eanfrid wrote:Why did you choose to install an EFI/signed kernel ? On a 80GB SSD with a MBR partitioning scheme

Where does the Mint installer let me choose which kernel to install? I never selected this kernel, the installer did.

Regards,

George

Linux Mint 20.3 Unsa Cinnamon 64-bit, Asus Vanguard B85, Intel Core i7 4770S

gwi: Level 2; Posts: 96; Joined: Mon Jun 04, 2012 4:20 pm

Re: Mint 15: kernel panic, cannot open root device

Post

by gwi » Sat Jun 29, 2013 7:04 am

WharfRat wrote:Have you tried chrooting to it Maybe generating another grub menu

Yes, I did, without success.

eanfrid wrote:Why did you choose to install an EFI/signed kernel ? On a 80GB SSD with a MBR partitioning scheme

Thank you for making this remark! I still don’t know why the installer installed en EIF/signed kernel, but I noticed that in the grub menu there was an entry «Previous Linux versions». That sounded a bit strange, since I repartitioned and formatted my drives. «Previous Linux versions» appeared to be a submenu, containing the generic kernel. That one booted normally.

After installing updates, the kernel version is now 3.8.0-25, instead of 3.8.0-19. Now the generic kernel is in the grub menu, and 3.8.0-19 efi/signed is in the submenu «Previous Linux versions» (although I uninstalled all four packages of kernel 3.8.0-19).

So, to summarize: I don’t know what happened, but your remark on EFI put me in the direction of finding the solution. Thanks for your help!

Regards,

George

Linux Mint 20.3 Unsa Cinnamon 64-bit, Asus Vanguard B85, Intel Core i7 4770S

elfaure

Re: Mint 15: kernel panic, cannot open root device

Post

by elfaure » Sat Jun 29, 2013 7:12 am

Hey-
I’m new to Linux but not Android, so please take what I say here as fairly newbe but I noticed that your /dev/sda is an SSD. On thing I found out is that Mint 15 stock does not support exFAT format out of the box. You have to install exFAT support manually. Is your SSD exFAT? I got a similar error trying to mount a 64GB flash card and it only mounted after installling exFAT support. Maybe the live CD has this built in, yet the OS does not?? Just a thought.

elfaure

Re: [SOLVED] Mint 15: kernel panic, cannot open root device

Post

by elfaure » Sat Jun 29, 2013 8:29 am

Just thought I’d throw it out there. All the micro SDXC (>= 64GB) flash cards (Sandisk, Kingston, Patriot, Sony, Polaroid) come exFAT right outta the box so they are Windows compatible (XP needs an exFAT patch). I thought the same may be true for SSDs but it looks like you’ve formatted yours ext4.

eanfrid

Re: Mint 15: kernel panic, cannot open root device

Post

by eanfrid » Sun Jun 30, 2013 1:59 pm

gwi wrote:

eanfrid wrote:Why did you choose to install an EFI/signed kernel ? On a 80GB SSD with a MBR partitioning scheme

Thank you for making this remark!
…
So, to summarize: I don’t know what happened, but your remark on EFI put me in the direction of finding the solution. Thanks for your help!

It was indeed the underlying implicit meaning of my remark: use a «normal» kernel

petri0: Level 2; Posts: 65; Joined: Wed Mar 28, 2012 5:40 pm

Источник

Description
===========
An kvm instance failed to boot with a kernel panic after hitting this error:

VFS: Cannot open root device «LABEL=cloudimg-rootfs» or unknown-block(0,0): error -6

Steps to reproduce
==================
This doesn’t reproduce reliably, it seems to be a race condition.

* I started an instance through the API. It had not attached storage, and was attached to a single network. It used an Ubuntu Xenial cloud image which booted successfully on a different instance on a different compute node.

Expected Result
===============
* I expected the instance to boot successfully

Actual Result
=============
* The instance failed to boot with a kernel panic:
http://pastebin.ubuntu.com/23911493/

* I used virsh destroy to stop that instance, then started it again through the API, and it worked.

Environment
===========
xenial/newtown/kvm/openvswitch, no attached storage.

ii nova-common 2:14.0.1-0ubuntu1~cloud0 all OpenStack Compute — common files
ii nova-compute 2:14.0.1-0ubuntu1~cloud0 all OpenStack Compute — compute node base
ii nova-compute-kvm 2:14.0.1-0ubuntu1~cloud0 all OpenStack Compute — compute node (KVM)
ii nova-compute-libvirt 2:14.0.1-0ubuntu1~cloud0 all OpenStack Compute — compute node libvirt support
ii python-nova 2:14.0.1-0ubuntu1~cloud0 all OpenStack Compute Python libraries
ii python-novaclient 2:6.0.0-0ubuntu1~cloud0 all client library for OpenStack Compute API — Python 2.7
ii libvirt-bin 1.3.1-1ubuntu10.6 amd64 programs for the libvirt library
ii libvirt0:amd64 1.3.1-1ubuntu10.6 amd64 library for interfacing with different virtualization systems
ii nova-compute-libvirt 2:14.0.1-0ubuntu1~cloud0 all OpenStack Compute — compute node libvirt support
ii python-libvirt 1.3.1-1ubuntu1 amd64 libvirt Python bindings

Источник

[SOLVED] Mint 15: kernel panic, cannot open root device

Re: Mint 15: kernel panic, cannot open root device

Re: Mint 15: kernel panic, cannot open root device

Re: Mint 15: kernel panic, cannot open root device

Re: Mint 15: kernel panic, cannot open root device

Re: Mint 15: kernel panic, cannot open root device

Re: Mint 15: kernel panic, cannot open root device

Re: Mint 15: kernel panic, cannot open root device

Re: [SOLVED] Mint 15: kernel panic, cannot open root device

Re: Mint 15: kernel panic, cannot open root device

Читайте также: