Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #37776
| From | Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: Does MSDOS mbr cause kernel panic rootfs sync? |
| Date | 2023-04-11 11:57 +1000 |
| Organization | A noiseless patient Spider |
| Message-ID | <1dregj-ng1.ln1@jefferson.foo> (permalink) |
| References | <tvcvug$jm5$1@reader2.panix.com> |
Sorry for the lateness of this followup! I've had a bit of a problem
downloading Usenet articles lately, but that's solved now (I hope).
Groovy hepcat vjp2.at@at.BioStrategist.dot.dot.com was jivin' in
comp.os.linux.misc on Wed, 22 Mar 2023 06:18 am. It's a cool scene! Dig
it.
> Maybe I've been barking up the wrong tree. On my old
> dos+xp+quantian
> config almost a decade ago,
A decade ago? And you're just getting around to asking about it now?
> I installed Quantian first
Ah, well there's your problem! You would've had better results
installing the MS based system(s) first. Whenever I'm installing
DOS/Losedows alongside Linux/Minix/*BSD, I always install the former
first. The system that comes with grub (my preferred boot loader) is
installed last, so that grub can take control of the MBR.
> then moved
> everything
> over to put MSDOS in the zero sector. Now I have MSDOS there.
I don't know what you mean by that. It's not very clear, I'm afraid.
What did you move? Where did you move it? And just where did you put
DOS? I don't understand.
Perhaps if you give us an indication of the layout of the partitions
on your HDD, it might help us understand what's going on.
But if I were to hazard a guess, I'd say you can't boot your Linux
system because the DOS/Losedows installations have overwritten the boot
loader with their own. Presumably you installed grub (or whichever boot
loader Quantian uses by default) to the MBR, and the subsequent
installation of DOS/Losedows has overwritten this with the MS boot
loader.
> Looking at
> some of the similar cases online I am wondering if this is the
> problem? If so, how fix? Something about redefining where everything
> is to knoppix?
You haven't actually stated the problem. But if it is as I have
surmised above, then the solution is fairly straight forward. Run a
rescue Linux system. This can even be the original Quantian disc you
installed from in the first place. There should be an option to
(re)install the boot loader. If not, there will certainly be an option
to run a shell. You can then mount your Quantian root file system, bind
mount the /dev filesystem beneath it (so you have access to devices -
specifically the HDD), then chroot to Quantian's root file system. Then
you can use commands to reinstall the boot loader. If you don't know
how to do all of these things, instructions can be easily found by
searching on Duck Duck Go or Google.
--
----- Dig the NEW and IMPROVED news sig!! -----
-------------- Shaggy was here! ---------------
Ain't I'm a dawg!!
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Find similar
Does MSDOS mbr cause kernel panic rootfs sync? vjp2.at@at.BioStrategist.dot.dot.com - 2023-03-21 19:18 +0000
Re: Does MSDOS mbr cause kernel panic rootfs sync? Marco Moock <mo01@posteo.de> - 2023-03-21 20:52 +0100
Re: Does MSDOS mbr cause kernel panic rootfs sync? Grant Taylor <gtaylor@tnetconsulting.net> - 2023-03-21 15:40 -0600
Re: Does MSDOS mbr cause kernel panic rootfs sync? Grant Taylor <gtaylor@tnetconsulting.net> - 2023-03-21 15:35 -0600
Re: Does MSDOS mbr cause kernel panic rootfs sync? "29V.X746" <29V.X746@noqb1u.net> - 2023-03-22 00:37 -0400
Re: Does MSDOS mbr cause kernel panic rootfs sync? "Nuno Silva" <nunojsilva@invalid.invalid> - 2023-03-22 07:49 +0000
Re: Does MSDOS mbr cause kernel panic rootfs sync? Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> - 2023-04-11 11:57 +1000
csiph-web