Your message dated Mon, 23 Nov 2015 12:48:47 +0000 with message-id <1448282927.2768.6.camel@decadent.org.uk> and subject line Re: Bug#787554: initramfs-tools: failed to start /dev/mdx, Usage: readlink, Can't find /root in /etc/fstab has caused the Debian Bug report #787554, regarding initramfs-tools: failed to start /dev/mdx, Usage: readlink, Can't find /root in /etc/fstab to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 787554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787554 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: initramfs-tools: failed to start /dev/mdx, Usage: readlink, Can't find /root in /etc/fstab
- From: Jochen Pawletta <jochen@hin.de>
- Date: Tue, 02 Jun 2015 19:45:53 +0200
- Message-id: <20150602174553.9876.71604.reportbug@joshua.hin.de>
Package: initramfs-tools Version: 0.120 Severity: important Hi I have some problems booting with initrd, it doesn't look linke other bug reports I saw, so here my bug report ... :-) Screenshot: http://jochen.hin.de/diverses/initramfs-tools-bug.jpg First the kernel has already startet /dev/md2 and /dev/md3 on my system. So could I ignore the messages which try to "Assemblling MD array"? Then there seems to be a problem with a readlink-call: "Usage: readlink ..." Then it says "Can't find /root in /etc/fstab" After than I am stuck in BusyBox. The Raid is already startet, the Root FS is /dev/md2 and ready to mount. The /usr FS is on a LVM (on /dev/md3) which is not started yet. I could manualy mount the Root FS and the /usr FS, also /dev, /proc, /sys (to /root) but I don't know how to initiate the init from there. (chroot and start the "real" init) So I now use my old initrd and my old kernel (2.6.32) to boot my system. (from Wheezy/oldstable) Could you help please? Jochen -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 16M May 29 19:11 /boot/initrd.img-3.16.0-4-686-pae -rw-r--r-- 1 root root 11M May 30 08:17 /boot/initrd.img-3.2.0-4-686-pae -rw-r--r-- 1 root root 11M May 30 08:18 /boot/initrd.img-3.2.0-4-686-pae2 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae root=UUID=84e9ea7c-4cb0-4c08-a024-278c79dab426 ro nmi_watchdog=1 nouveau.nomodeset=0 vga=791 -- resume # RESUME=/dev/sda2 #RESUME='UUID=89c6c0b8-7dc5-474e-ad93-67c9fa9c1ab2' -- /proc/filesystems ext3 fuseblk -- lsmod Module Size Used by tcp_diag 12400 0 inet_diag 17001 1 tcp_diag binfmt_misc 12813 1 xt_multiport 12492 2 ipt_REJECT 12454 1 ipt_LOG 12533 1 nf_conntrack_ipv4 13726 2 nf_defrag_ipv4 12443 1 nf_conntrack_ipv4 xt_conntrack 12601 2 nf_conntrack 43121 2 xt_conntrack,nf_conntrack_ipv4 xt_owner 12391 3 xt_tcpudp 12506 6 iptable_filter 12488 1 ip_tables 17079 1 iptable_filter x_tables 18158 8 ip_tables,iptable_filter,xt_tcpudp,xt_owner,xt_conntrack,ipt_LOG,ipt_REJECT,xt_multiport cpufreq_stats 12762 0 cpufreq_userspace 12520 0 cpufreq_conservative 12987 0 cpufreq_powersave 12422 0 nfsd 173901 2 nfs 265953 0 nfs_acl 12463 2 nfs,nfsd auth_rpcgss 32143 2 nfs,nfsd fscache 31978 1 nfs lockd 61373 2 nfs,nfsd sunrpc 148000 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd raid456 47757 1 async_raid6_recov 12518 1 raid456 async_memcpy 12363 2 async_raid6_recov,raid456 async_pq 12542 2 async_raid6_recov,raid456 ves1x93 12825 0 raid6_pq 86874 2 async_pq,async_raid6_recov async_xor 12390 3 async_pq,async_raid6_recov,raid456 xor 21608 1 async_xor async_tx 12540 5 async_xor,async_pq,async_memcpy,async_raid6_recov,raid456 pl2303 17094 0 usbserial 27365 1 pl2303 radeon 644939 0 ttm 47786 1 radeon psmouse 59609 0 drm_kms_helper 22738 1 radeon drm 146387 3 drm_kms_helper,ttm,radeon serio_raw 12803 0 dvb_ttpci 71302 6 stv0299 13144 1 pcspkr 12515 0 power_supply 13283 1 radeon i2c_i801 12670 0 i2c_algo_bit 12713 1 radeon ttpci_eeprom 12413 1 dvb_ttpci saa7146_vv 27541 1 dvb_ttpci saa7146 17218 2 saa7146_vv,dvb_ttpci dvb_core 68110 2 stv0299,dvb_ttpci videobuf_dma_sg 13055 1 saa7146_vv videobuf_core 17561 2 videobuf_dma_sg,saa7146_vv videodev 61658 1 saa7146_vv iTCO_wdt 16945 0 media 13692 1 videodev snd_hda_codec_hdmi 26352 1 evdev 17225 3 iTCO_vendor_support 12632 1 iTCO_wdt i2c_core 19116 10 videodev,ttpci_eeprom,i2c_algo_bit,i2c_i801,stv0299,drm,dvb_ttpci,drm_kms_helper,radeon,ves1x93 snd_hda_codec_via 32200 1 acpi_cpufreq 12807 0 mperf 12421 1 acpi_cpufreq snd_hda_intel 21786 0 snd_hda_codec 63477 3 snd_hda_intel,snd_hda_codec_via,snd_hda_codec_hdmi snd_hwdep 12943 1 snd_hda_codec snd_pcm 53461 3 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi snd_page_alloc 12867 2 snd_pcm,snd_hda_intel snd_timer 22356 1 snd_pcm snd 42761 7 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_via,snd_hda_codec_hdmi soundcore 12921 1 snd button 12817 0 processor 27565 1 acpi_cpufreq shpchp 26717 0 asus_atk0110 17113 0 thermal_sys 17752 1 processor coretemp 12770 0 fuse 52176 1 autofs4 22784 2 ext3 134152 11 mbcache 12938 1 ext3 jbd 47281 1 ext3 dm_mod 57386 30 raid1 26218 1 md_mod 85719 4 raid1,raid456 osst 47240 0 st 34317 0 ch 16776 0 ata_generic 12439 0 sg 21476 0 sd_mod 35425 12 usbhid 31554 0 hid 64284 1 usbhid crc_t10dif 12332 1 sd_mod uhci_hcd 22337 0 pata_jmicron 12432 0 ehci_hcd 39631 0 ahci 24917 8 libahci 18373 1 ahci libata 125014 4 libahci,ahci,pata_jmicron,ata_generic lpfc 404213 0 aic7xxx 98303 1 scsi_transport_fc 33961 1 lpfc scsi_tgt 13392 1 scsi_transport_fc scsi_transport_spi 19198 1 aic7xxx atl1e 27339 0 usbcore 104555 6 ehci_hcd,uhci_hcd,usbhid,usbserial,pl2303 scsi_mod 135081 11 scsi_tgt,scsi_transport_fc,scsi_transport_spi,aic7xxx,lpfc,libata,sd_mod,sg,st,ch,osst usb_common 12338 1 usbcore -- /etc/initramfs-tools/modules libata md -- /etc/kernel-img.conf # This is a sample /etc/kernel-img.conf file # See kernel-img.conf(5) for details # If you want the symbolic link (or image, if move_image is set) to be # stored elsewhere than / set this variable to the dir where you # want the symbolic link. Please note that this is not a Boolean # variable. This may be of help to loadlin users, who may set both # this and move_image. Defaults to /. This can be used in conjunction # with all above options except link_in_boot, which would not make # sense. (If both image_dest and link_in_boot are set, link_in_boot # overrides). image_dest = / # This option manipulates the build link created by recent kernels. If # the link is a dangling link, and if a the corresponding kernel # headers appear to have been installed on the system, a new symlink # shall be created to point to them. #relink_build_link = YES # If set, the preinst shall silently try to move /lib/modules/version # out of the way if it is the same version as the image being # installed. Use at your own risk. #clobber_modules = NO # If set, does not prompt to continue after a depmod problem in the # postinstall script. This facilitates automated installs, though it # may mask a problem with the kernel image. A diag‐ nostic is still # issued. This is unset be default. # ignore_depmod_err = NO # These setting are for legacy postinst scripts only. newer postinst # scripts from the kenrel-package do not use them 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=no -- /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] md3 : active raid5 sda4[0] sdd4[4] sdc4[3] sdb4[2] 5843400192 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU] md2 : active raid1 sda3[0] sdb3[2] 5241844 blocks super 1.2 [2/2] [UU] unused devices: <none> -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: busybox dmsetup fsck fuse keymap klibc kmod lvm2 mdadm ntfs_3g resume thermal udev -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools depends on: ii cpio 2.11+dfsg-4.1 ii klibc-utils 2.0.4-2 ii kmod 18-3 ii module-init-tools 18-3 ii udev 215-17 Versions of packages initramfs-tools recommends: pn busybox | busybox-initramfs | busybox-static <none> Versions of packages initramfs-tools suggests: ii bash-completion 1:2.1-4 -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 787554-done@bugs.debian.org
- Subject: Re: Bug#787554: initramfs-tools: failed to start /dev/mdx, Usage: readlink, Can't find /root in /etc/fstab
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Mon, 23 Nov 2015 12:48:47 +0000
- Message-id: <1448282927.2768.6.camel@decadent.org.uk>
- In-reply-to: <20150602174553.9876.71604.reportbug@joshua.hin.de>
- References: <20150602174553.9876.71604.reportbug@joshua.hin.de>
On Tue, 2015-06-02 at 19:45 +0200, Jochen Pawletta wrote: [...] > -- /etc/initramfs-tools/initramfs.conf > MODULES=most > BUSYBOX=y > KEYMAP=n > COMPRESS=gzip > DEVICE= > NFSROOT=auto The configuration says you want busybox in the initramfs... [...] > Versions of packages initramfs-tools recommends: > pn busybox | busybox-initramfs | busybox-static but you don't have a busybox package installed. Instead, you have an unpackaged version of busybox that is too old. If you install Debian's busybox package and run update-initramfs -u, you should get a working initramfs. Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---