Bug 207423 - LSPP: unable to reboot pseries after installing today's rawhide.
Summary: LSPP: unable to reboot pseries after installing today's rawhide.
Keywords:
Status: CLOSED DUPLICATE of bug 206453
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: powerpc
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-21 00:33 UTC by IBM Bug Proxy
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-21 15:44:32 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 27404 0 None None None Never

Description IBM Bug Proxy 2006-09-21 00:33:40 UTC 
LTC Owner is: latten.com
LTC Originator is: latten.com


Problem description:


I installed today's (sept 20, 2006) rawhide on an lpar/pseries, power5. 
After installing, system rebooted. During reboot, received the
following:

usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda5" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


Is it because it is looking for "sda5", instead of "/dev/sda5"?
/dev/sda5 is my root partition.

This also happened with yesterday's rawhide.
Comment 1 Jeremy Katz 2006-09-21 15:44:32 UTC 

*** This bug has been marked as a duplicate of 206453 ***
Note You need to log in before you can comment on or make changes to this bug.