Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i've tried fdisk -1 and this is the outcome:
[... ~]$ fdisk -1
bash: fdisk: command not found
so i tried /sbin/fdisk -1 and this is the outcome:
[... ~]$ /sbin/fdisk -1
/sbin/fdisk: invalid option -- 1
Usage: fdisk [-b SSZ] [-u] DISK Change partition table
fdisk -l [-b SSZ] [-u] DISK List partition table(s)
fdisk -s PARTITION Give partition size(s) in blocks
fdisk -v Give fdisk version
Here DISK is something like /dev/hdb or /dev/sda
and PARTITION is something like /dev/hda7
-u: give Start and End in sector (instead of cylinder) units
-b 2048: (for certain MO disks) use 2048-byte sectors
i ain't good with command lines now,how to run the fdisk in this case??
tried this immediately upon tat and heres wat ive got:
Disk /dev/sda: 250.0 GB, 250056171008 bytes
255 heads, 63 sectors/track, 30400 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 5230 42009943+ 7 HPFS/NTFS
/dev/sda2 5231 16708 92197035 f W95 Ext'd (LBA)
/dev/sda3 16709 30400 109980990 7 HPFS/NTFS
/dev/sda5 9060 16708 61440561 7 HPFS/NTFS
/dev/sda6 5231 5243 104359+ 83 Linux
/dev/sda7 5244 9059 30651988+ 8e Linux LVM
Partition table entries are not in disk order
If it was booting from the CDROM and you didn't see a grub menu, I doubt that the grub boot loader was run at all. You might want to change the PNP setting in the BIOS and try again. Another thing you could try is removing any usb peripherals that you don't need to perform an installation. I think that when it is probing for hardware there is something that jams it up.
If I read that correctly, your disk contains three physical partitions, sda[1-3]. sda2 is an "extended" (green) partition, containg (red) one NTFS partition, the Linux \boot partition, and a Linux "logical volume" containing, presumably, the swap and root (/) devices.
I suspect that Windoze is confused by the logical partition containing non-Windoze partitions.
Since you intend to re-install both OS, why not just delete ALL the partitions on your HD before you start your new installations?
But if i were to delete off all the partitions,mind if i ask:
1)do i loggin into xp and remove the linux partitions first?(but this way as grub was installed to mbr and i felt i may create more mess if i simply remove linux first?)
2)Or i use linux to remove xp first?(but in this way will it solve the problem?as in i will be able to start xp installation via cd this time?)
Windoze should be fine with that partition structure - so long as it can find a bootable primary partition (sda1 in this case) it should proceed.
I can't see any obvious reason why it should fail during the hardware scan unless it needs a (separate) driver for the SATA drive. If it does, one wonders how Windows was installed originally.
As for deleting the partitions, I'd do it from Linux personally. When I last had an issue like this I just zeroed out the first few sectors of the disk (including the MBR). Windows see the disk as unformatted and asks if you want to use it.