RE: [suse-autoinstall] YaST2 not starting from inst-sys
It turns out the problem I was having had nothing to do with SCSI or RAID. What happened was that my partitioning scheme was something along the lines of this: sda5: 512M sda6: 512M swap sda7: 2048M sda8: max <--- here's the problem sda9: 2048M The way I was using 'max' was that it allots the remaining space to its partition after ALL other partitions have been accounted for. Apparently, what actually happens is that it allots the remaining space taking into account only those partitions that have already been defined. This means that if you specify a 'max' partition it must always be last. Because all the space had already been allotted, YaST complained that the partition table was invalid. I think it'd be beneficial to allow a 'max' partition to be anywhere in the partitioning order. I imagine it'd probably be pretty easy to implement in code. I'd do it myself but I haven't seen any source code for this project. Thanks, Robert
-----Original Message----- From: Volkmar Glauche [mailto:glauche@uke.uni-hamburg.de] Sent: Tuesday, July 09, 2002 4:06 AM To: Robert Alonso Cc: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] YaST2 not starting from inst-sys
On Mon, 8 Jul 2002 ralonso@lis.state.oh.us wrote:
Thanks Volkmar. I tried replacing the root image using mkcramfs and I was successful to a certain degree. Now my problem is that I'm unable to partition the hard drive. YaST2 complains that the hard drive's partition table is unsupported. I've seen this error before and it was due to YaST trying to create all partitions as primary. See http://www.suse.de/~nashif/autoinstall/bugs.html#AEN60. That's why I wanted to use the inst-sys directory, so that I could use the updated package. Using the updated package has worked before on a standard IDE hard drive, but now I'm using two SCSI drives with RAID support and can't get the auto-partitioning to work.
Which RAID support do you use? If you want to create lvm volume groups from partitions on both drives, this will not work with even the newest available autoinstall module. I have got such a configuration on all workstations (15+) in our department and I am still waiting with the update until SuSE releases a working patch to the autoinstall module. I hope such a patch will be made available for 8.0 before the 8.1 release is shipped.
Has anyone had any success using autoyast with this type of configuration? Any hints?
Volkmar
-- Volkmar Glauche
Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg WWW http://glauche.home.pages.de/ Martinistr. 52 Phone 49(0)40-42803-5781 20246 Hamburg Fax 49(0)40-42803-9955
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
* ralonso@lis.state.oh.us <ralonso@lis.state.oh.us> [Jul 09. 2002 17:43]:
It turns out the problem I was having had nothing to do with SCSI or RAID. What happened was that my partitioning scheme was something along the lines of this: sda5: 512M sda6: 512M swap sda7: 2048M sda8: max <--- here's the problem sda9: 2048M
The way I was using 'max' was that it allots the remaining space to its partition after ALL other partitions have been accounted for. Apparently, what actually happens is that it allots the remaining space taking into account only those partitions that have already been defined. This means that if you specify a 'max' partition it must always be last. Because all the space had already been allotted, YaST complained that the partition table was invalid. I think it'd be beneficial to allow a 'max' partition to be anywhere in the partitioning order. I imagine it'd probably be pretty easy to implement in code. I'd do it myself but I haven't seen any source code for this project.
'max' does only make sense if you are using it with the last partition. Of course it is also possible to make it work with other partitions but that is not planned right now. Another negative effect is for example if you try to set 'max' on two partitions on the same drive... YaST2 source is available in the distribution and even without the having the source, you still can modify things if you want. It is script based as some of you might have noticed.... Anas
Thanks, Robert
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
participants (2)
-
Anas Nashif -
ralonso＠lis.state.oh.us