Bug 645196

Summary:	partitioning problems
Product:	[openSUSE] openSUSE 11.3	Reporter:	Charlie Barfield <nothereforever>
Component:	Installation	Assignee:	Charlie Barfield <nothereforever>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	aschnell
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	openSUSE 11.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Charlie Barfield 2010-10-09 10:37:19 UTC

i chose to create my own arangement as the installer saw my hard disks as a RAID array (2x drives double the space) instead of the way it was made and this might effect my other bugs i have reported.

i specified which partitions to erase and let it create its own arrangement for Home Root and Swap. after installing i found it didnt make Root a primary partition and couldnt boot it! it had it right before with my first install.
the difference between now and then is that then i told setup to make a fat32 partition at the end. now there is a NTFS i want to keep at the end of the drive.

about that fat 32 partition: i had told the setup to make a fat32 partition at the end of the drive but afterward i tried to access it and it was too big. 


so i tried the LVM arrangement. it made a /boot partition which should be good, and it made a 20 gig root and a 25 gig home and a 2gig swap but it left the rest of the LVM BLANK!! normally it fills the rest of the space with HOME. so i made an extra one in the LVM for usr and it is 34.9GIG


problems
A:setup sees my two drive arrangement as a space doubling raid. and dont see my partitions in my drives. this prevents setup mounting the drives as /windows/CDEF volumes. later in the installed operating system i have /media/label(s) for each one but they are inaccessible. i have posted a bug for that too but hadnt provided these setup details only the post install stuff: (https://bugzilla.novell.com/show_bug.cgi?id=640380)

B:setup can make fat32 partitions too big
C:no primary partition for root
D:LVM not filled.

Comment 1 Charlie Barfield 2010-10-09 11:19:32 UTC

well now i rebooted it.

problems
E:i had to in windows mark the /boot partition active
F:and i now have a imageless GRUB. after selecting the SUSE i get error 17 cannot mount selected partition.

root (hd1,0)
filesystem type unknown, partition type 0x7
kernel /....2.6.34-12.... root=/devsystem/root resume=/dev/system/swap 

so maybe try the nonLVM method and do it manually.

Comment 2 Charlie Barfield 2010-10-09 22:42:25 UTC

i tried again and it seemed to have my controllers confused and messed up my windows drive booting ability (removed the Active mark) not sure if it was this time (below) or last time (comment 1), this time i did tell it to put booting material on MBR and on root.
NOTE all my linux installations so far on this computer have been on a USB controller. the error in the last comment lacked the controller name.

this time i had partitions in this order, all primaries
Swap
Root
Home
NTFS

after making root Active,  Grub got this message
root (hd2,1)
filesysteom type unknown, partition type 0x7
kernal /boot/vmlin....desktop root=/dev/disk/by-id/[usb controller name part2] resume=/dev/disk/by-id/[usb controller name part1]

error 17 cannot mount selected partition 


i will try once more with the root as a primary partition and the rest in an extended.

Comment 4 Arvin Schnell 2010-10-11 08:12:48 UTC

Unfortunately your report does not contain the required information to
analyse the problems. Most importantly YaST logs are missing, see
http://en.opensuse.org/openSUSE:Bugreport_YaST.

A: YaST logs are missing. It's even unclear whether you have a BIOS RAID or
   Software RAID.

B: The partition is larger than 2TB? What is the actual problem?

C: It is possible to boot from logical partitons. Real problem unclear.

D: Need YaST logs.

E: Need YaST logs.

F: Need YaST logs.

Also, please make individual reports for the problems. Otherwise we cannot
assign the report to the correct people. E.g. partitioning, bootloader
configuration and grub are maintained by different people.

Comment 5 Charlie Barfield 2010-10-28 08:18:43 UTC

the bios is set to JBOD but the setup sees it different... it could be giving me an option of a software raid, but also the partitions on the drives are being reported incorrectly by setup and i dare not touch it!

the fat partition was 67Gig. when trying to access or write and/or format (cant remember) windows gave me an error so i reformatted to NTFS. this is the only NTFS drive SUSE mounts perfectly. the other drives it doesnt and reports a problem doing it (however a SUSE live CD works fine unusually) info on that in bug 640380.

i want primary partitions for root because windows can mark these as active and system can boot as normal... however the last couple of installs, it found grub on root partition but never booted, it gave error i wrote above. 

any yast log i give will be of the booted OS immediately after setup, after reboot it wont work. (by the way does the setup have yast logs? could be handy also)


by the way i cant get a yast log for problem D! its a setup flaw! a video or screen shot help if you do not believe me.... (and C as well but i have the feeling you think having all of linux in a extended partition is ok)

Charlie.

Comment 6 Charlie Barfield 2010-11-12 23:34:17 UTC

created Bug 653081 for problem A

Comment 7 Charlie Barfield 2010-11-13 01:53:39 UTC

created Bug 653456 for problem D

Comment 8 Charlie Barfield 2010-11-13 01:55:53 UTC

E and F is probably my fault

Comment 9 Tomáš Chvátal 2017-08-11 13:49:43 UTC

11.3 is no longer supported release and disk partitioning was rewritten in the meanwhile.