I'm running a SATA 200g drive.
After initial setup I go sata.i
Then cfdisk /dev/sda
Issue comes to cfdisk I can write a partition table to the drive but i cannot create a new partition. I have no [NEW] option. Was wondering if anyone knows whats going on, newby helped me with the first couple parts but he doesn't know.
Have you tried running cfdisk without any params? If not, give that a shot. I don't think I've installed slackware on a SATA drive, but I've installed it on a SCSI virtual drive, which required me to use scsi.i. Just plain cfdisk worked after that, IIRC.
cfdisk without params leads me to a nice drive with 164MB of space :)
Quote from: Mythix on December 22, 2005, 09:45:50 PM
cfdisk without params leads me to a nice drive with 164MB of space :)
Haha, that sucks. Kind of sounds like there's some problem with the physical drive itself, but that's just me talking. :)
Quote from: Mythix on December 22, 2005, 08:58:09 PM
I'm running a SATA 200g drive.
After initial setup I go sata.i
Then cfdisk /dev/sda
Issue comes to cfdisk I can write a partition table to the drive but i cannot create a new partition. I have no [NEW] option. Was wondering if anyone knows whats going on, newby helped me with the first couple parts but he doesn't know.
Are there any partitions already on there? If there are, you have to delete them.
Quote from: rabbit on December 23, 2005, 10:13:36 AMAre there any partitions already on there? If there are, you have to delete them.
He should still be able to make a partition if there's enough space to do so, correct?
No. If all 200gb of his drive are partitioned as FAT32 or whatever and he's only using 100gb of it, the other 100gb still counts as part of the partition. So, even if the drive isn't full but all of it is partitioned, then you have to delete the first partition and make 2 new ones.
Quote from: deadly7 on December 23, 2005, 11:40:36 AM
No. If all 200gb of his drive are partitioned as FAT32 or whatever and he's only using 100gb of it, the other 100gb still counts as part of the partition. So, even if the drive isn't full but all of it is partitioned, then you have to delete the first partition and make 2 new ones.
You can partition unpartitioned space. If 100 GB of space on the hard drive was left unpartitioned, he should be able to allocate it elsewhere.
I wasn't talking about how much of the partition was used, I was talking about how much space on the drive was left unpartitioned. Lern 2 red nub.
QuoteYou can partition unpartitioned space. If 100 GB of space on the hard drive was left unpartitioned, he should be able to allocate it elsewhere.
Duh. That's like saying "you can eat uneaten food."
QuoteI wasn't talking about how much of the partition was used, I was talking about how much space on the drive was left unpartitioned. Lern 2 red nub.
Well say so, then. From your first post it sounded like you were asking if he had disk space left, not disk space unpartitioned.
Quote from: deadly7 on December 23, 2005, 12:50:09 PM
QuoteYou can partition unpartitioned space. If 100 GB of space on the hard drive was left unpartitioned, he should be able to allocate it elsewhere.
Duh. That's like saying "you can eat uneaten food."
QuoteI wasn't talking about how much of the partition was used, I was talking about how much space on the drive was left unpartitioned. Lern 2 red nub.
Well say so, then. From your first post it sounded like you were asking if he had disk space left, not disk space unpartitioned.
Not really. Allocated but unused space is "uneaten food," it's just someone else's food. :P
No, you automatically assumed I was talking about unused, but already allocated space. Your problem. :P
Yeah, I would guess the problem is that it's already allocated. If it's loading at all, it means it found his drive (otherwise, it would say drive-not-found).
hmm, so what options does that leave me with? backup and reinstall windows with two partitions.
Quote from: Mythix on December 23, 2005, 02:40:18 PM
hmm, so what options does that leave me with? backup and reinstall windows with two partitions.
You already have windows installed on that partition? In that case, yeah. You'll have to back up Windows and then reallocate the space on your drive.
Quote from: Mythix on December 23, 2005, 02:40:18 PM
hmm, so what options does that leave me with? backup and reinstall windows with two partitions.
Install Windows first. One partition 98GB for Windows (should be enough). Another partition 100GB for Slackware (this much isn't needed, but tis nice to have) and then 2gb of linux-swap.
Quote from: deadly7 on December 23, 2005, 03:16:52 PM
Install Windows first. One partition 98GB for Windows (should be enough). Another partition 100GB for Slackware (this much isn't needed, but tis nice to have) and then 2gb of linux-swap.
It doesn't matter which one he installs first. Windows XP installation can partition unallocated space without damaging the already allocated partitions.
Quote from: Sidoh on December 23, 2005, 03:18:10 PM
Quote from: deadly7 on December 23, 2005, 03:16:52 PM
Install Windows first. One partition 98GB for Windows (should be enough). Another partition 100GB for Slackware (this much isn't needed, but tis nice to have) and then 2gb of linux-swap.
It doesn't matter which one he installs first. Windows XP installation can partition unallocated space without damaging the already allocated partitions.
Windows overwrites LILO with it's own startup, so it's easier to install Linux last.
Quote from: deadly7 on December 23, 2005, 03:21:42 PM
Windows overwrites LILO with it's own startup, so it's easier to install Linux last.
So I guess it depends on which one he'd want to use by default? :P
LILO reads both Windows and Linux... it lets you pick whichever one you want to boot up with.
Quote from: deadly7 on December 23, 2005, 03:31:03 PM
LILO reads both Windows and Linux... it lets you pick whichever one you want to boot up with.
I know... it was a joke. :P
Quote from: Sidoh on December 23, 2005, 03:43:28 PM
Quote from: deadly7 on December 23, 2005, 03:31:03 PM
LILO reads both Windows and Linux... it lets you pick whichever one you want to boot up with.
I know... it was a joke. :P
It wasn't very funny. :(
Quote from: deadly7 on December 23, 2005, 03:21:42 PM
Quote from: Sidoh on December 23, 2005, 03:18:10 PM
Quote from: deadly7 on December 23, 2005, 03:16:52 PM
Install Windows first. One partition 98GB for Windows (should be enough). Another partition 100GB for Slackware (this much isn't needed, but tis nice to have) and then 2gb of linux-swap.
It doesn't matter which one he installs first. Windows XP installation can partition unallocated space without damaging the already allocated partitions.
Windows overwrites LILO with it's own startup, so it's easier to install Linux last.
Technically it overwrites your MBR. If you selected the option to write LILO to disk as opposed to the MBR you'll be fine.
OR Install GRUB from Windows after you install Windows! (</grubbot>)