Mepis CDROM has wreaked havoc; my PC no longer finds any hard drive

I certainly didn't do anything to the XP system nor to partitions (I only have one). I can't remember exactly but I may possibly have opened one or more Windows files or folders, just as part of getting the feel of things.

Funny, as you say, that a CD (read-only, at that) should affect the HD. I thought the same - but in reverse - when my XP CDROM refused to open Recovery Console because it couldn't find any HD. The logic escapes me.

So much for trying to fix Windows. But keep in mind, you were trying to fix something that you said was broken. It is not Mepis' or Linux's fault if you don't know what you are doing. Find a local geek friend to help you before you make it worse.

Brian
Somewhere there is a village missing an idiot.

I seem to have created some confusion (or maybe I'm the idiot that that village is missing). I shouldn't have said "installed" should I? I ran the live CD only.

Secondly, I didn't say that it was this PC that was the broken one. It's another PC that's broken. I was using this (my main one) to burn the CD and, having burned it, to give it a test run. Before that, this PC was working fine.

Question ? Did you change the bios to boot from cd ? If so you might double check and see if your your bios has the hard drive listed as a bootable device in the boot order .

jim

tcranbrook

There's no relationship between the two machines (one's my desktop, in what passes for my workstation, the other's my HTPC in another room). The problem I've been trying for some time to find a fix for is in my HTPC; someone trying to help with that suggested I d'l and burn a CD of one of the Linux distros - as a means to help diagnose/fix that problem. I of course used my desktop to produce the CD. The rest you know...

james e. thompson

I'd always had the BIOS set to boot first from cd (because I don't have an a:\ drive), so I didn't have to change the order. And yes, it's still that way. Boot order is:- cd, USB FDD, c:\

There's no relationship between the two machines (one's my desktop, in what passes for my workstation, the other's my HTPC in another room). The problem I've been trying for some time to find a fix for is in my HTPC; someone trying to help with that suggested I d'l and burn a CD of one of the Linux distros - as a means to help diagnose/fix that problem. I of course used my desktop to produce the CD. The rest you know...

I don't know what exactly happened, but I had a similar 'end-result' (seemingly NO harddisk according to my Mepis-LiveCD. Unable to use the Mepis livecd to restore grub in the mbr) with an earlier RC from Mepis. I used ANOTHER livecd (not from Mepis) to boot and write grub to the mbr again. All 11 partitions on that single harddisk then appeared again - no data lost.
You case is however different since you need to restore the MBR for Windows: First use another LiveCD to write grub to the MBR of your HD. Then use your WinXP CD again to restore the MBR.

Hope you succeed.

Regards, Ko

New stage reached. First could I say thanks for the help so readily forthcoming here.

I now have two issues. One is with Windows. I found that when I installed an ATA hard drive with a copy of XP on it plus a lot of data, made it Primary master (shifting my multi drive to Secondary master) and booted-up, the machine booted straight into WinXP, with this disk as 'Drive 0' and my SATA drive as 'Drive 1'. In that configuration WinXP has given the ATA drive letter 'C' and the SATA drive letter 'E', and both are equally accessible. So I still have all my data:-) When I restore the previous configuration, the machine won't boot into WinXP at all (as before). I must pursue this in a Windows forum.

The other issue is with Linux (but may be off-topic here - probably should go in the 'Install Mepis' forum). I also have Knoppix on a CD; both the Mepis and the Knoppix live CDs now hang during install (both having installed successfully once, but only once), and both hang at around the same position:- at or immediately after loading /etc/fstab

Or maybe - since both issues seem to connect with file allocation tables - they are in fact linked after all...?

Brian

No offence taken.

Brian:

I don't know if you've got the same problem or not. But, it's been my experience that if you have mixed drive types and install Mepis to a SATA drive, the Mepis install script will *ALWAYS* trash the MBR in a way that Windows is no longer bootable.

This may be unique to my PC (Dell 8300). See my post in this thread for what I've found fixes mine:

http://www.mepis.org/node/8775#comment-30420

Edit: URL didn't work... trying it with code tags around it. If this doesn't work, copy and paste the above URL into your address bar.

http://www.mepis.org/node/8775#comment-30420

Jim C.

Mike:

I'm pretty sure it is a BIOS issue with my Dell. But, it doesn't make any difference how you set the drives, or what ports you use. The BIOS does not see my IDE drive (and, it's a relatively vanilla Western Digital).

It sees a CD Burner fine (regardless what connection use).

I upgraded the BIOS when I got this PC. Nope. It just does not like my drive (master or slave, doesn't make any difference what port on the MB you use). I can use the port and cables that work fine with the CD drive and it still won't work (even with the CD drive removed, the BIOS won't see it).

But, operating systems do see it fine (very strange). XP and Mepis can see it (as can other distros I've tried), even though the BIOS doesn't.

That's probably what's messing up the GRUB install from MEPIS. You don't want to have this IDE drive installed at the same time you're installing MEPIS to the SATA drive. Otherwise, it will trash your MBR for some reason where Windows can't boot.

Some of the other distros I've tried work OK with both drives in it during the install (for example Suse does fine with both and it's boot loader works OK).

With MEPIS, I just unplug it for the install to the SATA drive. It's no big deal (just an old drive I had some stuff on). I've since copied everything to the new one and will probably put the old one in another PC.

Jim C.

Not sure how much of the two previous posts I understand (please bear with me - I'm completely unfamiliar with Linux and not that clever with Windows). While I'd love to become a Linux user one day, my immediate problem is how to get my Windows box back to the way it was two days ago.

The ATA vs. SATA thing is a red herring (introduced by me). Two days ago I had only the one (SATA) drive in my machine, which was the way I built it; I've been happily running XP on that machine ever since. Now suddenly although the BIOS still sees the SATA drive the machine will no longer boot into Windows via that drive. I can't use Windows Recovery Console because it refuses to load (from the WinXP installation CD) - it just says there are no hard drives installed on my computer and aborts itself.

Is there some way to use the Mepis live CD so as to repair the MBR on the SATA hard drive, or if not is there some other workaround to enable me to boot into XP from that drive? Mepis is able to read from it and even (if I dared to use qtparted - which I don't) to create partitions on it. So can't it do anything to allow me to use it in Windows? Am I missing something that's right under my nose?

This worked for me (but, I don't know if you have the same problem):

http://www.mepis.org/node/8775#comment-30420

You can get the Ultimate Boot CD from here:

http://www.ultimatebootcd.com/

Jim C.

I'll repeat it in this thread:

Here is what I did when Windows wouldn't load:

Run Ranish Partition Manager from the Ultimate Boot CD

After you boot to the CD, you'll find Ranish under the File System Menu Choices. Make sure your NTFS partition is bootable (it wasn't after my last Mepis install before I figured out that the other drives were causing it).

I personally avoid QTParted (my experience with it has not been good, with errors/problems trying to change partions with this Dell).

Ranish doesn't understand NTFS. But, it can make the partition bootable again.

Then, go to a Windows Recovery Console (boot from your Windows CD).

Log into your Windows under recovery console (hopefully, it will find it).

Run Fixmbr (this alone may not fix the problem when you get a NTLDR not found error after a Mepis install).

Run Fixboot (sometimes this won't fix the problem either).

Make a copy of your boot.ini (copy it to bootini.old or something) just to be safe.

Run bootcfg /rebuild and make sure your Windows install is there.

Reboot and Windows will load again (at least that works for me).

If none of the above works, try installing Suse 10.0. For some reason, it managed to get Windows working again on my wife's laptop after a Mepis install wouldn't let it load Windows after some kind of "fluke" with GRUB.

Jim C.

Can anyone please suggest how I might try to retrieve this situation (presumably using the Mepis CDROM as a recovery disc, in some way)? I'm a newbie at this kind if thing and am desperate for some help.

(edit) I forgot to say that the version I burned is 3.1.1 (-1, I think)
I had a similar experiance while trying to install a newer copy of MEPIS on this laptop a few months ago. The problem occured while Grub was being written... an error reported that writing Grub had failed. It was then that I discovered a couple of serious things. First, the XP recovery CD had two ways to recover: 1) overwrite everything and lose all partitions and everything on your HD, or 2) install a second copy of XP, which would have taken a spare 5GB that the HD didn't have. Doing an "FDisk /mbr" would not work and neither could I use FDisk to explore the partitions. The XP recovery CD didn't have the HD recovery tools that previous Windows recovery CDs had.

The problem was that the logical partition which was previously marked as "Active" lost that mark and FDisk wasn't able to restore it. Thankfully, I was able to boot PCMagic 8.0's CD and run a file on it called pcboot.bat, which ran a console program which allowed me to reset the logical partition which held Windows (hda1) as the "Active" partition. Then I was able to run the PC Magic pgm which restored the mbr. That allowed XP to come up again. Then I downloaded a new copy of the same ISO, checked the md5 sum, and burned a fresh CD. The install of MEPIS using that CD went without incident and I am writing this msg from that laptop.

More than likely the problem was either a faulty ISO or a faulty burn of the MEPIS ISO.

You could be right (I've been known to be a mite hamfisted) However, I too did check the MD5 sum for the downloaded iso before I burned it. As to a faulty burn, how would I know?

Here is what I did when Windows wouldn't load:

Run Ranish Partition Manager from the Ultimate Boot CD

After you boot to the CD, you'll find Ranish under the File System Menu Choices. Make sure your NTFS partition is bootable (it wasn't after my last Mepis install before I figured out that the other drives were causing it).
Thanks JimC. This looks as if it might be just the ticket - provided I can understand how to use it and don't make any cockups.

Could you kindly first of all put me straight on one point though? Which version of UBCD should I use, basic or advanced? Left to myself I'd go for the basic (as you'll have noticed I'm anything but an advanced user) but if Ranish isn't on it then it won't serve for this purpose.

I didn't even know they had more than one version. Checking my download directory, it looks like the one I've got is 3.2 (current is 3.3). It's most surely just the basic (as I remember downloading it from one of the mirrors).

Their web site shows that the basic version of 3.3 includes Ranish.

Again, I have no idea if making the partition bootable will help with your problem or not. But, that's one of the things I did with mine.

I know very little about partitioning, and nothing at all about boot loaders, etc. So, I'm probaby not the best person to give advise. I'm just relaying what I found worked for me to get Windows working again, via trial and error.

Hi,

I'm not out of the wood yet but - unless and until it fails - I'm pursuing a strictly-Windows solution at present.

Meantime, though, I'm curious to know what people think I should do about using the Mepis live CD. *If* it is the case that using it once did cause the havoc I've reported, do I dare to use it again on the same PC (once I've - hopefully - got it running normally again)? Obviously, I now feel considerable trepidation about this. Am I right to feel that way?

I suppose it depends on how the problem I had is diagnosed, but not only can I not diagnose it myself but I doubt that I'd understand anyone else's diagnosis either However, the first thing seems to be to decide whether or not it *was* the Mepis live CD that caused the problem (if it wasn't, it was an extraordinary coincidence that I just happened to "lose" my MBR immediately after I'd run it - so I find this frankly unbelievable). Or is it possible through sheer clumsiness to cause Mepis live CD to misbehave in this way - in which case some helpful tips about "what NOT to do next time" would be much appreciated.

Beyond that, I'm all at sea. Any ideas...?

Here is what I did when Windows wouldn't load:

Run Ranish Partition Manager from the Ultimate Boot CD

After you boot to the CD, you'll find Ranish under the File System Menu Choices. Make sure your NTFS partition is bootable (it wasn't after my last Mepis install before I figured out that the other drives were causing it).

I personally avoid QTParted (my experience with it has not been good, with errors/problems trying to change partions with this Dell).

Ranish doesn't understand NTFS. But, it can make the partition bootable again.

Then, go to a Windows Recovery Console (boot from your Windows CD).

Log into your Windows under recovery console (hopefully, it will find it).

Run Fixmbr (this alone may not fix the problem when you get a NTLDR not found error after a Mepis install).

Run Fixboot (sometimes this won't fix the problem either).

Make a copy of your boot.ini (copy it to bootini.old or something) just to be safe.

Run bootcfg /rebuild and make sure your Windows install is there.

Reboot and Windows will load again (at least that works for me).

If none of the above works, try installing Suse 10.0. For some reason, it managed to get Windows working again on my wife's laptop after a Mepis install wouldn't let it load Windows after some kind of "fluke" with GRUB.

Jim C.

Thanks Jim, this helped me out too.

I don't know at what stage my WinXP became unbootable. I was booting in and out of the MEPIS Live CD and GParted Live CD and once I got my partitions in order I installed MEPIS. I saved the MEPIS boot loader to mbr, rebooted and thought I'd see if WinXP was still OK but it failed to load.

Anyway, it was easy to fix because the info was here in the forums. I like the Ultimate Boot CD Very useful.

Cheers.

I have never had a Live-CD cause any damage to a computer that a simple reboot would not fix, don't feel bad, Linux is not for every one.
----------------------------------------------------------------------------
MEPIS Help Files: http://www.mepis.org/docs/index.php/Main_Page
INTEL P-IV/HT 3.0GHz - 2X256 DDR3200 - SimplyMEPIS 6.0-1
KDE 3.5.4 - kernel 2.6.15-27-686-SMP - My iMAC runs De

The problems I used to have trying to install MEPIS probably had to due with the way the bios was detecting hard drives. I used to have mixed drive types in my PC, and the bios setup wouldn't recognize one of them (even though Windows saw it after loading).

After yanking the drive that wasn't properly recognized, I haven't seen this type of problem reoccur.

Jim C.

Hi Bruce;

This post was a bit outdated...

Probably all was solved.

Ruud