=Comment: #0================================================= SUBRATA MODAK <Subrata Modak <subrata.ibm.com>> - Storage not detected screenshot Platform: x86_64, Model: 8849J2A, Serial No: '99E2441, Hostname: x306m.in.ibm.com, F13 Alpha Installation does not detect Storage device on this machine. The machine has already SLES11 installed on it. F13 installation was achieved by making an entry in /boot/grub/menu.lst as follows: ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE Linux Enterprise Server 11 - 2.6.27.19-5 root (hd0,1) kernel /vmlinuz-2.6.27.19-5-default root=/dev/disk/by-id/scsi-SATA_WDC_WD800ABJS-2_WD-WMAM9KY17933-part3 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe initrd /initrd-2.6.27.19-5-default title F13 X86_64 Alpha Installation root (hd0,1) kernel /vmlinuz-F13ALPHA_x86_64-Install root=/dev/disk/by-id/scsi-SATA_WDC_WD800ABJS-2_WD-WMAM9KY17933-part3 resume=/dev/disk/by-id/scsi-SATA_WDC_WD800ABJS-2_WD-WMAM9KY17933-part3 crashkernel=128M-:64M@16M resume=/dev/disk/by-id/scsi-SATA_WDC_WD800ABJS-2_WD-WMAM9KY17933-part1 splash=silent showopts vnc askmethod initrd /initrd.img-F13ALPHA_x86_64-Install While booted in SLES11, the machine shows the following information: x306m:~ # uname -a Linux x306m 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 x86_64 GNU/Linux x306m:~ # fdisk -l Disk /dev/sda: 80.0 GB, 80032038912 bytes 255 heads, 63 sectors/track, 9730 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x8b047782 Device Boot Start End Blocks Id System /dev/sda1 2 262 2096482+ 82 Linux swap / Solaris /dev/sda2 * 263 653 3140707+ 83 Linux /dev/sda3 654 2611 15727635 83 Linux /dev/sda4 2612 9730 57183367+ 8e Linux LVM However, once the machine is rebooted with the installation kernel, after the initial stages, the machine does not detect the storage at all. Attached screenshots shows the actual scenarios. Regards-- Subrata =Comment: #1================================================= SUBRATA MODAK <Subrata Modak <subrata.ibm.com>> - Storgae not detected Screenshot 2 =Comment: #2================================================= SUBRATA MODAK <Subrata Modak <subrata.ibm.com>> - This issue exists with F13 Rawhide available at: http://software.linux.ibm.com/pub/mirrors/fedora.redhat.com/development/13/x86_64/os/, And yes, the F13-Alpha and the F13-Rawhide kernels are different. Regards-- Subrata =Comment: #4================================================= SUBRATA MODAK <Subrata Modak <subrata.ibm.com>> - Screenshot for tty03 This is still reproducible on F13 Beta. I am attaching the screenshots of tty03, tty04 & tty05. And also the various logs found at /tmp/ during installation. Regards-- Subrata =Comment: #5================================================= SUBRATA MODAK <Subrata Modak <subrata.ibm.com>> - Screenshot for tty04 =Comment: #6================================================= SUBRATA MODAK <Subrata Modak <subrata.ibm.com>> - Screenshot for tty05 =Comment: #7================================================= SUBRATA MODAK <Subrata Modak <subrata.ibm.com>> - All logs (anaconda+system+X,etc)
Created attachment 411851 [details] Storage not detected screenshot
Created attachment 411852 [details] Storgae not detected Screenshot 2
Created attachment 411853 [details] Screenshot for tty03
Created attachment 411854 [details] Screenshot for tty04
Created attachment 411855 [details] Screenshot for tty05
Created attachment 411856 [details] All logs (anaconda+system+X,etc)
Your syslog shows nothing storage-related.
------- Comment From Subrata Modak subrata.ibm.com 2010-05-09 12:02 EDT------- That is the same thing i am also worried about, why is storage not detected ?
------- Comment From edpollar.com 2010-06-16 12:02 EDT------- reassigning QA...
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Your bug report does not really provide any useful information. For example, the below information does not show anything other than that some unknown kind of 80.0 GB storage device is present: > While booted in SLES11, the machine shows the following information: > > x306m:~ # uname -a > Linux x306m 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 > x86_64 GNU/Linux > x306m:~ # fdisk -l > > Disk /dev/sda: 80.0 GB, 80032038912 bytes > 255 heads, 63 sectors/track, 9730 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x8b047782 > > Device Boot Start End Blocks Id System > /dev/sda1 2 262 2096482+ 82 Linux swap / Solaris > /dev/sda2 * 263 653 3140707+ 83 Linux > /dev/sda3 654 2611 15727635 83 Linux > /dev/sda4 2612 9730 57183367+ 8e Linux LVM Please provide the entire contents of the boot messages from booting that operating system (as a plain-text attachment, not in the comments box.) Also provide the output of the command "lspci -vnn" to show what devices are present, as a separate attachment.
No comment in a year, F13 is EOL already.