FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 10-04-2012, 12:42 AM
Stephen Powell
 
Default Bug#689558: initramfs-tools with MODULES=dep does not work with i2o hardware RAID controller

Package: initramfs-tools
Version: 0.107

My i386 PC has an i2o hardware RAID controller as the only "hard disk".
The block special files are defined as follows:

brw-rw---T 1 root disk 80, 0 Sep 23 15:24 /dev/i2o/hda
brw-rw---T 1 root disk 80, 1 Sep 23 15:24 /dev/i2o/hda1
brw-rw---T 1 root disk 80, 2 Sep 23 15:24 /dev/i2o/hda2
brw-rw---T 1 root disk 80, 5 Sep 23 15:24 /dev/i2o/hda5
brw-rw---T 1 root disk 80, 6 Sep 23 15:24 /dev/i2o/hda6
brw-rw---T 1 root disk 80, 7 Sep 23 15:24 /dev/i2o/hda7
brw-rw---T 1 root disk 80, 8 Sep 23 15:24 /dev/i2o/hda8

When using MODULES=dep, I get the following error messages from
"update-initramfs -uk $(uname -r)"

update-initramfs: Generating /boot/initrd.img-3.2.0-3-rt-686-pae
mkinitramfs: for root /dev/i2o/hda6 missing i /sys/block/ entry
mkinitramfs: workaround is MODULES=most
mkinitramfs: Error please report the bug
update-initramfs: failed for /boot/initrd.img-3.2.0-3-rt-686-pae with 1.

Here is the listing of the /sys/block directory:

# cd /sys/block
# ls -l
total 0
lrwxrwxrwx 1 root root 0 Oct 3 20:32 fd0 -> ../devices/platform/floppy.0/block/fd0
lrwxrwxrwx 1 root root 0 Sep 23 15:24 i2o!hda -> ../devices/pci0000:00/0000:00:02.0/0000:01:1d.0/0000:02:02.0/iop0/0:207/block/i2o!hda
lrwxrwxrwx 1 root root 0 Oct 3 20:32 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx 1 root root 0 Oct 3 20:32 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx 1 root root 0 Oct 3 20:32 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx 1 root root 0 Oct 3 20:32 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx 1 root root 0 Oct 3 20:32 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx 1 root root 0 Oct 3 20:32 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx 1 root root 0 Oct 3 20:32 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx 1 root root 0 Oct 3 20:32 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx 1 root root 0 Oct 3 20:32 sr0 -> ../devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sr0

I notice that the entry for the hard disk (i2o!hda) contains a special character:
the exclamation point. Could that be the cause of the trouble? (Or part of the
trouble?) The exclamation point is often used in the shell as a character to
access command history.

The following kernel modules are currently loaded:

Module Size Used by
tun 17832 2
bnep 17288 2
rfcomm 32694 0
bluetooth 107841 10 rfcomm,bnep
rfkill 18484 3 bluetooth
crc16 12327 1 bluetooth
ppdev 12651 0
lp 12797 0
binfmt_misc 12813 1
nfsd 173714 2
nfs 270075 0
nfs_acl 12463 2 nfs,nfsd
auth_rpcgss 32227 2 nfs,nfsd
fscache 31978 1 nfs
lockd 61351 2 nfs,nfsd
sunrpc 147955 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
loop 21911 0
snd_ca0106 33022 2
snd_ac97_codec 84169 1 snd_ca0106
snd_seq_midi 12744 0
snd_seq_midi_event 13124 1 snd_seq_midi
snd_rawmidi 22479 2 snd_seq_midi,snd_ca0106
snd_pcm 53344 2 snd_ac97_codec,snd_ca0106
snd_page_alloc 12867 2 snd_pcm,snd_ca0106
snd_seq 39489 2 snd_seq_midi_event,snd_seq_midi
evdev 17165 7
snd_seq_device 13016 3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer 22359 2 snd_seq,snd_pcm
snd 42695 11 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_rawmi di,snd_ac97_codec,snd_ca0106
soundcore 12921 1 snd
ac97_bus 12462 1 snd_ac97_codec
parport_pc 22036 1
psmouse 54893 0
serio_raw 12769 0
parport 31258 3 parport_pc,lp,ppdev
iTCO_wdt 16917 0
iTCO_vendor_support 12632 1 iTCO_wdt
i2c_i801 12670 0
pcspkr 12515 0
intel_rng 12501 0
rng_core 12580 1 intel_rng
i2c_core 19116 1 i2c_i801
shpchp 26717 0
container 12525 0
e7xxx_edac 12637 0
edac_core 30066 3 e7xxx_edac
button 12817 0
processor 27565 0
thermal_sys 17752 1 processor
ext3 142489 4
mbcache 12897 1 ext3
jbd 51409 1 ext3
i2o_block 12824 6
sg 21445 0
sr_mod 17468 0
cdrom 34813 1 sr_mod
ata_generic 12439 0
floppy 48166 0
pata_pdc202xx_old 12771 0
e100 31406 0
mii 12595 1 e100
i2o_core 30975 1 i2o_block
ata_piix 21175 0
libata 124986 3 ata_piix,pata_pdc202xx_old,ata_generic
uhci_hcd 26401 0
ehci_hcd 35477 0
scsi_mod 135198 3 libata,sr_mod,sg
usbcore 108302 3 ehci_hcd,uhci_hcd
usb_common 12338 1 usbcore

Obviously not all of these need to be in the initial RAM file system.

When using MODULES=most, everything works fine.

--
.'`. Stephen Powell
: :' :
`. `'`
`-


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1174598773.259884.1349311362011.JavaMail.root@md01 .wow.synacor.com">http://lists.debian.org/1174598773.259884.1349311362011.JavaMail.root@md01 .wow.synacor.com
 

Thread Tools




All times are GMT. The time now is 04:02 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org