Bug 118721 - 10.0RC1 HD partitions not detected during install, install aborted
Summary: 10.0RC1 HD partitions not detected during install, install aborted
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 1
Hardware: Other All
: P5 - None : Blocker
Target Milestone: SUSE Linux 10.1
Assignee: Thomas Fehr
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-24 21:19 UTC by Brian McNeil
Modified: 2005-09-29 08:53 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
same as comment (408 bytes, text/plain)
2005-09-27 18:28 UTC, Brian McNeil
Details
hwinfo.out debug file, (the only one I could get written to floppy) (35.33 KB, application/x-gzip)
2005-09-28 04:03 UTC, Brian McNeil
Details
tarred YaST2 directory (33.97 KB, application/x-gzip)
2005-09-29 04:11 UTC, Brian McNeil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brian McNeil 2005-09-24 21:19:18 UTC
Can't install 10.0RC1 in a multiboot enviroment because existing disk 
partitioning is not detected during the install process. 
 
Existing Partions, from beginning of HD to end 
ID	OS		USE	FILE_SYSTEM 
hda5	suse9.1 	/	ext3 
hda6	suse9.1		/tmp	ext3 
hda7			swap	linuxswap 
hda8	suse9.1		/home	ext3 
hda2	WindowsXP	C:	NTFS 
hda10	Linux Beta	/	ext3	(target / for this install) 
hda11			swap	linuxswap 
hda12	Linux Beta	/home	ext3	(target /home for this install) 
hda9	SharedData	D:	vfat 
 
I have used the "Linux Beta" partitions for other test installs, Mandriva, 
Slackware, etc and I have'nt had trouble installing to the partitions before.  
The Opensuse 10.0 RC1 installer does not see any of these partitions, just an 
unpartitioned 60G hda.  I note that these partions were not all created at the 
same time, and have been resized at different times (hence the unusual order), 
however all my OS's don't have a problem with them, including Suse9.1 
 
LILO on the MBR is controlled by the Suse9.1 install, and XP and the Beta 
Linux are chainloaded.  I install LILO for betas on the root of the target / 
partition. 
 
System: HP ZE4500 (DM371AV) AMD laptop   
Bios: Phoenix Tech KAM1.59 April 19 2004   
 AMD 2500+ Mobile w/512K cache (Barton Core) Bios shows as 1795 MHz   
 Mainboard HP 0024 PQ1A84   
 2x512M memory, 960M available, 64M for video   
 60gig Hitachi_DK23EA-60 harddrive revision 00K2A0A2   
 SAMSUNG CDRW/DVD SN-324f   
 3.5" FLOPPY DRIVE   
 Radeon IGP 320M dispaly adapter   
 HP Digital 1024x768 Monitor 19.7" visable   
 ALi M5229 PCI Bus Master IDE Controller   
 o2Micro  OZ6912 CardBus Controller   
 Ali PCI to USB Open Host Controller   
 Conexant 56K ACLink Modem (I don't use it)   
 Texas Insturments OHCI Compliant 1394 Net Adapter   
 Ralink RT2500 internal mini-pci card 802.11b/g WLAN   
 Nat. Semiconductor Corp DP83815/816 10/100 MacPhyter PCI Adapter   
 Synaptics PS/2 Port TouchPad   
 USB Root Hub (onboard is v1.1)   
 
 I sometimes use a USB v2.0 pcmcia card, usb keyboard, usb wheel mouse
Comment 1 Michael Radziej 2005-09-26 13:19:41 UTC
Please attach the complete directory /var/log/YaST2
see http://www.opensuse.org/Bug_Reporting_FAQ#YaST
Comment 2 Thomas Fehr 2005-09-26 15:13:33 UTC
need y2log files.
Comment 3 Brian McNeil 2005-09-27 18:28:40 UTC
Created attachment 50967 [details]
same as comment

I did read the referenced FAQ, but can't seem to write the requested file/dir
to either a floppy or USB key Drive using the shift+f8 utility. Did a
cntl+alt+f2 to a shell terminal and tried to cp to /media/floppy without
success. The command executes, but does not really write to the floppy. If you
would like to give a specific command to execute to get the file written to a
floppy , I will give it a try.
Comment 4 Brian McNeil 2005-09-28 04:03:18 UTC
Created attachment 51001 [details]
hwinfo.out debug file, (the only one I could get written to floppy)

I was able to use the write to floppy option in the expert system info to get
this file.  Unfortunity browsing to any other directory only resulted in the
same file being written.
Comment 5 Thomas Fehr 2005-09-28 09:09:24 UTC
Unfortunately the hwinfo file is not what I need, I need the filw from
/var/log/YaST2.
You can simply change to a console with a shell during installation by pressing
Ctrl-Alt-F2.
You can do the following:
- start 10.0 installation and let it run up to the point where YaST2 misdetects
  your disks
- switch to shell by pressing Ctrl-Alt-F2.
- mount one of the partitions at /mnt with the following commands:
  modprobe ext3
  mount -t ext3 /dev/hda6 /mnt
  cp -av /var/log/YaST2 /mnt
  umount /mnt
- abort installation, reboot into your SL 9.1 installation and attach the
  files copied onto your disk.
Comment 6 Brian McNeil 2005-09-29 04:11:55 UTC
Created attachment 51100 [details]
tarred YaST2 directory

I was able to get the requested directory using your above instructions.
Comment 7 Thomas Fehr 2005-09-29 08:53:37 UTC
Thanks for the logs, now I see what the problem with you disk layout is:
The following command:
"/usr/sbin/parted -s /dev/hda unit cyl print"
gives the error message 
"Error: Can't have overlapping partitions."

The problem is that your extended partition (/dev/hda1) spans cylinders 1 
to 116280 (the whole disk) but your windows partition (/dev/hda2) spans
cylinders 31206 to 72819 which overlaps with the extended partition.
Parted does not like that situation an therefore refuses to work.
Of course such a partitioning scheme is highly unusual and dangerous.
Unfortunately I see no way for you to be able to install linux SL 10.0. 
I will change  some things for SL 10.1 that will make installation on 
such a partition table possible again, but so far I did not consider 
such partition scheme existing at all.

For SL10.0 installation on such a disk will unfortuantely not be possible.
For SL10.1 I did the necessary changes in SVN repository to detect such a
case and make YaSTE rely on partition data from /proc/partitions instead of
parted in such a case.