jessie 3.16.0-4-686-pae kernel stuck at initramfs prompt due to ata_piix module
Upon upgrading from wheezy to jessie using linux-image-3.16.0-4-686-pae_3.16.7-ckt11-1_i386.deb for the kernel, I discovered that I would get stuck at an initramfs prompt complaining about md arrays not being found. When inspecting the directories, the entire /dev/disk directory was missing. So of course mdarray could not find the devices to start and array. None of the underlying hard drives were being found. The relevant part of dmsg output is the following. ata_piix :00:12.1: version 2.13 scsi2: error handler thread failed to spawn, error = -4 ata_piix: probe of :00:12.1 failed with error -12 After playing around for a bit I discovered that I could work around the problem by doing the following sequence. 1. rmmod ata_piix 2. modprobe ata_piix 3. repeat 1-2 until dmsg stops listing the ata_piix errors, and /dev/disk appears 4. type exit into the initramfs prompt, and debian boots just fine Usually I only have to reload the module once, but occasionally I need to do it two or three times. At this point, I think that this is a kernel bug. This behavior never happened in the 3.2.0-4-686-pae kernel in wheezy. I am not sure whom to contact or what to do next to fix this problem. Thanks in advance for any advice or help, Neil -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558d5cba.8010...@ohiogray.org
Re: initramfs prompt
Darac Marjal wrote: add root=device: Hello Darac. # Partiton table: #1 pri ? sda1 ? ? # make by OS automatically #5 log 0.45 sda5 B ext4 / #6 log 12.0 sda6 ext4 /home #7 log 9.6sda7 ext4 /usr #8 log 3.2sda8 ext4 /var #9 log 0.8sda9 ext4 /swap #10 log 0.5sda10 ext4 /tmp #11 log 1.0sda11 ext4 /install #2 pri 2.5sda2 fat32 /windows --- my partition table is from sda5 - sda2, sda1 was make by OS automatically (from dmesg: [ 2.484098] sda: sda1 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda2). I put the bootflag on a logical partition (sda5), the debian installer warned me, but i ignored it. After the installation, for fix it, i make on the commandline of Grub: parttool hd0,2 boot+ [to make the selected partition be the active (bootable) partition on its disk, clearing the active flag on all other partitions. - GNU GRUB Manual 2.00.html#parttool] # Grub boot menu completely after installation: load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos5)' search --no-floppy --fs-uuid --set=root 6d0c6734-04ea-406d-8b23-e07ae7396fdd echo 'Loading Linux 3.2.0-4-686-pae ...' linux /boot/vmlinuz- 3.2.0-4-686-pae root=UUID=6d0c6734-04ea-406d-8b23-e07ae7396fdd ro single echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-4-686-pae - In this constellation the initiation isn't sucessfully, only reach pcmcia-sockets ..., then the screen turns black and the initiation stops without a prompt. Without root=UUID=6d0c6734-04ea-406d-8b23-e07ae7396fdd it reach the initramfs prompt. root=/dev/sda5 in the boot menu does the same as root=UUID=6d0c6734-04ea-406d-8b23-e07ae7396fdd. Others as hd0,msdos5, hd0,5, /dev/sda2, label=rootfs, Label=rootfs reach only the initramfs prompt. (I have found rootfs in /proc/mount: rootfs / rootfs rw 0 0) With '--set=root 430a2f6f-b3ae-480f-959f-60568d6512f3' and 'root=UUID=430a2f6f- b3ae-480f-959f-60568d6512f3' (=sda2) not initiate and give message: error: file not found. error: you need to load the kernel first. - # output from ls (initramfs) ls bin conf dev etc init lib proc root run sbin scripts sys tmp var (initramfs) ls /root empty (initramfs) ls /scripts functions init-bottom init-top local local-premount nfs (initramfs) ls /sys block bus class dev devices firmware fs hypervisor kernel module power (initramfs) ls /conf arch.conf /conf.d/resume initramfs.conf (initramfs) ls /etc ld.so.cache ld.so.conf /ld.so.conf.d/ /modprobe.d/ /udev/udev.conf (initramfs) ls /init /init empty Julien wrote: locate harddrive: Hello Julien (initramfs) sfdisk -l /bin/sh: sfdisk: not found #and (initramfs) cd /bin (initramfs) ln -s busybox sfdisk (initramfs) sfdisk -l /bin/sh: sfdisk: applet not found - # Here the output of 'help' from busybox: (initramfs) help Built-in commands: . : [ [[ alias bg break cd chdir command continue echo eval exec exit export false fg getopts hash help jobs kill let local printf pwd read readonly return set shift source test times trap true type ulimit umask unalias unset wait [ [[ adjtimex ar arp arping ash awk basename blockdev brctl bunzip2 bzcat bzip2 cal cat chgrp chmod chown chroot chvt clear cmp cp cpio cttyhack cut date dc dd deallocvt depmod df diff dirname dmesg dnsdomainename dos2unix du dumpkmap dumpleases echo egrep env expand expr false fgrep find fold free freeramdisk ftpget ftpput getopt getty grep groups gunzip gzip halt head hexdump hostid hostname httpd hwclock id ifconfig init insmod ionice ip ipcalc kill killall klogd last less ln loadfont loadkmap logger login logname logread losetup ls lsmod lzcat lzma md5sum mdev microcom mkdir mkfifo nknod mkswap mktemp modinfo modprobe more mount mt mv nameif nc netstat nslookup od openvt patch pidof ping ping6 pivot_root poweroff printf ps pwd rdate readlink realpath reboot renice reset rev rm rmdir rmmod route rpm rpm2cpio run-parts sed seq setkeycodes setsid sh sha1sum sha256sum sha512sum sleep sort start-stop-daemon stat strings stty swapoff swapon switch_root sync sysctl syslogd tac tail tar taskset tee telnet test tftp time timeout top touch tr traceroute traceroute6 true tty udhcpc udhcpd umount uname uncompress unexpand uniq unix2dos unlzma
initramfs prompt
Hello. I have a laptop without cdrom or floppy and it isn't usb-bootable. After an unsuccessfull installation mininal of debian wheezy 7.6 i got only a initramfs prompt, busybox and little programs in /sbin and /bin. I can't write on the disk, all changes get lost after reboot. Can i and when how write to the disk ? Here some output: #Grub menu: GNU GRUB ... search --fs-uuid echo ... linux /boot/vmlinuz-3.2.0-4-686-pae ro ... #boot: ... [ 0.927417] Simple Boot Flag at 0x6e set to 0x1 ... [ 0.965249] ERST: Table is not found ! [ 0.965312] GHES: HEST is not enabled ! ... [ 2.129223] sd 0:0:0:0: [sda] Write Protect is off [ 2.129471] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ... [ 2.484098] sda: sda1 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda2 ... Begin: Loading essential drivers ... done Begin: Running /scripts/init-premount ... done ... modprobe: module unknown not found in modules.dep mount: can't read '/etc/fstab': No such a file or directory Begin: Running /scripts/local-bottom ... done done Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such a file or directory done Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg. [ 4.899187] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ... BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash) Enter 'help' ... /bin/sh: can't access tty: job control turned off (initramfs) _ Bye -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/aaad2d0fdf31192f09b774865a1fd...@andaluciajunta.es
Re: initramfs prompt
On Fri, Nov 07, 2014 at 12:29:31PM +0100, Achim Spreen wrote: Hello. I have a laptop without cdrom or floppy and it isn't usb-bootable. After an unsuccessfull installation mininal of debian wheezy 7.6 i got only a initramfs prompt, busybox and little programs in /sbin and /bin. I can't write on the disk, all changes get lost after reboot. Can i and when how write to the disk ? Here some output: #Grub menu: GNU GRUB ... search --fs-uuid echo ... linux /boot/vmlinuz-3.2.0-4-686-pae ro ... #boot: ... [ 0.927417] Simple Boot Flag at 0x6e set to 0x1 ... [ 0.965249] ERST: Table is not found ! [ 0.965312] GHES: HEST is not enabled ! ... [ 2.129223] sd 0:0:0:0: [sda] Write Protect is off [ 2.129471] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ... [ 2.484098] sda: sda1 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda2 ... Begin: Loading essential drivers ... done Begin: Running /scripts/init-premount ... done ... modprobe: module unknown not found in modules.dep mount: can't read '/etc/fstab': No such a file or directory Begin: Running /scripts/local-bottom ... done done Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such a file or directory done Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg. [ 4.899187] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ... BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash) Enter 'help' ... /bin/sh: can't access tty: job control turned off (initramfs) _ OK, so initramfs hasn't been able to find your root filesystem. I thought that generally resulted in the kernel panicking, but apparently not. I notice that you haven't told the kernel where your root filesystem is, though, so either autodetection hasn't worked or there is no autodetection. I would suggest adding root=device to the end of the linux /boot/vmlinuz-3.2.0-4-686-pae ro line, where device is any valid way of telling linux where the device is (so you could say /dev/sda1, LABEL=rootfs, UUID=1234-567... etc etc). If that works and you get into your system, re-run sudo update-grub to fix the grub configuration. Bye -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/aaad2d0fdf31192f09b774865a1fd...@andaluciajunta.es signature.asc Description: Digital signature
Re: initramfs prompt
2014-11-07 14:06 GMT+01:00 Darac Marjal mailingl...@darac.org.uk: On Fri, Nov 07, 2014 at 12:29:31PM +0100, Achim Spreen wrote: Hello. I have a laptop without cdrom or floppy and it isn't usb-bootable. After an unsuccessfull installation mininal of debian wheezy 7.6 i got only a initramfs prompt, busybox and little programs in /sbin and /bin. I can't write on the disk, all changes get lost after reboot. Can i and when how write to the disk ? Here some output: #Grub menu: GNU GRUB ... search --fs-uuid echo ... linux /boot/vmlinuz-3.2.0-4-686-pae ro ... #boot: ... [ 0.927417] Simple Boot Flag at 0x6e set to 0x1 ... [ 0.965249] ERST: Table is not found ! [ 0.965312] GHES: HEST is not enabled ! ... [ 2.129223] sd 0:0:0:0: [sda] Write Protect is off [ 2.129471] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ... [ 2.484098] sda: sda1 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda2 ... Begin: Loading essential drivers ... done Begin: Running /scripts/init-premount ... done ... modprobe: module unknown not found in modules.dep mount: can't read '/etc/fstab': No such a file or directory Begin: Running /scripts/local-bottom ... done done Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such a file or directory done Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg. [ 4.899187] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ... BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash) Enter 'help' ... /bin/sh: can't access tty: job control turned off (initramfs) _ OK, so initramfs hasn't been able to find your root filesystem. I thought that generally resulted in the kernel panicking, but apparently not. I notice that you haven't told the kernel where your root filesystem is, though, so either autodetection hasn't worked or there is no autodetection. I would suggest adding root=device to the end of the linux /boot/vmlinuz-3.2.0-4-686-pae ro line, where device is any valid way of telling linux where the device is (so you could say /dev/sda1, LABEL=rootfs, UUID=1234-567... etc etc). If that works and you get into your system, re-run sudo update-grub to fix the grub configuration. Bye -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/aaad2d0fdf31192f09b774865a1fd...@andaluciajunta.es Hi, in addition, you can try to locate your hard drive with sfdisk -l . I think that it should work. If not, try : # cd /bin # ln -s busybox sfdisk # sfdisk -l
