SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I understand that:
1. "When i load windows, it just does not find the partition and asks to reboot. Still i can access all the windows files using slackware."
2. cfdisk shows Windows as /dev/hdc1 and lilo is set to boot /dev/hdc1
3. Posting the exact error may be useful rather than "...and error message shows up, don't remember exactly, but it's mbr error".
4. Lilo installs with no errors by running /sbin/lilo
I am not convinced it is the MBR. I am thinking misconfiguration or file corruption. What does the Windows boot.ini look like?
First- I am very sorry that I missed the extended partition. I am very glad that other posters stood on this mistake. I should not have being playing with an MBR so late at night my time.
My review of the thread to date.
1. MBR record of the disk partitioning is correct.
2. Rerunning lilo has not effected any change.
3. OP says that Slackware can access the Windows partitions of the disk, suggesting that Windows partitions are intact.
4. Problem occurs only when control of the boot process is passed to the Windows boot code.
My conclusion from the above is that the problem lies with the Windows boot code.
Perhaps a hex dump of the first sector in the primary Windows partition would provide a clue?
The thing is, as allend says, it's likely not the partiton table that's at fault. I mean, if restoring the old MBR didn't work, and neither did re-installing lilo ... then it can't be the MBR.
You might need to re-install Window$. Looks like it's screwed.
win installation cd has some repair functions.
(we fixed a non bootable pc this way after partition magic crashed during resizing of c partition. as far as i remember mbr was ok but the first sector of the ntfs filesystem or the position of the winloader on the filesystem was broken)
maybe the easiest way is to repair win with a installation cd (without the whole mess of reinstallation, reconfiguration of win reinstallation of software.....)
this will overwrite the mbr and linux is no longer bootable.
then you have to boot into linux with cd, floppy or usb make a backup of the mbr and reinstall lilo.
Sorry i didn't respond to your answers. It's because of travel.
Finaly, i have done with this problem! I just needed to convert partition to fat32 and the boot error was gone. After that, i converted partition back to ntfs and all is working fine again.
Here i found the answer: http://www.hardwareanalysis.com/content/topic/19004/
Looks like it's a quite global problem.
Thanks to all, who has tried to help me.