SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In this example, sda is the source. Sdb is the target. Do not reverse the intended source and target. Surprisingly many people do. Notrunc means 'do not truncate the output file'. Noerror means to keep going if there is an error. Normally dd stops at any error.
Copy MBR only of a hard drive: [/color]
Code:
This will copy the first 446 bytes of the hard drive to a file. If you haven't already guessed, reversing the objects of if and of, in the dd command line reverses the direction of the write.
First, do *not* go deleting any partitions. That partition layout is fine.
Quote:
When i load windows, it just does not find the partition and asks to reboot.
What does this mean ???.
Explain fully - are these messages from Windows or grub ???. That is, is Windoze booting successfully (from grub) but then dying ???.
i see boot screen. choose windows. and error message shows up, don't remember exactly, but it's mbr error.
I can go for restart if it is so important, but, believe me, it's not windows error.
Yes, there is a problem.
hdc1 starts at 1 and ends at 876.
hdc2 starts at 877 and ends at 4870. - This end point is wrong.
hdc5 starts at 877 and ends at 4159. - This start point is wrong.
hdc6 starts at 4160 and ends at 4870.
NO! It's RIGHT!
hdc2 is extended partition and "embraces" hdc5 and hdc6!
to fix:
from Slackware. Check if a mbr backup exists in /boot in file like boot.xxxx
from Windows. Put your cd, boot in recovery console. fixmbr and fixboot (I don't remember the exact commands) fixmbr /? to learn. With fixmbr from Windows (probably with Slackware too) you gone LOOSE access to slackware. So, you are gonna need to boot with slack cd 1. I chroot to my root partition and ran lilo again.
mkdir /mnt/myslack
mount /dev/hdc6 /mnt/myslack
chroot /mnt/myslack
vi /etc/lilo.conf (if needed)
lilo
probably you are ok now..
Make a backup of your MBR because it's annoying to do all this stuff.
hdc2 is extended partition and "embraces" hdc5 and hdc6!
to fix:
from Slackware. Check if a mbr backup exists in /boot in file like boot.xxxx
from Windows. Put your cd, boot in recovery console. fixmbr and fixboot (I don't remember the exact commands) fixmbr /? to learn. With fixmbr from Windows (probably with Slackware too) you gone LOOSE access to slackware. So, you are gonna need to boot with slack cd 1. I chroot to my root partition and ran lilo again.
mkdir /mnt/myslack
mount /dev/hdc6 /mnt/myslack
chroot /mnt/myslack
vi /etc/lilo.conf (if needed)
lilo
probably you are ok now..
Make a backup of your MBR because it's annoying to do all this stuff.
Hi,
I agree with your solution in part. I would add for the 'lilo';
Code:
#lilo -v -t -b /dev/hda #change to the user /dev/hd
#-t will test lilo 'do man lilo'
#lilo -v -b /dev/hda #write lilo to MBR /dev/hda
The OP should 'man lilo' and 'man lilo.conf' for more information.
As for the fixmbr
command Microsoft shows the format. For the fixboot
command example.
If the OP uses the Microsoft commands then these will restore the windows. Then the OP will need to use the chroot series for the Slackware that 'ludist' suggests to get the bootloader working again.
Note: A lot of newbies confuse the use of the extended partitions. If you create a extended partition on /dev/hda as /dev/hda3 the first partition within the extended /dev/hda3 will be /hda5. This would be so in any of the partitions that you would create as extended, be it /hda1, /hda2, /hda3 or /hda4. The first partition within the extended will be /hda5 on the defined extended device.
You could reference the partition section of the 'The Linux System Administrator's Guide: Version 0.7'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.