Bug 716799
|
Description
gostrc
2011-06-27 06:39:08 UTC
Some additional info: dmsetup ls --tree returns "No Devices Found" When it dropped me to the dracut shell, I don't have /dev/cdrom and I don't have /dev/sr0 (In reply to comment #1) > Some additional info: > dmsetup ls --tree returns "No Devices Found" > > When it dropped me to the dracut shell, I don't have /dev/cdrom and I don't > have /dev/sr0 Oh.. wow.. no /dev/sr0 !! I still experience this problem, but I managed to create a live USB using Fedora's live usb creator. I then booted and it dropped me to dracut shell once again. But this time I saw that /dev/sdb was there! I changed the grub boot line from some UUID that was in there to /dev/sdb and it booted and I managed to install Fedora :) Well since this bug has been closed as "worksforme", I would like to take the time to explain that this probably isn't a bug that everyone will experience because it depends on specific hardware. Unless you have a spare sony vgn-bx760 laptop hanging around, I believe this is a legitimate bug report. Lo and behold, I just tried fedora 16 beta and I get this same bug. I bet this bug has been there for a while now since I even experience it with centos 5/6 and scientific linux 5/6 also. This is why I'm going to reopen this bug report and hopefully I can work with you guys somehow and try to get to the bottom of this. Closing this bug as "worksforme" without any further explanation really hurts me because I have taken the time to file it instead of ignoring it and going with another distribution (non-redhat). My mistake. Thank you for trying the f16 beta. Could you post the full boot output of that boot? Created attachment 526348 [details]
dmesg output for no quiet rhgb kernel options
Created attachment 526349 [details]
dmesg output for no quiet rhgb kernel options with added rdshell rdinitdebug kernel options
Thanks for letting me reopen this and for everyone's time. I have attached boot messages for both a clean (no rhgb quiet) option and one with additional kernel options (rdshell rdinitdebug). Let me know what else I could provide for this bug. This same bug during boot has happened to me also yesterday once but it never followed the no rhgb quiet command. It also displayed sh and displayed something like "your job control has stopped" or something of the sort and it does this mostly everytime>>>>..... I'm expericing the same problem after boot-up without disk, (error message) (no root device found, boot failed, sleeping forever) and I am now using the same Toshiba Model100 laptop giving me this problem to write this now. But to be able to use this laptop I have to use a Fedora 15 live boot disk and I would like to save the Fedora 15 to my empty 100 GB partitioned and titled /media/vg-toshiba100 ext4 hard disk if possible. My problem began when I format (cleaned) the just mentioned hard disk of Fedora 14 so I could update to Fedora 15. In hard drive 4 devices are there: Device 1. /dev/sr0, Mount Point: /run/initramfs/live, FilesystemType: iso9660, Total Size: 643.6MB, Availible: 0bytes. Device 2. /dev/sr0, Mount Point: /mnt/live, FilesystemType: iso9660, Total Size: 643.6MB, Availible: 0bytes. Device 3. /dev/mapper/live-rw/, Mount Point: is just forward slash, / , FilesystemType: ext 4, TotalSize: 3.9GB, Availible: 2.0GB Device 4. /dev/sda2, Mount Point: /media/vg-toshiba100, FilesystemType: ext 4, TotalSize: 91.2GB, Availible: 91.2GB In the disk analyzer tree and/or pie it shows that all of Fedora 15 files of drivers and libraries are there along with linux kernel 2.6.38.2-9.fc15.i686. I ran all the test and it reads that my disk is healthy! Any help would be most appreciative. (In reply to comment #8) > Thanks for letting me reopen this and for everyone's time. > > I have attached boot messages for both a clean (no rhgb quiet) option and one > with additional kernel options (rdshell rdinitdebug). > > Let me know what else I could provide for this bug. Hm. So the /dev/sdb showing up after you get to the prompt seems to be your iPod being detected as a mass-storage device. I think that is unrelated to not finding the "rootfs" on the live image. Could you possibly attach the boot logs from a working Linux install? Either Ubuntu or Arch is fine (or both), as long as I can see the device detection portions. Created attachment 531463 [details]
working archlinux boot log
I have attached the boot log for my working archlinux installation. Hm. When you boot the live images (that latest RC4 image would be good to test), and you get dropped to a prompt, can you do: cat /sys/devices/platform/sony-laptop/cdpower If that file doesn't exist, can you do: modprobe sony-laptop and check again? If the value is 0, try: echo "1" > /sys/devices/platform/sony-laptop/cdpower and see if the sr0 device shows up in dmesg. I tried cat /sys/devices/platform/sony-laptop/cdpower and it said the file didn't exist. So I tried modprobe sony-laptop (with a dash) and it said module sony_laptop (with an underscore) not found. (In reply to comment #14) > I tried cat /sys/devices/platform/sony-laptop/cdpower and it said the file > didn't exist. > > So I tried modprobe sony-laptop (with a dash) and it said module sony_laptop > (with an underscore) not found. Well... that might be the actual problem then. Which image did you use exactly so I can go poke around in the contents? Harald, do you know if the live images have a restricted module set that would exclude some of the x86 platform drivers? I used fedora 16 RC4 located here: http://dl.fedoraproject.org/pub/alt/stage/16.RC4/Live/x86_64/Fedora-16-x86_64-Live-Desktop.iso Would you be willing to boot the ARCH install with loglevel=8 or debug set on the kernel command line? I'd like to see the full device detection of the ARCH kernel. It would be nice to compare two 3.1 kernels as well, but it seems even the latest arch snapshot is still based on 3.0. Created attachment 531647 [details]
archlinux boot log with loglevel=8
Attched the dmesg output while booting linux 3.0.7 with loglevel=8. The 3.1 kernel is in the testing repos and there have been some bugs which have been discovered which were worthy of keeping it in testing for now. Just to make sure I didn't missing something, you did have an iPod plugged into the machine when you booted what is attached in comment #6, right? And can we get a dump of lsusb -v and lspci -v from the arch install? (In reply to comment #20) > Just to make sure I didn't missing something, you did have an iPod plugged into > the machine when you booted what is attached in comment #6, right? I plugged in the ipod after getting dropped to the dracut shell. Created attachment 531664 [details]
lspci -v from archlinux
Created attachment 531665 [details]
lsusb -v from archlinux
(In reply to comment #21) > And can we get a dump of lsusb -v and lspci -v from the arch install? Certainly, attached both files. (In reply to comment #25) > (In reply to comment #21) > > And can we get a dump of lsusb -v and lspci -v from the arch install? > > Certainly, attached both files. And possibly the same from the Fedora live image? I really appreciate your willingness to help. The theory about the sony-laptop driver is probably incorrect since the power to the cdrom driver would have to be on for the live image to boot anyway. So we're still trying to figure out what the difference between the ARCH kernel and the Fedora kernel is. I looked at the source, but there are no patches that seem related at all so it's likely a config setting. (In reply to comment #26) > (In reply to comment #25) > > (In reply to comment #21) > > > And can we get a dump of lsusb -v and lspci -v from the arch install? > > > > Certainly, attached both files. > > And possibly the same from the Fedora live image? > I couldn't run lsusb/lspci because it said those commands were not found. > I really appreciate your willingness to help. The theory about the sony-laptop > driver is probably incorrect since the power to the cdrom driver would have to > be on for the live image to boot anyway. So we're still trying to figure out > what the difference between the ARCH kernel and the Fedora kernel is. I looked > at the source, but there are no patches that seem related at all so it's likely > a config setting. And I the same with your willingness to help me :) (In reply to comment #27) > > And possibly the same from the Fedora live image? > > > > I couldn't run lsusb/lspci because it said those commands were not found. Ugh, right. The live image is space limited and your machine isn't finding the contents anyway because of the missing drive. Hm. That probably means you'll have similar problems booting from the DVD iso into a rescue mode so that won't help. Would it be possible to install the Fedora kernel RPM in the ARCH installation and boot ARCH with that kernel? I've been looking at the differences in the kernel configs and the biggest things that stick out are CONFIG_IDE not being set in the Fedora kernel, and ums-cypress not getting loaded (or present in) the initrd. (In reply to comment #15) > (In reply to comment #14) > > I tried cat /sys/devices/platform/sony-laptop/cdpower and it said the file > > didn't exist. > > > > So I tried modprobe sony-laptop (with a dash) and it said module sony_laptop > > (with an underscore) not found. > > Well... that might be the actual problem then. Which image did you use exactly > so I can go poke around in the contents? > > Harald, do you know if the live images have a restricted module set that would > exclude some of the x86 platform drivers? yes... sony_laptop might not be included in the dracut initramfs, which is used for the livecd. I can hardcode it though. Created attachment 531784 [details]
fedora boot log with loglevel=8
Created attachment 531786 [details]
lspci -v from fedora
Created attachment 531788 [details]
lsusb -v from fedora
(In reply to comment #28) > (In reply to comment #27) > > > And possibly the same from the Fedora live image? > > > > > > > I couldn't run lsusb/lspci because it said those commands were not found. > > Ugh, right. The live image is space limited and your machine isn't finding the > contents anyway because of the missing drive. Hm. That probably means you'll > have similar problems booting from the DVD iso into a rescue mode so that won't > help. > I managed to hunt down all packages required to run lsusb and lspci and extracted them manually and copied them over to the dracut environment. I have attached output from lspci -v, lsusb -v, and dmesg with loglevel=8 for fedora 16 RC4. Hope this helps. Again, the ipod message in dmesg was plugged in after getting dropped to the shell. > Would it be possible to install the Fedora kernel RPM in the ARCH installation > and boot ARCH with that kernel? > Do you still want me to look into this after I have attached the above files? > I've been looking at the differences in the kernel configs and the biggest > things that stick out are CONFIG_IDE not being set in the Fedora kernel, and > ums-cypress not getting loaded (or present in) the initrd. (In reply to comment #33) > (In reply to comment #28) > > (In reply to comment #27) > > > > And possibly the same from the Fedora live image? > > > > > > > > > > I couldn't run lsusb/lspci because it said those commands were not found. > > > > Ugh, right. The live image is space limited and your machine isn't finding the > > contents anyway because of the missing drive. Hm. That probably means you'll > > have similar problems booting from the DVD iso into a rescue mode so that won't > > help. > > > > I managed to hunt down all packages required to run lsusb and lspci and > extracted them manually and copied them over to the dracut environment. > I have attached output from lspci -v, lsusb -v, and dmesg with loglevel=8 for > fedora 16 RC4. > Hope this helps. > Again, the ipod message in dmesg was plugged in after getting dropped to the > shell. OK, excellent. Thank you. > > Would it be possible to install the Fedora kernel RPM in the ARCH installation > > and boot ARCH with that kernel? > > > > Do you still want me to look into this after I have attached the above files? Hm. No. The drivers in use for the IDE controllers are the same between ARCH and fedora. Let's do something else instead. Using the same trick you did above, can you get the modules in the following directory onto the machine and insmod them? http://jwboyer.fedorapeople.org/pub/bug716799/ That should at least bring the fedora kernel to equivalent levels of drivers loaded (minus the IDE stuff). You might also try loading scsi_wait_scan. If those don't work either, we have some other cmdline arguments to try I guess: pci=nocrs pcie_aspm=off (though I don't think this will do anything since ASPM already seems disabled) rdblacklist=ahci (In reply to comment #34) > (In reply to comment #33) > > (In reply to comment #28) > > > (In reply to comment #27) > > > > > And possibly the same from the Fedora live image? > > > > > > > > > > > > > I couldn't run lsusb/lspci because it said those commands were not found. > > > > > > Ugh, right. The live image is space limited and your machine isn't finding the > > > contents anyway because of the missing drive. Hm. That probably means you'll > > > have similar problems booting from the DVD iso into a rescue mode so that won't > > > help. > > > > > > > I managed to hunt down all packages required to run lsusb and lspci and > > extracted them manually and copied them over to the dracut environment. > > I have attached output from lspci -v, lsusb -v, and dmesg with loglevel=8 for > > fedora 16 RC4. > > Hope this helps. > > Again, the ipod message in dmesg was plugged in after getting dropped to the > > shell. > > OK, excellent. Thank you. > > > > Would it be possible to install the Fedora kernel RPM in the ARCH installation > > > and boot ARCH with that kernel? > > > > > > > Do you still want me to look into this after I have attached the above files? > > Hm. No. The drivers in use for the IDE controllers are the same between ARCH > and fedora. Let's do something else instead. > > Using the same trick you did above, can you get the modules in the following > directory onto the machine and insmod them? > > http://jwboyer.fedorapeople.org/pub/bug716799/ > > That should at least bring the fedora kernel to equivalent levels of drivers > loaded (minus the IDE stuff). You might also try loading scsi_wait_scan. also had to hunt down insmod, I loaded rfkill.ko, nothing, next I loaded sony-laptop.ko, some brightness control thing popped up but nothing related to the cdrom, next I loaded ums-cypress.ko, and it created a /dev/sr0 file :) I will attach the dmesg from that. Created attachment 531808 [details]
working dmesg log for fedora 16 RC4
(In reply to comment #36) > > Using the same trick you did above, can you get the modules in the following > > directory onto the machine and insmod them? > > > > http://jwboyer.fedorapeople.org/pub/bug716799/ > > > > That should at least bring the fedora kernel to equivalent levels of drivers > > loaded (minus the IDE stuff). You might also try loading scsi_wait_scan. > > also had to hunt down insmod, > I loaded rfkill.ko, nothing, next > I loaded sony-laptop.ko, some brightness control thing popped up but nothing > related to the cdrom, next > I loaded ums-cypress.ko, and it created a /dev/sr0 file :) Well, that is indeed good news. The unfortunate part is that we won't be able to get a change into the final release of the F16 live images. The module _should_ be present in the actual DVD install isos, so an F16 install will work there. Harald, I'm going to assign this back to dracut since the only kernel related thing is a missing module in the initramfs. Do you think you could include the ums-cypress module for live images in the future? yes Created attachment 533312 [details]
lspci from fedora 16 rescue DVD install disc
I have this problem, too. I'm upgraded from DVD install disc my fedora 64 bit system from 15 to 16. I do grub2-mkconfig -o /boot/grub2/grub.cfg nad grub2-install /dev/sda. After boot: dracut Warning: No root device "block:/dev/by-uuid/c411e4ca-acc4-48f4-8b56-7d65e728bd68" found Dropping to debug shell. sh: cant access tty; job control turned off dracut:/# My motherboard: Asus M2N4-SLI. 6GB RAM. Created attachment 533313 [details]
lsusb from fedora 16 rescue DVD install disc
Created attachment 533314 [details]
dmesg from fedora 16 rescue DVD install disc
Created attachment 533315 [details]
results Boot Info Script 0.60 from fedora 16 rescue DVD install disc
Created attachment 533316 [details]
grub2.cfg from fedora 16 rescue DVD install disc
Created attachment 533317 [details]
/etc/defaults/grub from fedora 16 rescue DVD install disc
Created attachment 533318 [details]
ls -l /boot from fedora 16 rescue DVD install disc
All files I'm created after boot my computer from Fedora 16 DVD install disc. From chroot upgraded system. I'm created a small /boot partition first in disk. This resolve my problem. Same issue here laoding intial ramdisk ... dracut warning: no root device "block:/dev/mapper/vg_(computer name)-lv_root" found dracut warning: LVM vg_(computer name)/lv_root not found dracut warning: LVM vg_(computer name)/lv_swap not found I just made intallation made a few commands to update rebooted and then this. dracut-013-19.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/dracut-013-19.fc16 Package dracut-013-19.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dracut-013-19.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16098/dracut-013-19.fc16 then log in and leave karma (feedback). dracut-013-19.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |