If Lenny is installed now, do this in a terminal window:
Code: Select all
$ su
[Enter root password.]
# fdisk -l
Phil
Code: Select all
$ su
[Enter root password.]
# fdisk -l
Grub legacy and grub4dos count the number of partitions from zero, while Grub 2 counts the number from 1.Radvan wrote:(1) GRUB 2 is not the one who is causing troubles. It's FDISK but it is nothing new. Create a prtition with Debian FDISK, even in Lenny, and LVM will stop talking with you.
(2) I have noticed that Debian Squeeze FDISK numbers partitions from the end of the disk. At least, sometimes. In my last (successful) attempt, I have created 4 primary partitions for Debian using OS/2 LVM (I can afford it, I have 2 disks). The first one (from the beginning of the disk) was root, followed by /home, swap, and user defined FAT32 partition for passing files between eCS and Debian. Debian FDISK accepted these partitions without commentaries but - the root partition was (hd1,4). In Lenny, the partition would be (hd1,0). Oh, well, where the sad people which failed to install Sueeze along with other operating system installed their GRUB ... ?
(3) The whole installation runs without problems (if it does not crash in debootstrap or in "installing software"). I have installed on ext4, placing GRUB 2 (no GRUB legacy) on (hd1,4). After rebooting, the disk was okay for LVM, it was possible to add the Debian root partition to the boot manager menu and boot Squeeze. Terrific!
Code: Select all
Disk 1
C 2055 HPFS primary Bootable "eCS"
7 Boot Manager primary Startable
D 32002 JFS logical Advanced/LVM
E 32002 JFS logical Advanced/LVM
F 31319 JFS logical Advanced/LVM
Disk 2
20002 Linux primary Bootable "root"
65005 Linux primary
5004 Linux Swap primary
5361 FAT32 primary
Code: Select all
Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 7 HPFS/NTFS
/dev/sda2 * 263 263 8032+ a OS/2 Boot Manager
/dev/sda3 264 12161 95570685 f W95 Ext'd (LBA)
/dev/sda5 * 264 4343 32772568+ 35 Unknown
/dev/sda6 * 4344 8168 30724281 35 Unknown
/dev/sda7 * 8169 12161 32073741 35 Unknown
Disk /dev/sdb: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d5a01
Device Boot Start End Blocks Id System
/dev/sdb1 11476 12161 5510295 b W95 FAT32
/dev/sdb2 10838 11475 5124735 82 Linux swap / Solaris
/dev/sdb3 2551 10837 66565327+ 83 Linux
/dev/sdb4 1 2550 20482843+ 83 Linux
Partition table entries are not in disk order
You can execute fdisk after removing /dev/sda (OS/2 HDD) physically. Then it does not harm LVM of OS/2.Radvan wrote:(1) GRUB 2 is not the one who is causing troubles. It's FDISK but it is nothing new. Create a prtition with Debian FDISK, even in Lenny, and LVM will stop talking with you.
I encourage you to read the thread more closely. Even the OP, who made the problem 10 times harder than it had to be, said (quoting verbatim here)dickr wrote:Luckely I found this thread before I started to install OS/2 because it is not going to work if I understand it correctly.
Radvan wrote:Here I want to report a victory It is really possible to install Squeeze and OS/2 on the same computer!
One of the crucial mistakes made by the OP was in listening to folks (over in the Ubuntu forums) who simply didn't know what they were talking about. Rather than relying on the testimony of folks whose expertise you cannot verify, I'd encourage you to experiment for yourself, by following a suggestion I made to the OP: try it all out in a VM before applying it to "bare metal."dickr wrote:Before I start cleaning the partitions, can someone tell me if my plan might work?