I've got my drive setup so that I can dual boot Windows and Slackware, with two other partitions that I chain load (those two partitions use their own boot loader).
Here's the output from `fdisk -l`
/dev/sda1 * 63 644034559 322017248+ 7 HPFS/NTFS/exFAT
/dev/sda2 644036606 1053631844 204797619+ 5 Extended
/dev/sda3 1053631845 1057628312 1998234 82 Linux swap / Solaris
/dev/sda4 1057628313 1250263727 96317707+ 83 Linux
/dev/sda5 644036608 748894207 52428800 83 Linux
/dev/sda6 748894271 1053631844 152368787 83 Linux
Previously, I had my lilo.conf setup like this:
other = /dev/sda1
label = Windows
table = /dev/sda
image = /boot/vmlinuz
root = /dev/sda2
label = Old-Slack
other = /dev/sda5
label = Debian
other = /dev/sda6
label = New-Slack
Note that Old-Slack's root was set to the Extended
partition. This worked fine until I installed Windows 7 and had to reset the MBR with lilo again, and after that point all of my links to dev/sda2
were broke because they weren't pointing to the actual partition with data on it. I know this wasn't something that happened on this one partition: each of my Linux partitions reference a directory on Old-Slack and they all broke after my MBR fix.
Now I've edited sda2 out and sda4 in (the correct partition) and things are back to normal.
How was my system running before when it was referencing the Extended partition instead of the actual partition with the data on it (sda4)? Did I just get lucky? Did I even fix it this time?