Package: initramfs-tools
Version: 0.107
Severity: important
File: /usr/sbin/mkinitramfs

Dear Maintainer,

After upgrading the packages on my system it failed to boot because
initramfs couldn't find the rootfs. The
/dev/disk/ directory was missing. I then noticed udevadm failed with
a socket error that an address family wasn't
found.

Comparing the old and new initramfs image I noticed that the module
"unix" wasn't included in the /conf/modules
file anymore.

I have manually added unix to /etc/initramfs-tool/modules file to get
the system to boot.

-- Package-specific info:
-- initramfs sizes
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.2.7 root=UUID=5fe9420c-42fb-4d1c-ac21-81bdcb0f64be ro

-- resume
RESUME=UUID=7b5bd194-57b8-4b74-86e0-2cbc6c28f9e1
-- /proc/filesystems
ext4
vfat

-- lsmod
Module Size Used by
iptable_nat 3840 1
nf_nat 14357 1 iptable_nat
xt_TCPMSS 3127 4
xt_tcpmss 1417 4
iptable_mangle 1528 1
xt_tcpudp 2351 6
nf_conntrack_ipv4 11001 5 nf_nat,iptable_nat
nf_defrag_ipv4 1187 1 nf_conntrack_ipv4
xt_state 1175 2
nf_conntrack 54597 4 xt_state,nf_conntrack_ipv4,nf_nat,iptable_nat
iptable_filter 1368 1
ip_tables 16072 3 iptable_filter,iptable_mangle,iptable_nat
x_tables 16003 8
ip_tables,iptable_filter,xt_state,xt_tcpudp,iptabl e_mangle,xt_tcpmss,xt_TCPMSS,iptable_nat
pppoe 9898 2
pppox 1714 1 pppoe
af_packet 24934 2
ppp_generic 18048 6 pppox,pppoe
slhc 4977 1 ppp_generic
ipv6 265541 18
nls_iso8859_1 4301 1
nls_cp437 5833 1
vfat 9743 1
fat 47522 1 vfat
usbhid 33948 0
hid 82563 1 usbhid
loop 16894 0
8250_pnp 4599 0
xhci_hcd 76626 0
8250 19989 1 8250_pnp
ehci_hcd 39586 0
serial_core 17489 1 8250
rtc_cmos 8264 0
r8169 45968 0
i2c_i801 7909 0
i2c_core 17107 1 i2c_i801
e1000e 136645 0
usbcore 136745 4 ehci_hcd,xhci_hcd,usbhid
usb_common 866 1 usbcore
ext4 265072 1
crc16 1303 1 ext4
jbd2 48164 1 ext4
mbcache 5473 1 ext4
raid1 24658 3
md_mod 96065 4 raid1
sd_mod 32342 8
crc_t10dif 1276 1 sd_mod
ahci 19501 6
libahci 18255 1 ahci
libata 135458 2 libahci,ahci
unix 25011 56

-- /etc/initramfs-tools/modules
unix
sd_mod
raid1

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=yes

-- /proc/mdstat
Personalities : [raid1]
md125 : active raid1 sda3[0] sdb3[2]
16777144 blocks super 1.0 [2/2] [UU]

md126 : active raid1 sda2[0] sdb2[2]
107994040 blocks super 1.0 [2/2] [UU]
bitmap: 0/1 pages [0KB], 65536KB chunk

md127 : active (auto-read-only) raid1 sda1[0] sdb1[2]
262132 blocks super 1.0 [2/2] [UU]
bitmap: 0/1 pages [0KB], 65536KB chunk

unused devices: <none>

-- /sys/block
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
md125
md126
md127
sda
sdb

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:

/usr/share/initramfs-tools/hooks:
busybox
dmsetup
keymap
klibc
kmod
mdadm
thermal
udev


-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (950, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.7 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initramfs-tools depends on:
ii cpio 2.11-8
ii klibc-utils 2.0.1-1
ii kmod 9-2
ii module-init-tools 9-2
ii udev 175-7

Versions of packages initramfs-tools recommends:
ii busybox 1:1.20.0-7

Versions of packages initramfs-tools suggests:
ii bash-completion 1:2.0-1

-- Configuration Files:
/etc/initramfs-tools/update-initramfs.conf changed:
update_initramfs=yes
backup_initramfs=yes


-- no debconf information


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAAb3RxNOuL-FimqkgQ4Sr-oRq4PYs4pu8w=S-T-Sj5iq1gkPvw@mail.gmail.com

Now that I think about it, the reason I made unix a module why back
was because initramfs gave errors that it wasn't a module during boot.
I have since tracked down the change to the udev package as I was
unaware that the udev package was responsible for the force loading of
the unix module in the first place.

What worries me is that anybody upgrading an old Debian install with a
custom kernel and modular unix will end up with an unbootable system
after upgrading to wheezy. I will raise this issue with the udev
maintainer.


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAAb3RxPw-UKy6hap56+mK3yZJO2ObuZ3D4qobO5d2nndZaSNEw@mail.gma il.com">http://lists.debian.org/CAAb3RxPw-UKy6hap56+mK3yZJO2ObuZ3D4qobO5d2nndZaSNEw@mail.gma il.com

On Thu, Oct 04, 2012 at 05:54:26AM -0400, Avernar wrote:
>
> What worries me is that anybody upgrading an old Debian install with a
> custom kernel and modular unix will end up with an unbootable system
> after upgrading to wheezy. I will raise this issue with the udev
> maintainer.

This issue has loooong been decided, if you are concerned,
please propose a patch for the wheezy release notes.

Modular unix is bad for cache-hits performance reasons!

Best,

--
maks


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20121004101246.GF31605@vostochny.stro.at">http://lists.debian.org/20121004101246.GF31605@vostochny.stro.at