auto partitioning suggested me keeping 40 gb for vista, however i decided its too much (having 160 gb total so it does matter), i reduced it manually to 20 (5 gb free).
After reducing, installer automatically increased total sda4 extended size, but didnt change anything of further sda5, sda6, sda7
So i thought those gigabytes i made available by reducing win are going nowhere
so i calculated difference for start and end cylinders for sda5 and sda6 and changed them accordingly, then increased sda7 to max
now it looks like:
sda4 extended start 2411 end 9898
sda5 swap start 2411 end 2672
sda6 / start 2673 end 4745
sda7 /home start 4746 end 9898
please tell me if this is right and i can proceed
because im not sure about beginning of sda5, maybe it should start from 2412 for example or maybe require even more - i dont know because i moved that manually.
ok now the installation goes on this is not a question rather an error report.
after getting error 1008 i tried to re-run install. however, it refused to determine anything at the partitioning stage.
so i took dvd out and reboot with vista.
1st it started some chkdsk stuff in text mode.
then it booted completely but suggested to reboot for unknown reason (i agreed)
after i found that changes were made: vista part. size cut to 20gb and everything works fine - so no data damaged.
then i started install once again.
this time it determined partitions well, however, there were two 2gb swap suggested and 1st one was without “F” sign - looks like it was created on previous run.
another odd thing that, numbers changed a bit:
last cyl for extended 9899 (was 9898) and at the same time another one - (ntfs data logical part. which i intend to convert to linux later) was beginning from 9899.
to make safe i changed sda7’s last to 9898 (not to be the same with one of following partition)
this may be a suggestion to developers:
on phase of selecting partition, when you reduce size of existing os’ default - very direct, quite easy for users, it automatically suggests to increase extended partition.
but, if user wants to do so, we may assume he wants to do that to favor linux’s parts, so they could be suggested to be increased accordingly as well.
A week ago we tried installing MS Win XP first and then openSUSE 11.0 without any error.
Then later when we installed Vista by erasing the whole hard disk (using recovery CDs) and then openSUSE 11.0 this error -1008 suddenly appeared.
Then we again tried installing Win XP (also using recovery CDs) erasing the whole hard disk, and now the -1008 error did also appear when installing openSUSE 11.0.
Eventually we solved the problem today:
We believe the -1008 error upon creating the first logical partition in the extended partition (i.e. in most automatic cases the swap partition as /dev/sda5) is caused by a wrong Id label on the extended partition.
When rebooting in ‘rescue mode’ from the install DVD, logging in as root and running ‘fdisk’, the Id label of the extended partition was something like ‘W95 extended partition’.
When deleting and remaking the extended partition from fdisk, the extended partition was now automatically given Id 5 (‘Extended’) as label. Writing the partition table with this label on the extended partition and rebooting, now the installation of openSUSE 11.0 went flawlessly. The linux partitions inside the extended partition was created during the install process.
According to the man page of ‘fdisk’ the fdisk program is buggy doing fuzzy things and it is recommended to use ‘cfdisk’ instead. (This we discovered afterwards )
Hope this resolves your error -1008 problems as well
Most installers don’t use fdisk(8) but sfdisk(8), which is a very nice utility but rather trickier to use than fdisk(8). I love it for making records of partition tables, that can be restored later.
Basically, you should create free space, then make new partition. If an extended partiton has logicals, you need to delete them, in order to delete it and create new.
Though I am not keen on LVM partitions for root, they work very well for others (apart from /boot) and are to be preferred over traditonal partition schemes for their flexibility.
)