I recently tried to install SuSE 7 on a new machine (AMD Athlon 900 on an Abit KT7). Although the install appeared to work I got an error message at the end, RPM reported an error. I tracked it down to an error in fdisk, a segmentation fault. Fdisk either failed to create the partitions or created corrupt partitions. It seems that the install script through YAST2 didn't detect that there was no filesystem on the destination drive, and spent 8 hours copying the contents of the DVD to /dev/nul. When I re-ran the install I noticed that formatting the 13Gb disk appeared to take a few seconds. I found out about the seg fault when I ran fdisk from the rescue system. It wouldn't even display the partition information. That means that I couldn't even install SuSE after formatting the disk using another release of Linux. I tested it with Redhat 6.2 which formatted the disks correctly and installed cleanly. Any suggestions, other than waiting for a SuSE 7.1 DVD that is. -- Bernard Peek Not necessarily speaking for: POSTer Audience Research -- POSTAR Ltd. 27 Sale Place, London, W2 1YR. (020 7479-9700) Bernard@postar.co.uk
Use redhat to get the partion scheam you want then do the install using those partions , just sprecify how to mount them ect.. At 10:59 AM 1/22/2001 +0000, Bernard Peek wrote:
I recently tried to install SuSE 7 on a new machine (AMD Athlon 900 on an Abit KT7). Although the install appeared to work I got an error message at the end, RPM reported an error.
I tracked it down to an error in fdisk, a segmentation fault. Fdisk either failed to create the partitions or created corrupt partitions. It seems that the install script through YAST2 didn't detect that there was no filesystem on the destination drive, and spent 8 hours copying the contents of the DVD to /dev/nul.
When I re-ran the install I noticed that formatting the 13Gb disk appeared to take a few seconds. I found out about the seg fault when I ran fdisk from the rescue system. It wouldn't even display the partition information. That means that I couldn't even install SuSE after formatting the disk using another release of Linux. I tested it with Redhat 6.2 which formatted the disks correctly and installed cleanly.
Any suggestions, other than waiting for a SuSE 7.1 DVD that is.
-- Bernard Peek Not necessarily speaking for: POSTer Audience Research -- POSTAR Ltd. 27 Sale Place, London, W2 1YR. (020 7479-9700) Bernard@postar.co.uk
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/support/faq
In article <3.0.3.32.20010122064412.00fd2cc4@popd.ix.netcom.com>, Samy Elashmawy <samelash@ix.netcom.com> writes
Use redhat to get the partion scheam you want then do the install using those partions , just sprecify how to mount them ect..
I tried that. Yast uses fdisk to read the partition information, but on mys system that always fails. Yast interprets this as an attempt to install on an empty disk. It won't permit me to use the existing partitions, it will only offer the option of repartitioning and using the whole disk. -- Bernard Peek Not necessarily speaking for: POSTer Audience Research -- POSTAR Ltd. 27 Sale Place, London, W2 1YR. (020 7479-9700) Bernard@postar.co.uk
At 03:52 PM 1/22/2001 +0000, Bernard Peek wrote:
In article <3.0.3.32.20010122064412.00fd2cc4@popd.ix.netcom.com>, Samy Elashmawy <samelash@ix.netcom.com> writes
Use redhat to get the partion scheam you want then do the install using those partions , just sprecify how to mount them ect..
I tried that. Yast uses fdisk to read the partition information, but on mys system that always fails. Yast interprets this as an attempt to install on an empty disk. It won't permit me to use the existing partitions, it will only offer the option of repartitioning and using the whole disk.
Hmm, realy odd , Ok can you thrash the drive or do you have data on it ? If you can trash the drive I would then try using the whole disk , then reinstall it. Next I would try installing 6.4 and if that works , try installing 7.0 over that. PIA I know. Have you defraged and done a scandisk on the dos partions ? and fschecked the linux partions ? Use one of those system on a flopy distros for this if you cant get linux started. Have you used any thing like partion magic or any funky boot loaders ? You may need to totaly reformat the disk and even reformat the MBR via a dos fdisk /MBR. also is the /boot partion below 1024 cyl ? other wise you will need the latest version of lilo. Also BTW when you set the boot partion /boot as the first partion on disk , are you giving it at least two cylenders ? My install freaked out with only one cylender , I have a 20 gig drive and each cyl is 7.5 meg. I would not reboot. I made it two cyl with 1/0 as starting and 1.2 as ending cyl and it booted up fine. Hope that some of this helps.
-- Bernard Peek Not necessarily speaking for: POSTer Audience Research -- POSTAR Ltd. 27 Sale Place, London, W2 1YR. (020 7479-9700) Bernard@postar.co.uk
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/support/faq
In article <3.0.3.32.20010122102037.00743dbc@popd.ix.netcom.com>, Samy Elashmawy <samelash@ix.netcom.com> writes
At 03:52 PM 1/22/2001 +0000, Bernard Peek wrote:
In article <3.0.3.32.20010122064412.00fd2cc4@popd.ix.netcom.com>, Samy Elashmawy <samelash@ix.netcom.com> writes
Use redhat to get the partion scheam you want then do the install using those partions , just sprecify how to mount them ect..
I tried that. Yast uses fdisk to read the partition information, but on mys system that always fails. Yast interprets this as an attempt to install on an empty disk. It won't permit me to use the existing partitions, it will only offer the option of repartitioning and using the whole disk.
Hmm, realy odd , Ok can you thrash the drive or do you have data on it ? If you can trash the drive I would then try using the whole disk , then reinstall it.
Done that. It didn't work because the partition table was corrupt.
Next I would try installing 6.4 and if that works , try installing 7.0 over that. PIA I know. Have you defraged and done a scandisk on the dos partions ? and fschecked the linux partions ? Use one of those system on a flopy distros for this if you cant get linux started.
There are no DOS partitions, it's a Linux only system. I've already cleaned the disk and repartitioned several times.
Have you used any thing like partion magic or any funky boot loaders ? You may need to totaly reformat the disk and even reformat the MBR via a dos fdisk /MBR. also is the /boot partion below 1024 cyl ? other wise you will need the latest version of lilo.
The /BOOT partition was the first 16Mb of the disk, that's what Yast gave it. I tried manually partitioning using Red Hat and gave it a 21Mb /BOOT partition, that didn't work either. I know that there's nothing wrong with the disk because it's running the Red Hat distro perfectly. -- Bernard Peek Not necessarily speaking for: POSTer Audience Research -- POSTAR Ltd. 27 Sale Place, London, W2 1YR. (020 7479-9700) Bernard@postar.co.uk
-----Original Message----- From: Bernard Peek [mailto:Bernard@postar.co.uk] Sent: Monday, January 22, 2001 10:53 AM To: suse-linux-e@suse.com Subject: Re: [SLE] FDISK problem in SuSE 7.0
In article <3.0.3.32.20010122064412.00fd2cc4@popd.ix.netcom.com>, Samy Elashmawy <samelash@ix.netcom.com> writes
Use redhat to get the partion scheam you want then do the install using those partions , just sprecify how to mount them ect..
I tried that. Yast uses fdisk to read the partition information, but on mys system that always fails. Yast interprets this as an attempt to install on an empty disk. It won't permit me to use the existing partitions, it will only offer the option of repartitioning and using the whole disk.
Did you choose Custom partitioning? If you did and the installation still will not allow you to proceed then there is something wrong with your partition table. Also with the KT7 you must have your drive connected to the standard IDE channel you can not use it in SuSE if it is connected to the ATA100 channel. Charles (-: Forever never goes beyond tomorrow.
In article <000001c0848e$127035a0$0300a8c0@bigboy>, Charles A Edwards <eslrahc@bellsouth.net> writes
-----Original Message----- From: Bernard Peek [mailto:Bernard@postar.co.uk] Sent: Monday, January 22, 2001 10:53 AM To: suse-linux-e@suse.com Subject: Re: [SLE] FDISK problem in SuSE 7.0
In article <3.0.3.32.20010122064412.00fd2cc4@popd.ix.netcom.com>, Samy Elashmawy <samelash@ix.netcom.com> writes
Use redhat to get the partion scheam you want then do the install using those partions , just sprecify how to mount them ect..
I tried that. Yast uses fdisk to read the partition information, but on mys system that always fails. Yast interprets this as an attempt to install on an empty disk. It won't permit me to use the existing partitions, it will only offer the option of repartitioning and using the whole disk.
Did you choose Custom partitioning? If you did and the installation still will not allow you to proceed then there is something wrong with your partition table.
I can't use custom partitioning. I can select that option but it uses fdisk to read the partition table, and fdisk fails. The partition table seems to be perfectly OK, because Red Hat will boot from it.
Also with the KT7 you must have your drive connected to the standard IDE channel you can not use it in SuSE if it is connected to the ATA100 channel.
It's a standard KT7 board, not the KT7-RAID. I have an additional controller card with ATA100 ports and SuSE sees those OK. I could install Linux on hdg but that wouldn't help because would still need to write to the MBR on hda. -- Bernard Peek Not necessarily speaking for: POSTer Audience Research -- POSTAR Ltd. 27 Sale Place, London, W2 1YR. (020 7479-9700) Bernard@postar.co.uk
participants (3)
-
Bernard Peek -
Charles A Edwards -
Samy Elashmawy