Bug 127305 - cannot boot fedora off of ieee1394 drive
Summary: cannot boot fedora off of ieee1394 drive
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-07-06 12:58 UTC by Jason Duerstock
Modified: 2015-01-04 22:07 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2006-05-04 12:57:32 UTC

Attachments (Terms of Use)

Description Jason Duerstock 2004-07-06 12:58:06 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a1)

Description of problem:
After setting up the modules.conf and building the initrd to include
sbp2, I cannot use a ieee1394 drive as my root disk.

I get the following boot log:

VFS: Mounted root (ext2 filesystem).
Red Hat nash version 3.5.22 starting
Mounted /proc filesystem
Mounting sysfs
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Loading ieee1394.ko module
Loading ohci1394.ko module
ohci1394: $Rev: 1203 $ Ben Collins <bcollins@debian.org>
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10] 
MMIO=[f7ffb000-f7ffb7ff] Max Packet=[2048]
Loading sbp2.ko module
sbp2: $Rev: 1205 $ Ben Collins <bcollins@debian.org>
Loading jbd.ko
Loading ext3.ko
Creating block devices
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Freeing unused kernel memory: 144k freed
Kernel panic: No init found.  Try passing init= option to kernel.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. move root partition to ieee1394 drive
2. set up modules.conf to support sbp2
3. rebuild initrd
4. boot

Actual Results:  See description above

Expected Results:  system should boot successfully

Additional info:

Comment 3 Dave Jones 2005-10-06 00:08:40 UTC
any luck with later kernels ?

Comment 4 John Thacker 2006-05-04 12:57:32 UTC
No respose from reporter.  Closing.

Note You need to log in before you can comment on or make changes to this bug.