A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

How to reset dual boot Linux:Win GRUB after "inaccessible boot device"



 
 
Thread Tools Rate Thread Display Modes
  #16  
Old December 6th 18, 11:53 PM posted to alt.comp.os.windows-10,alt.os.linux
arlen holder
external usenet poster
 
Posts: 130
Default How to reset dual boot Linux:Win GRUB after "inaccessible boot device"

On Thu, 6 Dec 2018 22:40:55 +0000, Andy D. Robinson wrote:

The question is what's the most graceful way to clear the OS giblets?
Do I simply wipe out C:\Windows on HDD2 (sdb) and HDD1 (sdc)?
(Is it _that_ easy? Or will that open a new can of worms?)


Drat. I apologize.
I never switch privacy nyms on purpose in the same thread.

My vpn scripts that Marek mostly wrote somehow didn't like,
I think, that I moved from Linux to Windows just now, posting from both
(where it keeps a variable based on the subject line), so something
didn't reset (a bug in those scripts somewhere as my long time Usenet
reader is "vi" and the randomizer scripts use telnet to the nntp server).

Anyway, the question that remains is simply how to gracefully
eliminate all the cross-platform OS giblets, which a
o The Windows 10 on HDD1 (WD10EFRX, sdc)
o The Windows 10 on HDD2 (Toshiba, sdb)
o The Ubuntu 17.10 on HDD2 (sdb)
o The Grub on HDD2
http://www.bild.me/bild.php?file=8520861grub12.jpg

Is it as simple as deleting C:\Windows in HDD1 (sdc) & HDD2 (sdb)?
http://www.bild.me/bild.php?file=4411450grub01.jpg

Can I just "rm -rf" to wipe out /etc/grub on HDD2 (sdb)?
http://www.bild.me/bild.php?file=6315743grub_02.jpg

I'm confused what's the graceful way to wipe out the OS giblets
while keeping the data on HDD1 (WD sdc) & HDD2 (Toshiba sdb) intact?
Ads
  #17  
Old December 6th 18, 11:55 PM posted to alt.comp.os.windows-10,alt.os.linux
๐Ÿ˜‰ Good Guy ๐Ÿ˜‰
external usenet poster
 
Posts: 1,483
Default How to reset dual boot Linux:Win GRUB after "inaccessible bootdevice"

On 06/12/2018 22:40, Andy D. Robinson wrote:
Re


Please note this chap calling himself as Andy D. Robinson is a known
paedophile nym-shifter so please update your kill-file to make sure you
don't see any of his posts about paedophilia activities. There is no
point in responding to any of his posts. It was all quiet until his
post just popped up.

Path: aioe.org!news.mixmin.net!.POSTED!not-for-mail
From: "Andy D. Robinson"
Newsgroups: alt.comp.os.windows-10,alt.os.linux
Subject: How to reset dual boot Linux:Win GRUB after "inaccessible boot device"
Date: Thu, 6 Dec 2018 22:40:55 +0000
Organization: Mixmin
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 6 Dec 2018 22:40:55 -0000 (UTC)
Injection-Info: news.mixmin.net; posting-host="d7f3355f28ead1fdfbeed8e206f882bf7dbeb703";
logging-data="22076"; "
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
Content-Language: en-GB
Xref: aioe.org alt.comp.os.windows-10:80281 alt.os.linux:51776




--
With over 950 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

  #18  
Old December 7th 18, 02:02 AM posted to alt.comp.os.windows-10,alt.os.linux
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default How to reset dual boot Linux:Win GRUB after "inaccessible bootdevice"

Andy D. Robinson wrote:
Message-ID news
If you don't want the other OSes, delete the OS giblets,
so that nobody, not the OS itself, nor any OS-prober, can
detect them.


Hi Paul,

That is what I want to do, but I'm not sure how to do it gracefully.

I don't need (nor want) the older Windows 10s on HDD1 & HDD2.
http://www.bild.me/bild.php?file=4411450grub01.jpg

I'd be perfectly happy to eliminate the two old Win10 OS giblets!
http://www.bild.me/bild.php?file=8520861grub12.jpg

I booted to Grub and then Linjux to run Carlos' suggested bootinfoscript.
https://github.com/arvidjaar/bootinfoscript/raw/master/bootinfoscript
http://www.bild.me/bild.php?file=9161369grub11.jpg

This script proved:
o HDD3: The only working Windows is on sda (WD10EZEX)
o HDD2: Grub & Ubuntu (17.10) is on sdb (TOSHIBA_HDWD110)
o HDD1: Nothing of use (other than data) is on sdc (WD10EFRX)
http://www.bild.me/bild.php?file=9161369grub11.jpg

That script "thinks" that Windows is "working" on all 3 HDDs.

But the HDD1 & HDD2 Windows are both long gone, never to be recovered.
And I don't care about the Ubuntu since I'll install Ubuntu 18.10 on HDD3.
And, I don't care about the Grub on sda2 either.

The question is what's the most graceful way to clear the OS giblets?
Do I simply wipe out C:\Windows on HDD2 (sdb) and HDD1 (sdc)?
(Is it _that_ easy? Or will that open a new can of worms?)


You can remove partitions with "gparted". Even a LiveCD will do.
Windows can do it too.

which gparted # check if it is present
gparted # system will tell you how to install
sudo gparted # run it - needs root for physical layer access

You can remove the Windows partitions if you want.

*******

You can use "dd" to erase a disk entirely. Here, I'm erasing
16 sectors at a time, in an attempt to keep the disk drive
at full rate. As long as the 8192 divides evenly into the
disk size, the whole disk gets erased.

dd if=/dev/zero of=/dev/sda bs=8192

To monitor the erasure and its rate

which iotop # check
iotop # hint
sudo iotop # run
sudo iotop -a # run (accumulated)

https://linux.die.net/man/1/iotop

I sometimes run two terminal windows, with a sudo iotop
in one, and a sudo iotop -a in the other. It allows you
to examine the progress, and estimate the ETA.

*******

I might have these in the wrong order.

sdc1 sdc2
+-----+-------------------+---------+--- - -
1 sdc | MBR |* System Reserved | Old W10 |
+-----+-------------------+---------+--- - -

sdb1 sdb2 sdb3
+-----+-------------------+---------+--------------------
2 sdb | MBR |* System Reserved | Old W10 | Extended
+-----+-------------------+---------+--------------+- - -
GRUB | Ubuntu 17.10 | SWAP?
+--------------+------
sdb5

sda1 sda2 ??? ???
+-----+-------------------+------------+-------------------+---------------+
3 sda | MBR |* System Reserved | Latest W10 | Ubuntu 18.04 next | 1GB SWAP next |
+-----+-------------------+------------+-------------------+---------------+
W10,
GRUB
next

On the middle one, remove sdb5 then sdb3, then the others in any order.
In the top one, remove in any order.

dd erasure of 1 and 2, if you wanted it forensically clean
and wanted to aid future "testdisk" partition scans. Even
when you remove a partition, the header sector of the partition
is left, and will be "sniffed" by "testdisk" on a scan. Cleaning
a disk thoroughly takes a while, so it's a time versus opportunity
thing.

Before you start, unplug 1 and 2 and verify it boots. Maybe
you are already satisfied that 3 boots just fine, and don't need
to do this now.

When installing Ubuntu on 3, you can:

1) Define a couple partitions before the job starts.

2) Win10 is a bit of a weasel, in that you can define
sda3 as a primary, but Win10 will make sda4 Extended
and sda5 Logical. We can't have that now. Using "diskpart",
you can make a primary for sda4 and override the less
than hygienic Disk Management behavior. It should really
ask whether you want a Primary or Extended/Logical, rather
than just charge ahead and ruin it.

3) Shut down, unplug drive 1 and drive 2. Best practice
is to leave no room for an install to run amok.

4) Make sure you have a backup of sda1 and sda2, just in
case that's an OS you really want to keep. Never assume
anything, about installs, no matter which OS does it.
(Win2K once, erased a disk on me. It was recoverable,
but still a bit of a shocker.)

5) In Ubuntu, do a Custom install, select the big partition
as your "Slash", select the small partition as your "Swap"
and away you go.

6) Plug in drive 1 and drive 2.

Paul
  #19  
Old December 7th 18, 04:07 AM posted to alt.comp.os.windows-10,alt.os.linux
Carlos E.R.[_3_]
external usenet poster
 
Posts: 1,356
Default How to reset dual boot Linux:Win GRUB after "inaccessible bootdevice"

On 06/12/2018 23.53, arlen holder wrote:
On Thu, 6 Dec 2018 22:40:55 +0000, Andy D. Robinson wrote:

The question is what's the most graceful way to clear the OS giblets?
Do I simply wipe out C:\Windows on HDD2 (sdb) and HDD1 (sdc)?
(Is it _that_ easy? Or will that open a new can of worms?)


Drat. I apologize.
I never switch privacy nyms on purpose in the same thread.

My vpn scripts that Marek mostly wrote somehow didn't like,
I think, that I moved from Linux to Windows just now, posting from both
(where it keeps a variable based on the subject line), so something
didn't reset (a bug in those scripts somewhere as my long time Usenet
reader is "vi" and the randomizer scripts use telnet to the nntp server).


Sigh :-(


Anyway, the question that remains is simply how to gracefully
eliminate all the cross-platform OS giblets, which a
o The Windows 10 on HDD1 (WD10EFRX, sdc)
o The Windows 10 on HDD2 (Toshiba, sdb)
o The Ubuntu 17.10 on HDD2 (sdb)
o The Grub on HDD2
http://www.bild.me/bild.php?file=8520861grub12.jpg

Is it as simple as deleting C:\Windows in HDD1 (sdc) & HDD2 (sdb)?
http://www.bild.me/bild.php?file=4411450grub01.jpg

Can I just "rm -rf" to wipe out /etc/grub on HDD2 (sdb)?


That does not remove grub. The most important part of Grub is not inside
any partition or filesystem, but in some out of sight sectors.

You posted it yourself:

= Grub2 (v2.00) is installed in the MBR of /dev/sdb and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos5)/boot/grub. It also embeds following components:


There is no clean way to delete that in Windows without special
software. You could erase the first track of the disk, that would do it,
but would erase any partition table, too.

What we do is to simply overwrite the code in first sector of the disk,
the MBR (but not the rest of the sector). I have forgotten the msdos
command that did that... ah, "fdisk /mbr" it was. Still, grub's core.img
is not deleted, but nothing points to it and thus it will not run and
display the menu.

No need to delete Linux or Windows with anything special. Just use a
*good* partitioning software and tell it to delete the relevant
partitions leaving empty unpartitioned space there. It works instantly,
seconds.

If you are paranoid - wait, you are, 'cos you are the nameshifter - then
use dd in Linux to overwrite with zeroes. It will take hours. Or use one
of those programs that overwrites with random data 32 times. It will
take days. Or use a special command in the "ATA Security Feature Set" to
do a "security erase". There is some Windows software to do it, but I
don't remember which.


--
Cheers, Carlos.
  #20  
Old December 7th 18, 05:28 AM posted to alt.comp.os.windows-10,alt.os.linux
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default How to reset dual boot Linux:Win GRUB after "inaccessible bootdevice"

Carlos E.R. wrote:
On 06/12/2018 23.53, arlen holder wrote:
On Thu, 6 Dec 2018 22:40:55 +0000, Andy D. Robinson wrote:

The question is what's the most graceful way to clear the OS giblets?
Do I simply wipe out C:\Windows on HDD2 (sdb) and HDD1 (sdc)?
(Is it _that_ easy? Or will that open a new can of worms?)

Drat. I apologize.
I never switch privacy nyms on purpose in the same thread.

My vpn scripts that Marek mostly wrote somehow didn't like,
I think, that I moved from Linux to Windows just now, posting from both
(where it keeps a variable based on the subject line), so something
didn't reset (a bug in those scripts somewhere as my long time Usenet
reader is "vi" and the randomizer scripts use telnet to the nntp server).


Sigh :-(


Anyway, the question that remains is simply how to gracefully
eliminate all the cross-platform OS giblets, which a
o The Windows 10 on HDD1 (WD10EFRX, sdc)
o The Windows 10 on HDD2 (Toshiba, sdb)
o The Ubuntu 17.10 on HDD2 (sdb)
o The Grub on HDD2
http://www.bild.me/bild.php?file=8520861grub12.jpg

Is it as simple as deleting C:\Windows in HDD1 (sdc) & HDD2 (sdb)?
http://www.bild.me/bild.php?file=4411450grub01.jpg

Can I just "rm -rf" to wipe out /etc/grub on HDD2 (sdb)?


That does not remove grub. The most important part of Grub is not inside
any partition or filesystem, but in some out of sight sectors.

You posted it yourself:

= Grub2 (v2.00) is installed in the MBR of /dev/sdb and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos5)/boot/grub. It also embeds following components:


There is no clean way to delete that in Windows without special
software.


Do you mean "dd.exe" ?

We have one of those.

http://www.chrysocome.net/dd

http://www.chrysocome.net/downloads/dd-0.6beta3.zip

The "dd.exe" is a bit "cranky" and is an acquired taste.

There's also a hex editor that opens disk drives.
You have to run that as Administrator to run amok
in there. I've not seen any description of what
happens when you zero out the entire C: partition
while the OS is running :-)

https://mh-nexus.de/en/hxd/

There's all sorts of fun utilities. Even the
OS has the buildin "diskpart", which can remove
the MBR or clean an entire disk from end to end.
("Clean" and "Clean All").

There's fixboot, fixmbr, bootsect, bootrec, all
sorts of utilities. And bcdedit for adjusting
the boot menu in Vista+.

Paul
  #21  
Old December 7th 18, 02:24 PM posted to alt.comp.os.windows-10,alt.os.linux
Carlos E.R.[_3_]
external usenet poster
 
Posts: 1,356
Default How to reset dual boot Linux:Win GRUB after "inaccessible bootdevice"

On 07/12/2018 05.28, Paul wrote:
Carlos E.R. wrote:
On 06/12/2018 23.53, arlen holder wrote:
On Thu, 6 Dec 2018 22:40:55 +0000, Andy D. Robinson wrote:

The question is what's the most graceful way to clear the OS giblets?
Do I simply wipe out C:\Windows on HDD2 (sdb) and HDD1 (sdc)?
(Is it _that_ easy? Or will that open a new can of worms?)
Drat. I apologize.ย* I never switch privacy nyms on purpose in the
same thread.

My vpn scripts that Marek mostly wrote somehow didn't like, I think,
that I moved from Linux to Windows just now, posting from both
(where it keeps a variable based on the subject line), so something
didn'tย* reset (a bug in those scripts somewhere as my long time Usenet
reader is "vi" and the randomizer scripts use telnet to the nntp
server).


Sigh :-(


Anyway, the question that remains is simply how to gracefully
eliminate all the cross-platform OS giblets, which a
o The Windows 10 on HDD1 (WD10EFRX, sdc)
o The Windows 10 on HDD2 (Toshiba, sdb)
o The Ubuntu 17.10 on HDD2 (sdb)
o The Grub on HDD2
ย*http://www.bild.me/bild.php?file=8520861grub12.jpg

Is it as simple as deleting C:\Windows in HDD1ย* (sdc) & HDD2 (sdb)?
ย*http://www.bild.me/bild.php?file=4411450grub01.jpg

Can I just "rm -rf" to wipe out /etc/grub on HDD2 (sdb)?


That does not remove grub. The most important part of Grub is not inside
any partition or filesystem, but in some out of sight sectors.

You posted it yourself:

ย*= Grub2 (v2.00) is installed in the MBR of /dev/sdb and looks at
sector 1 of ย*ย*ย* the same hard drive for core.img. core.img is at this
location and looks ย*ย*ย* for (,msdos5)/boot/grub. It also embeds
following components:


There is no clean way to delete that in Windows without special
software.


Do you mean "dd.exe" ?


I was not aware of it. Interesting!


We have one of those.

http://www.chrysocome.net/dd

ย*ย* http://www.chrysocome.net/downloads/dd-0.6beta3.zip


It says:

ยซThis version does not actually do any conversion but it allows the
flexible copying of data under in a win32 environment. At the moment
block devices under Win9x are not supported but that will be added soon.ยป


Ah, no raw access, but it is needed in this case.

But then the examples have things that seem raw access:

dd if=\\.\a: of=c:\temp\disk1.img bs=1440k


The "dd.exe" is a bit "cranky" and is an acquired taste.


I imagine :-)

It is "special" in Linux, so in Windows even more :-)


There's also a hex editor that opens disk drives.


Yes, I have used them in the past. PCtools or Norton Utilities, but
before that I think "debug.com" would do. We could remove boot virii
with those in MsDOS.

You have to run that as Administrator to run amok
in there. I've not seen any description of what
happens when you zero out the entire C: partition
while the OS is running :-)


LOL :-)


https://mh-nexus.de/en/hxd/

There's all sorts of fun utilities. Even the
OS has the buildin "diskpart", which can remove
the MBR or clean an entire disk from end to end.
("Clean" and "Clean All").

There's fixboot, fixmbr, bootsect, bootrec, all
sorts of utilities. And bcdedit for adjusting
the boot menu in Vista+.


Right, then it is just google on how to repair the MBR :-)


For those that do not know how grub works:

When Grub installs on the MBR (non GPT disks) it rewrites the boot code
that is on the MBR (the rest of the sector is mostly the partition
table). This code loads into memory some more sectors from the hard
disk, that typically are simply the following sectors in the first
track, and which are not inside any partition. After loading these
sectors into RAM, the code jumps to it (runs it).

This is "core.img".

All this reading is done using the BIOS interrupt calls to load sectors
from disk directly: the boot code doesn't know (yet) how to handle files.

This core.img then reads /boot/grub and learns how to read files, and
then it can write the menu.

To erase grub when installed in this manner, the only thing that is
necessary is to replace the boot code in the first sector of the disk,
the MBR. "core.img" is not deleted because it is not trivial to do, and
if nothing calls it, it is innocuous, it can not run.


GRUB can install in another manner which I prefer. The MBR is left
intact, or instead replaced with what is called "generic MBR code". This
code looks at the partition table (it is in memory at this time), finds
the first partition that is marked bootable, loads the first sector of
that partition and runs it. Windows does the same thing. Next, some
files are loaded, but not as files, but as direct sector read (bios can
not cope with files). Ie, the boot code has a table of which sectors to
read. MsDOS did the same, which is the reason that those one or two
files were unmovable.


(I may have written inaccuracies, but I think it is mostly correct)


--
Cheers, Carlos.
  #22  
Old December 8th 18, 02:03 AM posted to alt.comp.os.windows-10,alt.os.linux
Peter 'Shaggy' Haywood
external usenet poster
 
Posts: 1
Default How to reset dual boot Linux:Win GRUB after "inaccessible boot device"

Groovy hepcat arlen holder was jivin' in alt.os.linux on Thu, 6 Dec 2018
08:57 am. It's a cool scene! Dig it.

On Wed, 5 Dec 2018 19:58:51 +0100, Carlos E.R. wrote:

Wait, the photo you posted is very different from your text above. It
displays:

o Ubuntu
o Advanced options for Ubuntu
o Memory test
o Windows 10 (on /dev/sda1)
o Windows 10 (on /dev/sdb1)
o Windows 10 (on /dev/sdc1)

Those are three different disks, the first partition of each one.


Mea culpa.
The pictures are correct.
My transcription was wrong.

The correction is sda1, sdb1, & sdc1, each of which is it's own HDD.


No, each is the first partition of a separate HDD. This is an
important distinction in many ways.

The only working Windows is HDD3 on sda1 (SATA1):
http://www.bild.me/bild.php?file=6315743grub_02.jpg

The other two Windows got corrupted (one by MS, the other by me):
http://www.bild.me/bild.php?file=4411450grub01.jpg

Trial and error shows HDD3 to be "WDC WD10EZEX":
http://www.bild.me/bild.php?file=9539818grub04.jpg

Where HDD3 was already set up in the BIOS to boot first:
http://www.bild.me/bild.php?file=1696675grub07.jpg

What "seems" to be happening is:
o Disconnecting HDD2 & HDD3, Windows boots from HDD3.
o Connecting HDD2 & HDD3, Grub on either HDD2 or HDD3 takes over!


No, no, that's not what's happening. At least, the HDD you've
installed the new system on (what you've been calling HDD3) can't have
grub on it. You see, it's like this...

Grub is a multi-stage boot loader. That means that it takes 2 (or
more) steps to boot a system.
First, there is the stage 1 boot loader installed (usually)
in /dev/sda - the boot sector (or MBR) of the first hard drive. Note
that this is not the same as the boot sector of /dev/sda1, the first
partition of the first hard drive. When it is installed, information
about the location of grub's stage 2 and setup files is stored in the
stage 1 image. (These are generally installed in the Linux
distro's /boot directory, usually on its root partition). When the
machine boots, it loads and runs stage 1. This then loads in the
coresponding stage 2. (Note that it may actually load a stage 1.5, an
intermediate stage, first.)
Next, stage 2 kicks in and loads the setup files and any loadable
modules it needs to do its work. It then presents the menu and waits
for user input. Ultimately it performs whatever task the user has
selected (eg. booting an OS).
Now, if you've just removed the first two hard drives and installed a
new OS (without grub) on the third (and only remaining) one, then
either of two things will happen. Either the new system will boot
normally, or an old grub stage 1 will load and look for its
coresponding stage 2 - and fail to find it. Since your Microstuffed
Losedows installation is booting from this HDD, then it means grub is
not installed on it at all.

So, what's happening? Well, I'm always tinkering with computers, and
one thing that always annoys me is that the drive boot order is
frequently changed when I install a new HDD. I have to go into the
BIOS/UEFI setup and change it to the correct order. Another possibility
is that your UEFI based system is booting from the first UEFI partition
it finds, which may contain grub. (Grub stage 1 can be installed to a
partition instead of the MBR. And I'm not sure of the details, but I
think it is installed to a special UEFI partition in a UEFI setup.) A
possible way around this might be to boot in legacy/BIOS mode instead
of UEFI mode.
In any event, your HDD3 with the new Losedows installation isn't the
drive that's booting.

--


----- Dig the NEW and IMPROVED news sig!! -----


-------------- Shaggy was here! ---------------
Ain't I'm a dawg!!
  #23  
Old December 8th 18, 08:41 AM posted to alt.comp.os.windows-10,alt.os.linux
Diesel
external usenet poster
 
Posts: 937
Default How to reset dual boot Linux:Win GRUB after "inaccessible boot device"

arlen holder news Tue, 04 Dec 2018 08:07:37 GMT in alt.os.linux, wrote:

On Tue, 4 Dec 2018 07:33:17 -0000 (UTC), Diesel wrote:

I'm shocked Arlen. I didn't detect one single insult or
condescending remark or comment in your entire post.


Your mother wears army boots while swimming after troop ships.
There now... are you feeling more comfy now that I just insulted
you?


That'll work. [g]

Problem with Grub is that it shouldn't even exist since this HDD3
is supposed to be "only Windows" at this point in time.


I've read the entire thread (so far). Just wipe the drive out, load
Windows 10 on it, and when you're ready, let ubuntu put Grub back on
the drive for you.

So Grub is coming from somewhere else.


As you've learned, it's coming from the drive in question. You
already know what to do about it, or you should by now. Have at it.




--
Don't become the next David Brooks cyberstalking victim!
Visit https://tekrider.net/pages/david-brooks-stalker.php (10/10 WOT)
to learn more. If you've already become a victim or know someone who
has, you can provide the following information to them, your lawyer,
local law enforcement, etc.
https://www.devon-cornwall.police.uk - His local police. Report?
David Brooks (BoaterDave)
Jersey Cottage 86 Granary Lane
Budleigh Salterton Devon EX9 6ER United Kingdom
Phone: 44-1395-443340 (H) 07974-193550 (M)
Email(s): ,
  #24  
Old December 9th 18, 07:01 PM posted to alt.comp.os.windows-10,alt.os.linux
arlen holder
external usenet poster
 
Posts: 130
Default How to reset dual boot Linux:Win GRUB after "inaccessible boot device"

On Fri, 7 Dec 2018 14:24:55 +0100, Carlos E.R. wrote:

Right, then it is just google on how to repair the MBR :-)
For those that do not know how grub works:


I realize I haven't updated this thread, where, as a courtesy and as a good
Usenet citizen, I usually post an update showing exactly what was done so
as to add to the overall tribal knowledge.

Fact is, I'm moving more cautiously than normal for a couple of reasons,
one being that I now UNDERSTAND what is going on thanks to your input
(plural your).

I'm also cautious because, while I don't care what happens to the Windows
10 on the two older HDDs, I don't want to wipe out the partition as I will
lose the data on those two older HDDs. (Given the Win10 on those two HDDs
were both bricked earlier this year, I've likely pulled "much" of the data
I need that was on them, but I don't know for sure.)

I could just move the data around, given I have 3TB in toto for the three
disks, but what I think I'll do is "gracefully" remove the working Ubuntu
on HDD2, and gracefully remove the working Grub on HDD2, and then, probably
far less gracefully, remove the long-gone bricked Windows 10 on HDD2 and
HDD1.

It should be noted that the Microsoft Store couldn't resurrect either of
those bricked Win10s so there's no reason for me to even try.

The operative word here is "gracefully" remove the working Grub & Ubuntu
and the two non-working Win10 setups.

I have BIOS (not UEFI) but this Ubuntu thread shows the complexity:
https://askubuntu.com/questions/429610/uninstall-grub-and-use-windows-bootloader#869888

No two procedures seem to be alike, which means I need to better UNDERSTAND
the two steps:
a. Gracefully removing the "active" booters (i.e., Grub & Ubuntu on HDD2)
b. Gracefully removing the "bricked" booters (i.e., Win10 on HDD1 & HDD2)

I'll report back when I have done my homework (which includes re-reading
both Carlos' and Paul's helpful hints and reading all their references).

Thanks.
  #25  
Old December 10th 18, 03:45 PM posted to alt.comp.os.windows-10,alt.os.linux
Carlos E.R.[_3_]
external usenet poster
 
Posts: 1,356
Default How to reset dual boot Linux:Win GRUB after "inaccessible bootdevice"

On 09/12/2018 19.01, arlen holder wrote:
On Fri, 7 Dec 2018 14:24:55 +0100, Carlos E.R. wrote:

Right, then it is just google on how to repair the MBR :-)
For those that do not know how grub works:


I realize I haven't updated this thread, where, as a courtesy and as a good
Usenet citizen, I usually post an update showing exactly what was done so
as to add to the overall tribal knowledge.

Fact is, I'm moving more cautiously than normal for a couple of reasons,
one being that I now UNDERSTAND what is going on thanks to your input
(plural your).

I'm also cautious because, while I don't care what happens to the Windows
10 on the two older HDDs, I don't want to wipe out the partition as I will
lose the data on those two older HDDs. (Given the Win10 on those two HDDs
were both bricked earlier this year, I've likely pulled "much" of the data
I need that was on them, but I don't know for sure.)

I could just move the data around, given I have 3TB in toto for the three
disks, but what I think I'll do is "gracefully" remove the working Ubuntu
on HDD2, and gracefully remove the working Grub on HDD2, and then, probably
far less gracefully, remove the long-gone bricked Windows 10 on HDD2 and
HDD1.

It should be noted that the Microsoft Store couldn't resurrect either of
those bricked Win10s so there's no reason for me to even try.

The operative word here is "gracefully" remove the working Grub & Ubuntu
and the two non-working Win10 setups.

I have BIOS (not UEFI) but this Ubuntu thread shows the complexity:
https://askubuntu.com/questions/429610/uninstall-grub-and-use-windows-bootloader#869888

No two procedures seem to be alike, which means I need to better UNDERSTAND
the two steps:
a. Gracefully removing the "active" booters (i.e., Grub & Ubuntu on HDD2)
b. Gracefully removing the "bricked" booters (i.e., Win10 on HDD1 & HDD2)

I'll report back when I have done my homework (which includes re-reading
both Carlos' and Paul's helpful hints and reading all their references).


You only need to do something that is safe and fast:

Have all the disks connected. Get to the bios page. Configure which disk
is to boot. Only one disk has to boot, the one that currently has
Windows, hdd3. Done. Boot.

I have been telling this several times, so just do it!




--
Cheers, Carlos.
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 01:31 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ฉ2004-2024 PCbanter.
The comments are property of their posters.