Jump to content

More Partitions . . More Distro's to boot


longgone

Recommended Posts

;) :o :hmm: :hmm: Well...... with such glowing praise and admiration for Slack 10.0 ... I will order it today ..... (it will beat the heck out of doing all the updates to current).... :ermm: :ermm: :)
Link to comment
Share on other sites

  • Replies 845
  • Created
  • Last Reply

Top Posters In This Topic

  • longgone

    415

  • Bruno

    377

  • SonicDragon

    22

  • teacher

    14

Top Posters In This Topic

:D :P :clap: :D Bruno.......I have just created/caused a massive (I think) problem..... I was in the process of doing a reinstall of Fedora on a different partition which failed completely and now I am unable to boot into much of anything. I am posting from Mndrake 9.0...tried the boot/rescue disk for Drake 10 and it doesn't get me in at all. I am getting errors having to do with init....had several .. kernel panic.... errors. Is there some means of fixing this without haviing to do complete reinstalls..... I have a suspicion what the cause is/was but it is a hardware problem... which will require replacement.... any suggestions that are not devestating?????
Link to comment
Share on other sites

Dale . . . :(You could try a repair on Drake 10 . . . but I have the suspission that you just overwrote a Drake 10 partition . . :D . . . so a reinstall and a complete redo of Lilo.conf might be the step to take.( Or try to "upgrade" your 10 install with 10. . . . sometimes that helps and leaves your personal files in tact )This was supposed to be your set-up:hda1 ... 1.9 Drake9hda3 ... 34 XPhda5 ... SWAPhda6 ... 3.8 Drake9hda7 ... 9.7 Drake9- - - - - - - - - - - - - - - hda8 ... 6.8 Slackwarehda9 ... 6.8 Knoppixhda10 .. 6.8 SUSE= = = = = = = = = = = = = = = hdb1 ... 1.9 Drake10hdb5 ... 3.9 Drake10hdb6 ... 9.7 Drake10 - - - - - - - - - - - - - - hdb7 ... 7.0 Fedorahdb8 ... 7.0 Debianhdb9 ... Keep empty for future new thingsI hope you did not repartition your drive . . . . . ??:P Bruno

Link to comment
Share on other sites

Bruno.....I do not think that I over wrote any partitions, but then not sure either. When I tried the 10 boot/rescue disk or a normal boot I get the following output....hdb: dma_intr:status=0x51 { DriveReady SeekComplete Error}hdb: dma_intr: Error=0x40 {UncorrectableError}, LBAsect=65, Sector65End Request: I/O error, dev hdb, Sector 65EXT3-fs unable to read superblockmount: Error 22 mounting ext3 Flag defaultswell, retrying without the option flagsPivotroot: Pivot_root (sysroot,/sysroot/initrd) failed: 2remounting devfs at correct place if necessarymonted devfs on /devfreeing unused kernel memory: 272k freedkernel panic: no init found. try passing init=option to kernelthe portion from the first hdb entry to the line just before the Pivotroot entry are repeated 2 times and then on the third time the Pivotroot entry and all that follows is included. I can boot into the OS's that I have floppy disks for, at least I can on Mndrk 9.0 and Slack 9.1, have not tried the Knoppix 3.4 disk yet.Just checked the Knoppix floppy disk and I can boot into it partially, it gets to a point and then I start to get I/O errors line after line, but it does allow me to boot into XP.Hope this bit of info is a help...

Edited by longgone
Link to comment
Share on other sites

Hi DaleSo it looks it is just your hdb that is messed up . . the one you re-installed Fedora.My question is: What did you exactly do to re-install it ? Did you delete the partition and recreate it again to have it clean for the install ?Can you boot knoppix Live and have a look on hdb1 and see if you can find a file called /etc/mandrake-release ? See the no init you get means it can not find the / partition on the same place as it used to be before the re-install of Fedora.My advice is still: flip in the Mandrake 10 CD and choose the option "upgrade" and see what happens . . :"> Bruno

Link to comment
Share on other sites

I hope Bruno's advice works. If not, I am afraid Fedora toasted a few things. That is one reason I avoid Fedora. It does not play nice with other distros!Julia

Link to comment
Share on other sites

:hmm: Bruno,,,,,,I thought that also, but I cannot boot the Knoppix (a normal boot anyway) partition either and it should be on hda8. It gets part way through the boot process and then hangs at an I/O error and just keeps doing it over and over. I have no idea how long it would stay there since at that point my guess is that it is not going any further I just reset the machine and use the boot disk for either Mndrk 9.0 or Slack 9.1. I tried in Mndrk 9.0 to access the hard drives to view them through the MCC> mount points> hard drive...but it will not allow me access. It just gets to the icon for the Hard Drive and then it fades in and out and the activity light on the hard drive blinks once each time this happens. The end result is I cannot see the partitioning using that method.Now about the re-install...nothing unusual except that on the first attempt I got to the part where the installation of the packages should begin and I got a warning that I had not allocated enough space in / for the packages I was installing and I could not go back far enough (using the back button) to correct it so I had to restart it and then that is where the problem started. It would get to that same area and just hang, would not go any further in the installation. I attempted it 4 or 5 times to no avail and then I tried ot just do a normal boot into Drake 10 and that is when I discovered that mess that I posted a couple of posts back. Needless to say at the moment I can only get into Mndrk 9.0 via floppy, Slack 9.1 via floppy, and Windows XP via Knoppix floppy. I cannot access Mndrk 10.0 (hdb1, etc) nor can I access Knoppix itself (hda8), and for sure not Fedora (hdb7).On top of all that mess, I now have a continous, steady hard drive activity light (which I have never had before).During this re-install/install I used the DiskDruid in order to get the exact partition I wanted for Fedora which was the same as it was on. I clicked on that partition, clicked new, created the / partition and then went on with the default install unitl it came to package selection at which point I added in KDE and Developement packages.You will have to walk me through the advice on the Knoppix live CD step, and for the moment I will have to wait to do the Mndrake 10 option as I am quite sure that the whole problem started with the CD drive that I was using to make this install. I have ordered a replacement 3-7 business days. I have a feeling that even though I do not use the CD/DVD/CDRW units very much at all that even just sitting around they go bad. Time to replace all of them I think.But that is what the current situation is at this point. (Oh what a day for a day dream) :'(
Link to comment
Share on other sites

I clicked on that partition, clicked new, created the / partition
See Dale . . here is where things went wrong . . . . you clicked "new" and "created the / partition" . . . this messed up the full partition table.Now, we can save your setup, but this will be a long long long journey . . . so be prepared. ( The more distro you multiboot, the bigger the mess usually is because we have to first check where everything went was placed to, and after that edit all the /etc/fstab files of those distro's and rewrite the complete /etc/lilo.conf )The first thing I want you to do is boot Mandrake 9.0 ( with your floppy ) and post me the lilo.conf:
# cat /etc/lilo.conf

:'( Bruno

Link to comment
Share on other sites

Bruno,,,,Okay, I can do the "cat" but at the moment am on a different machine (for sale type) so I will have to tear everything down to bring up the standard back up machine....On to a new subj but still in my last post about the steady hard drive activity light. I noticed that when I booted into XP via the Knoppix floppy that for some reason the light acts normal, it is just when I am in a Linux distro (makes no difference which one) that it is on steady.Well, off I go to do what I have to do..... bbl

Link to comment
Share on other sites

Well, we will have to be in Linux to check that one out . . . . it sure looks like Fedora messed up the HDs ruthlessly . . . ;):) Bruno

Link to comment
Share on other sites

Hi DaleIt is getting late here . . . . so I am giving you some "homework" so I can see the results in the morning ;)Once booted in Mandrake I want to see this:

su< password >fdisk /dev/hda

Then press the P key and post what you see . . . Then press the Q key to close fdisk.Then

fdisk /dev/hdb

Then press the P key and post what you see . . . Then press the Q key to close fdisk.And also I want to see

# cat /etc/lilo.conf

To see if it is good enough to write that 9.0 lilo to tha MBR for as long as we have not retored the 10.0 partition. ( we will return to the 10.0 lilo as soon as we finished fixing )Just as a reference . . . this is how the fdisk results of your HDs did look like a good few weeks ago before we started adding distros:

============================================Disk /dev/hda: 100.0 GB, 100030242816 bytes255 heads, 63 sectors/track, 12161 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/hda1 1 254 2040223+ 83 Linux/dev/hda2 255 2100 14827995 5 Extended/dev/hda3 * 2101 6562 35841015 7 HPFS/NTFS/dev/hda5 255 317 506016 82 Linux swap/dev/hda6 318 826 4088511 83 Linux/dev/hda7 827 2100 10233373+ 83 Linux=============================================Disk /dev/hdb: 61.4 GB, 61492838400 bytes16 heads, 63 sectors/track, 119150 cylindersUnits = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System/dev/hdb1 1 4063 2047720+ 83 Linux/dev/hdb2 4064 32506 14335272 5 Extended/dev/hdb3 * 1 1 0 0 EmptyPartition 3 does not end on cylinder boundary./dev/hdb4 * 1 1 0 0 EmptyPartition 4 does not end on cylinder boundary./dev/hdb5 4064 12189 4095472+ 83 Linux/dev/hdb6 12190 32506 10239736+ 83 Linux============================================
See you tomorrow ;):) Bruno
Link to comment
Share on other sites

Bruno,,,,Here is the first post of several .....

[nowarntimeout=100message=/boot/messagemenu-scheme=wb:bw:wb:bwimage=/boot/vmlinuz-enterprise        label=linux-enterpris        root=/dev/hda1        initrd=/boot/initrd-enterprise.img        append="devfs=mount hdd=ide-scsi"        read-onlyimage=/boot/vmlinuz        label=failsafe        root=/dev/hda1        initrd=/boot/initrd.img        append="failsafe devfs=nomount hdd=ide-scsi"        read-onlyother=/dev/fd0        label=floppy        unsafeother=/dev/hda3        label="Windows"        table=/dev/hda[root@localhost dale]#]
Link to comment
Share on other sites

Now here is the second post .... the results are not pretty at allllll......

[root@localhost dale]# fdisk /dev/hdaThe number of cylinders for this disk is set to 12161.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)Command (m for help): pDisk /dev/hda: 255 heads, 63 sectors, 12161 cylindersUnits = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System/dev/hda1 1 254 2040223+ 83 Linux/dev/hda2 * 255 12161 95642977+ 5 Extended/dev/hda3 2101 6562 35841015 7 HPFS/NTFS/dev/hda5 255 317 506016 82 Linux swap/dev/hda6 318 826 4088511 83 Linux/dev/hda7 827 2100 10233373+ 83 Linux/dev/hda8 6563 7454 7164958+ 83 Linux/dev/hda9 7455 8346 7164958+ 83 Linux/dev/hda10 8347 9238 7164958+ 83 Linux/dev/hda11 9239 12161 23478966 83 LinuxCommand (m for help): q[root@localhost dale]# fdisk /dev/hdbUnable to open /dev/hdb[root@localhost dale]# pbash: cd: OLDPWD not set[root@localhost dale]#[root@localhost dale]#
Link to comment
Share on other sites

On first sight Dale . . . your hda2 is bootable and it should be hda3 . . that is all there is wrong for hda . . . I think hdb will have more dammage thoughTo set the bootable bit correctly do this:

fsdisk /dev/hda

then press A --> then the 2 ( to take of the bootable bit off hda2. )Next press A --> and then 3 to set the bootable bit to hda3Then press P again and post the resultsThen press Q to close fdiskAlso you can do

/sbin/lilo

to write the Drake 9.0 lilo to the MBR . . so then you can boot Drake 9 and Windows from the lilo boot menuB) Bruno

Link to comment
Share on other sites

Here are the results..... hope I did it correctly...

[Password:[root@localhost dale]# fsdisk /dev/hdabash: fsdisk: command not found[root@localhost dale]# fdisk /dev/hdaThe number of cylinders for this disk is set to 12161.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)Command (m for help): aPartition number (1-11): 2Command (m for help): aPartition number (1-11): 3Command (m for help): pDisk /dev/hda: 255 heads, 63 sectors, 12161 cylindersUnits = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System/dev/hda1 1 254 2040223+ 83 Linux/dev/hda2 255 12161 95642977+ 5 Extended/dev/hda3 * 2101 6562 35841015 7 HPFS/NTFS/dev/hda5 255 317 506016 82 Linux swap/dev/hda6 318 826 4088511 83 Linux/dev/hda7 827 2100 10233373+ 83 Linux/dev/hda8 6563 7454 7164958+ 83 Linux/dev/hda9 7455 8346 7164958+ 83 Linux/dev/hda10 8347 9238 7164958+ 83 Linux/dev/hda11 9239 12161 23478966 83 LinuxCommand (m for help): q[root@localhost dale]# /sbin/liloAdded linux-enterpris *Added failsafeAdded floppyAdded Windows[root@localhost dale]#
Link to comment
Share on other sites

DaleThe partition table looks good . . but I did give a wrong command at the end . . instead of a Q ( Quit ) . . this time it had to be a W ( Write the new table ) . . So I am afread you have to check it again . . . . and see if the changes you made did hold . . so please check before reboot.The LILO looks perfect !:) Bruno

Link to comment
Share on other sites

:) :P B) Bruno.....Here is the latest update ......[
[root@localhost dale]# fdisk /dev/hdaThe number of cylinders for this disk is set to 12161.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)Command (m for help): pDisk /dev/hda: 255 heads, 63 sectors, 12161 cylindersUnits = cylinders of 16065 * 512 bytes Device Boot    Start    End    Blocks Id  System/dev/hda1          1    254 2040223+  83  Linux/dev/hda2 *    255  12161  95642977+ 5  Extended/dev/hda3          2101      6562  35841015    7  HPFS/NTFS/dev/hda5        255    317    506016 82  Linux swap/dev/hda6        318    826 4088511 83  Linux/dev/hda7        827      2100  10233373+  83  Linux/dev/hda8          6563      7454 7164958+  83  Linux/dev/hda9          7455      8346 7164958+  83  Linux/dev/hda10      8347      9238 7164958+  83  Linux/dev/hda11      9239  12161  23478966 83  LinuxCommand (m for help): aPartition number (1-11): 2Command (m for help): aPartition number (1-11): 3Command (m for help): wThe partition table has been altered!Calling ioctl() to re-read partition table.WARNING: Re-reading the partition table failed with error 16: Device or resource busy.The kernel still uses the old table.The new table will be used at the next reboot.Syncing disks.[root@localhost dale]#
Link to comment
Share on other sites

See . . it did NOT get written correctly , , , so we have to do it again:

fsdisk /dev/hda

then press A --> then the 2 ( to take of the bootable bit off hda2. )Next press A --> and then 3 to set the bootable bit to hda3Then press P again and post the resultsThen press W to write the new partition table ! ( and maybe Q after that if fdisk did not close after the W )We want to end up with the little star behind the hdaa3 . . and NOT behind the hda2 :'(:) Bruno

Link to comment
Share on other sites

Bruno,,,,,Running into a problem here .... this post will show it

[Password:[root@localhost dale]# fsdisk /dev/hdabash: fsdisk: command not found[root@localhost dale]# fdisk /dev/hdaThe number of cylinders for this disk is set to 12161.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)Command (m for help): aPartition number (1-11): 2WARNING: Partition 2 is an extended partitionCommand (m for help): aPartition number (1-11): 3Command (m for help): pDisk /dev/hda: 255 heads, 63 sectors, 12161 cylindersUnits = cylinders of 16065 * 512 bytes Device Boot    Start    End    Blocks Id  System/dev/hda1          1    254 2040223+  83  Linux/dev/hda2 *    255  12161  95642977+ 5  Extended/dev/hda3          2101      6562  35841015    7  HPFS/NTFS/dev/hda5        255    317    506016 82  Linux swap/dev/hda6        318    826 4088511 83  Linux/dev/hda7        827      2100  10233373+  83  Linux/dev/hda8          6563      7454 7164958+  83  Linux/dev/hda9          7455      8346 7164958+  83  Linux/dev/hda10      8347      9238 7164958+  83  Linux/dev/hda11      9239  12161  23478966 83  LinuxCommand (m for help):]
Link to comment
Share on other sites

DaleSorry . . I did not read your previous post carefull enough . . . . . you have to do it ONE MORE TIME :P . . . . the bit is now on hdda2 again . . ( and it was on hda3 on the previous post so that was correct :whistling: )Again, sorry . . I think it is just getting too late to read carefully . . . :url:

fsdisk /dev/hda

then press A --> then the 2 ( to take of the bootable bit off hda2. )Next press A --> and then 3 to set the bootable bit to hda3Then press P again and post the resultsThen press W to write the new partition table ! ( and maybe Q after that if fdisk did not close after the W )Then reboot . . and it should be okayB) Bruno

Link to comment
Share on other sites

Bruno,,,,,,,Okay I give it a try ... but one question .... what is fsdisk I get errors when I enter that command

Password:[root@localhost dale]# fsdisk /dev/hdabash: fsdisk: command not found[root@localhost dale]# fdisk /dev/hdaThe number of cylinders for this disk is set to 12161.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)Command (m for help): aPartition number (1-11): 2Command (m for help): aPartition number (1-11): 3Command (m for help): pDisk /dev/hda: 255 heads, 63 sectors, 12161 cylindersUnits = cylinders of 16065 * 512 bytes Device Boot    Start    End    Blocks Id  System/dev/hda1          1    254 2040223+  83  Linux/dev/hda2        255  12161  95642977+ 5  Extended/dev/hda3 *      2101      6562  35841015    7  HPFS/NTFS/dev/hda5        255    317    506016 82  Linux swap/dev/hda6        318    826 4088511 83  Linux/dev/hda7        827      2100  10233373+  83  Linux/dev/hda8          6563      7454 7164958+  83  Linux/dev/hda9          7455      8346 7164958+  83  Linux/dev/hda10      8347      9238 7164958+  83  Linux/dev/hda11      9239  12161  23478966 83  LinuxCommand (m for help): wThe partition table has been altered!Calling ioctl() to re-read partition table.WARNING: Re-reading the partition table failed with error 16: Device or resource busy.The kernel still uses the old table.The new table will be used at the next reboot.Syncing disks.[root@localhost dale]#
Link to comment
Share on other sites

Now it is perfect Dale . . reboot in Linux first and then try to rebvoot in Windows after that.Never mind the fdisk error message . . . ;)We will do hdb tomorrow !:whistling: Bruno

Link to comment
Share on other sites

:hmm: :hmm: :hmm: :whistling: :url: :P :) Bruno,,,,Something is not going according to Hoyle.... I just rebooted and got all the way to the point where it should have booted into the OS but it stopped and said it needed a boot disk, inserted the floppy, did three fingered assault and booted into 9.0 ... went to fdisk /dev/hda and it looks good (will post it) shouldn't I have been able to boot into 9.0 or XP without the floppy ????
Password:[root@localhost dale]# fdisk /dev/hdaThe number of cylinders for this disk is set to 12161.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)Command (m for help): pDisk /dev/hda: 255 heads, 63 sectors, 12161 cylindersUnits = cylinders of 16065 * 512 bytes Device Boot    Start    End    Blocks Id  System/dev/hda1          1    254 2040223+  83  Linux/dev/hda2        255  12161  95642977+ 5  Extended/dev/hda3 *      2101      6562  35841015    7  HPFS/NTFS/dev/hda5        255    317    506016 82  Linux swap/dev/hda6        318    826 4088511 83  Linux/dev/hda7        827      2100  10233373+  83  Linux/dev/hda8          6563      7454 7164958+  83  Linux/dev/hda9          7455      8346 7164958+  83  Linux/dev/hda10      8347      9238 7164958+  83  Linux/dev/hda11      9239  12161  23478966 83  LinuxCommand (m for help): q[root@localhost dale]#
Link to comment
Share on other sites

Dale . . you are missing the first 5 lines of your Llo.conf . . see this is what you posted:

nowarntimeout=100message=/boot/messagemenu-scheme=wb:bw:wb:bwimage=/boot/vmlinuz-enterprise        label=linux-enterpris        root=/dev/hda1        initrd=/boot/initrd-enterprise.img        append="devfs=mount hdd=ide-scsi"        read-onlyimage=/boot/vmlinuz        label=failsafe        root=/dev/hda1        initrd=/boot/initrd.img        append="failsafe devfs=nomount hdd=ide-scsi"        read-onlyother=/dev/fd0        label=floppy        unsafeother=/dev/hda3        label="Windows"        table=/dev/hda[root@localhost dale]#]
And this is how it should be:
boot=/dev/hdamap=/boot/mapdefault="Mandrake"keytable=/boot/us.kltpromptnowarntimeout=100message=/boot/messagemenu-scheme=wb:bw:wb:bwimage=/boot/vmlinuz-enterprise        label=linux-enterpris        root=/dev/hda1        initrd=/boot/initrd-enterprise.img        append="devfs=mount hdd=ide-scsi"        read-onlyimage=/boot/vmlinuz        label=failsafe        root=/dev/hda1        initrd=/boot/initrd.img        append="failsafe devfs=nomount hdd=ide-scsi"        read-onlyother=/dev/fd0        label=floppy        unsafeother=/dev/hda3        label="Windows"        table=/dev/hda
:whistling: Bruno
Link to comment
Share on other sites

This is strange.... :whistling: :url: :P

boot=/dev/hdamap=/boot/mapvga=normalkeytable=/boot/us.kltpromptnowarntimeout=100message=/boot/messagemenu-scheme=wb:bw:wb:bwimage=/boot/vmlinuz-enterprise label=linux-enterpris root=/dev/hda1 initrd=/boot/initrd-enterprise.img append="devfs=mount hdd=ide-scsi" read-onlyimage=/boot/vmlinuz label=failsafe root=/dev/hda1 initrd=/boot/initrd.img append="failsafe devfs=nomount hdd=ide-scsi" read-onlyother=/dev/fd0 label=floppy unsafeother=/dev/hda3 label="Windows" table=/dev/hda
Link to comment
Share on other sites

:) :ermm: Ahh.... yes I still am unable to do a normal, regular boot. and that Lilo that I posted is un-touched by me. I just did a kedit /etc/lilo.conf and posted the results of that, which appears to have all that you said it should have. I still need to used the floppy to get a boot into the GUI, for Mndrk and Slack. Need to use the Knoppix floppy to get into XP..... this is what fdisk /dev/hda has (looks good)...
Password:[root@localhost dale]# fdisk /dev/hdaThe number of cylinders for this disk is set to 12161.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)Command (m for help): pDisk /dev/hda: 255 heads, 63 sectors, 12161 cylindersUnits = cylinders of 16065 * 512 bytes Device Boot    Start    End    Blocks Id  System/dev/hda1          1    254 2040223+  83  Linux/dev/hda2        255  12161  95642977+ 5  Extended/dev/hda3 *      2101      6562  35841015    7  HPFS/NTFS/dev/hda5        255    317    506016 82  Linux swap/dev/hda6        318    826 4088511 83  Linux/dev/hda7        827      2100  10233373+  83  Linux/dev/hda8          6563      7454 7164958+  83  Linux/dev/hda9          7455      8346 7164958+  83  Linux/dev/hda10      8347      9238 7164958+  83  Linux/dev/hda11      9239  12161  23478966 83  LinuxCommand (m for help): q
you must admit that when I do job I do it thoroughly and completely ..... :) :lol: :)
Link to comment
Share on other sites

You sure did a rock-hard job on your HD's Dale . . . Let us try to get this puzzle cracked . . . I would like to see hdb now:

# fdisk /dev/hdb

Also please check the BIOS and make sure that it is still set to your 1st HD and not the 2nd or any other drive ( sure floppy and CD-Rom can come first, but the 3rd boot device has to be IDE-0Also after checking that do this:

# /sbin/lilo -b /dev/hda

and reboot to see if you get the boot menu. :D Bruno

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...