Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

All extremists should be taken out and shot.


computers / alt.os.linux.mint / Re: Can't access boot drive (vdi)

SubjectAuthor
* Can't access boot drive (vdi)Bill
+* Re: Can't access boot drive (vdi)Andrei Z.
|`* Re: Can't access boot drive (vdi)Bill
| `* Re: Can't access boot drive (vdi)Bill
|  `* Re: Can't access boot drive (vdi)Paul
|   +- Re: Can't access boot drive (vdi)Bill
|   `* Re: Can't access boot drive (vdi)Bill
|    `* Re: Can't access boot drive (vdi)Paul
|     `* Re: Can't access boot drive (vdi)Bill
|      `- Re: Can't access boot drive (vdi)Paul
`- Re: Can't access boot drive (vdi)Bill

1
Can't access boot drive (vdi)

<_JGML.1676663$vBI8.591869@fx15.iad>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5584&group=alt.os.linux.mint#5584

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx15.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
From: nonegi...@att.net (Bill)
Subject: Can't access boot drive (vdi)
Newsgroups: alt.os.linux.mint
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: Avast (VPS 230304-4, 3/4/2023), Outbound message
X-Antivirus-Status: Clean
Lines: 15
Message-ID: <_JGML.1676663$vBI8.591869@fx15.iad>
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Sat, 04 Mar 2023 12:22:18 UTC
Date: Sat, 4 Mar 2023 07:22:19 -0500
X-Received-Bytes: 1304
 by: Bill - Sat, 4 Mar 2023 12:22 UTC

I did a clean install of VirtualBox 7.06 (on Windows 10 Pro), and
installed LM 21.1.

All went well. On subsequent restart I get the error (copied from the Log)

00:00:08.027292 VMMDev: Guest Log: BIOS: Boot from Hard Disk 0 failed
00:00:08.027878 VMMDev: Guest Log: BIOS: No bootable medium found!

The proper dvi file is shown in the "Storage" (I "selected" it again, to
make sure).
Settings show SATA Port 0, Solid State Drive and "Hot Pluggable", are
both currently selected, but I think they were originally unset.

I've tried various things (redundantly..), but I hope someone can assist
me. Thank you!

Re: Can't access boot drive (vdi)

<ttvfuu$2q1mc$1@paganini.bofh.team>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5586&group=alt.os.linux.mint#5586

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!paganini.bofh.team!not-for-mail
From: no-em...@invalid.invalid (Andrei Z.)
Newsgroups: alt.os.linux.mint
Subject: Re: Can't access boot drive (vdi)
Date: Sat, 4 Mar 2023 16:09:50 +0300
Organization: To protect and to server
Message-ID: <ttvfuu$2q1mc$1@paganini.bofh.team>
References: <_JGML.1676663$vBI8.591869@fx15.iad>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 4 Mar 2023 13:09:50 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="2950860"; posting-host="rxkh9OkzK1NjfpMLLxfORw.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.8.0
Cancel-Lock: sha256:y6xk8qc6yfgsq0AvRG6hK+gQxzZGlChJO4ivmuZA7/c=
Content-Language: en-GB
X-Notice: Filtered by postfilter v. 0.9.3
 by: Andrei Z. - Sat, 4 Mar 2023 13:09 UTC

Bill wrote:
> I did a clean install of VirtualBox 7.06 (on Windows 10 Pro), and
> installed LM 21.1.
>
> All went well. On subsequent restart I get the error (copied from the Log)
>
> 00:00:08.027292 VMMDev: Guest Log: BIOS: Boot from Hard Disk 0 failed
> 00:00:08.027878 VMMDev: Guest Log: BIOS: No bootable medium found!
>
> The proper dvi file is shown in the "Storage" (I "selected" it again, to
> make sure).
> Settings show SATA Port 0, Solid State Drive and "Hot Pluggable", are
> both currently selected, but I think they were originally unset.
>
> I've tried various things (redundantly..), but I hope someone can assist
> me.  Thank you!

Troubleshooting "No Bootable Medium Found" Error in VirtualBox

https://itsfoss.com/virtualbox-no-bootable-medium-found/

Re: Can't access boot drive (vdi)

<vAVML.249463$5S78.76396@fx48.iad>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5591&group=alt.os.linux.mint#5591

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx48.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Subject: Re: Can't access boot drive (vdi)
Content-Language: en-US
Newsgroups: alt.os.linux.mint
References: <_JGML.1676663$vBI8.591869@fx15.iad>
<ttvfuu$2q1mc$1@paganini.bofh.team>
From: nonegi...@att.net (Bill)
In-Reply-To: <ttvfuu$2q1mc$1@paganini.bofh.team>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: Avast (VPS 230304-12, 3/4/2023), Outbound message
X-Antivirus-Status: Clean
Lines: 28
Message-ID: <vAVML.249463$5S78.76396@fx48.iad>
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Sun, 05 Mar 2023 05:16:11 UTC
Date: Sun, 5 Mar 2023 00:16:11 -0500
X-Received-Bytes: 1933
 by: Bill - Sun, 5 Mar 2023 05:16 UTC

On 3/4/2023 8:09 AM, Andrei Z. wrote:
> Bill wrote:
>> I did a clean install of VirtualBox 7.06 (on Windows 10 Pro), and
>> installed LM 21.1.
>>
>> All went well. On subsequent restart I get the error (copied from the
>> Log)
>>
>> 00:00:08.027292 VMMDev: Guest Log: BIOS: Boot from Hard Disk 0 failed
>> 00:00:08.027878 VMMDev: Guest Log: BIOS: No bootable medium found!
>>
>> The proper dvi file is shown in the "Storage" (I "selected" it again,
>> to make sure).
>> Settings show SATA Port 0, Solid State Drive and "Hot Pluggable", are
>> both currently selected, but I think they were originally unset.
>>
>> I've tried various things (redundantly..), but I hope someone can
>> assist me.  Thank you!
>
> Troubleshooting "No Bootable Medium Found" Error in VirtualBox
>
> https://itsfoss.com/virtualbox-no-bootable-medium-found/
>

Thank you for this! It makes me feel like I'm in good company--instead
of being the only one encountering this problem. I think I'll "start
fresh". I did such a thorough job of customizing my installation I was
hesitating about doing that.

Re: Can't access boot drive (vdi)

<weYML.1796355$GNG9.1299386@fx18.iad>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5592&group=alt.os.linux.mint#5592

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx18.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Subject: Re: Can't access boot drive (vdi)
Content-Language: en-US
Newsgroups: alt.os.linux.mint
References: <_JGML.1676663$vBI8.591869@fx15.iad>
<ttvfuu$2q1mc$1@paganini.bofh.team> <vAVML.249463$5S78.76396@fx48.iad>
From: nonegi...@att.net (Bill)
In-Reply-To: <vAVML.249463$5S78.76396@fx48.iad>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: Avast (VPS 230304-12, 3/4/2023), Outbound message
X-Antivirus-Status: Clean
Lines: 31
Message-ID: <weYML.1796355$GNG9.1299386@fx18.iad>
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Sun, 05 Mar 2023 08:17:32 UTC
Date: Sun, 5 Mar 2023 03:17:32 -0500
X-Received-Bytes: 2098
 by: Bill - Sun, 5 Mar 2023 08:17 UTC

On 3/5/2023 12:16 AM, Bill wrote:
> On 3/4/2023 8:09 AM, Andrei Z. wrote:
>> Bill wrote:
>>> I did a clean install of VirtualBox 7.06 (on Windows 10 Pro), and
>>> installed LM 21.1.
>>>
>>> All went well. On subsequent restart I get the error (copied from the
>>> Log)
>>>
>>> 00:00:08.027292 VMMDev: Guest Log: BIOS: Boot from Hard Disk 0 failed
>>> 00:00:08.027878 VMMDev: Guest Log: BIOS: No bootable medium found!
>>>
>>> The proper dvi file is shown in the "Storage" (I "selected" it again,
>>> to make sure).
>>> Settings show SATA Port 0, Solid State Drive and "Hot Pluggable", are
>>> both currently selected, but I think they were originally unset.
>>>
>>> I've tried various things (redundantly..), but I hope someone can
>>> assist me.  Thank you!
>>
>> Troubleshooting "No Bootable Medium Found" Error in VirtualBox
>>
>> https://itsfoss.com/virtualbox-no-bootable-medium-found/
>>
>
> Thank you for this! It makes me feel like I'm in good company--instead
> of being the only one encountering this problem. I think I'll "start
> fresh". I did such a thorough job of customizing my installation I was
> hesitating about doing that.

Didn't work. Next time I'll try "installing" in EFI mode.

Re: Can't access boot drive (vdi)

<tu1o14$19dqj$1@dont-email.me>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5593&group=alt.os.linux.mint#5593

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Can't access boot drive (vdi)
Date: Sun, 5 Mar 2023 04:39:48 -0500
Organization: A noiseless patient Spider
Lines: 24
Message-ID: <tu1o14$19dqj$1@dont-email.me>
References: <_JGML.1676663$vBI8.591869@fx15.iad>
<ttvfuu$2q1mc$1@paganini.bofh.team> <vAVML.249463$5S78.76396@fx48.iad>
<weYML.1796355$GNG9.1299386@fx18.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 5 Mar 2023 09:39:48 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="8cbd2dbee657433a28d1f197436ddc6e";
logging-data="1357651"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19ulUMReFgHc5NnIWxM9VBmnU5nlOVS+Po="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:94RwpVlgpzdBj45qMSrbCHYhLtI=
In-Reply-To: <weYML.1796355$GNG9.1299386@fx18.iad>
Content-Language: en-US
 by: Paul - Sun, 5 Mar 2023 09:39 UTC

On 3/5/2023 3:17 AM, Bill wrote:

>
> Didn't work.  Next time I'll try "installing" in EFI mode.

The EFI popup boot key is <esc>, and depending on the hosting
software, you have to hammer the living shit out of that key,
to meet the tiny timing window.

If successful, you can select a storage device in the Guest
as the boot device.

This covers cases where the machine throws a "No bueno" and
refuses to admit anything bootable is in there.

Look in the Guest settings, for the tick box to turn on EFI support.

Enable EFI (special OSes only)

You would turn that on, before the install, and boot your hybrid ISO
with that enabled.

Paul

Re: Can't access boot drive (vdi)

<mPZML.1796358$GNG9.333245@fx18.iad>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5594&group=alt.os.linux.mint#5594

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!feeder1.feed.usenet.farm!feed.usenet.farm!peer02.ams4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx18.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Subject: Re: Can't access boot drive (vdi)
Content-Language: en-US
Newsgroups: alt.os.linux.mint
References: <_JGML.1676663$vBI8.591869@fx15.iad>
<ttvfuu$2q1mc$1@paganini.bofh.team> <vAVML.249463$5S78.76396@fx48.iad>
<weYML.1796355$GNG9.1299386@fx18.iad> <tu1o14$19dqj$1@dont-email.me>
From: nonegi...@att.net (Bill)
In-Reply-To: <tu1o14$19dqj$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: Avast (VPS 230304-12, 3/4/2023), Outbound message
X-Antivirus-Status: Clean
Lines: 30
Message-ID: <mPZML.1796358$GNG9.333245@fx18.iad>
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Sun, 05 Mar 2023 10:05:06 UTC
Date: Sun, 5 Mar 2023 05:05:08 -0500
X-Received-Bytes: 1864
 by: Bill - Sun, 5 Mar 2023 10:05 UTC

On 3/5/2023 4:39 AM, Paul wrote:
> On 3/5/2023 3:17 AM, Bill wrote:
>
>>
>> Didn't work.  Next time I'll try "installing" in EFI mode.
>
> The EFI popup boot key is <esc>, and depending on the hosting
> software, you have to hammer the living shit out of that key,
> to meet the tiny timing window.
>
> If successful, you can select a storage device in the Guest
> as the boot device.
>
> This covers cases where the machine throws a "No bueno" and
> refuses to admit anything bootable is in there.
>
> Look in the Guest settings, for the tick box to turn on EFI support.
>
>        Enable EFI (special OSes only)
>
> You would turn that on, before the install, and boot your hybrid ISO
> with that enabled.
>
>    Paul
>

Yes, I'm going to try that. It didn't help using it (only) post install.

Thanks!

Re: Can't access boot drive (vdi)

<Hk1NL.1014944$Tcw8.523180@fx10.iad>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5597&group=alt.os.linux.mint#5597

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx10.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Subject: Re: Can't access boot drive (vdi)
Content-Language: en-US
Newsgroups: alt.os.linux.mint
References: <_JGML.1676663$vBI8.591869@fx15.iad>
<ttvfuu$2q1mc$1@paganini.bofh.team> <vAVML.249463$5S78.76396@fx48.iad>
<weYML.1796355$GNG9.1299386@fx18.iad> <tu1o14$19dqj$1@dont-email.me>
From: nonegi...@att.net (Bill)
In-Reply-To: <tu1o14$19dqj$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: Avast (VPS 230305-6, 3/5/2023), Outbound message
X-Antivirus-Status: Clean
Lines: 31
Message-ID: <Hk1NL.1014944$Tcw8.523180@fx10.iad>
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Sun, 05 Mar 2023 14:05:27 UTC
Date: Sun, 5 Mar 2023 09:05:28 -0500
X-Received-Bytes: 2084
 by: Bill - Sun, 5 Mar 2023 14:05 UTC

On 3/5/2023 4:39 AM, Paul wrote:
> On 3/5/2023 3:17 AM, Bill wrote:
>
>>
>> Didn't work.  Next time I'll try "installing" in EFI mode.
>
> The EFI popup boot key is <esc>, and depending on the hosting
> software, you have to hammer the living shit out of that key,
> to meet the tiny timing window.
>
> If successful, you can select a storage device in the Guest
> as the boot device.
>
> This covers cases where the machine throws a "No bueno" and
> refuses to admit anything bootable is in there.
>
> Look in the Guest settings, for the tick box to turn on EFI support.
>
>        Enable EFI (special OSes only)
>
> You would turn that on, before the install, and boot your hybrid ISO
> with that enabled.
>
>    Paul

It brings me into "UEFI mode", and while I tried alot of things, I
couldn't proceed through it (with "continue") to do the install. I
presume I was to try to boot the virtual "optical" driver so that it
would see my iso file. Is there a command, besides "exit" from the UEFI
mode I might find useful?

Re: Can't access boot drive (vdi)

<tu3qvv$1jp43$1@dont-email.me>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5606&group=alt.os.linux.mint#5606

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Can't access boot drive (vdi)
Date: Sun, 5 Mar 2023 23:42:39 -0500
Organization: A noiseless patient Spider
Lines: 40
Message-ID: <tu3qvv$1jp43$1@dont-email.me>
References: <_JGML.1676663$vBI8.591869@fx15.iad>
<ttvfuu$2q1mc$1@paganini.bofh.team> <vAVML.249463$5S78.76396@fx48.iad>
<weYML.1796355$GNG9.1299386@fx18.iad> <tu1o14$19dqj$1@dont-email.me>
<Hk1NL.1014944$Tcw8.523180@fx10.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 6 Mar 2023 04:42:39 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="25f3fa48a5293ee6562060bb9109d048";
logging-data="1696899"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+TP0m2ZX6FwxtheTSSgUz+O9LYDB+9dec="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:mruKhxXwuSJCmeT/Uzhh9vEgXTg=
In-Reply-To: <Hk1NL.1014944$Tcw8.523180@fx10.iad>
Content-Language: en-US
 by: Paul - Mon, 6 Mar 2023 04:42 UTC

On 3/5/2023 9:05 AM, Bill wrote:
> On 3/5/2023 4:39 AM, Paul wrote:
>> On 3/5/2023 3:17 AM, Bill wrote:
>>
>>>
>>> Didn't work.  Next time I'll try "installing" in EFI mode.
>>
>> The EFI popup boot key is <esc>, and depending on the hosting
>> software, you have to hammer the living shit out of that key,
>> to meet the tiny timing window.
>>
>> If successful, you can select a storage device in the Guest
>> as the boot device.
>>
>> This covers cases where the machine throws a "No bueno" and
>> refuses to admit anything bootable is in there.
>>
>> Look in the Guest settings, for the tick box to turn on EFI support.
>>
>>         Enable EFI (special OSes only)
>>
>> You would turn that on, before the install, and boot your hybrid ISO
>> with that enabled.
>>
>>     Paul
>
> It brings me into "UEFI mode", and while I tried alot of things, I couldn't proceed through it (with "continue") to do the install. I presume I was to try to boot the virtual "optical" driver so that it would see my iso file. Is there a command, besides "exit" from the UEFI mode I might find useful?
>

Does it look like this, when you hammer <esc> key ?

[Picture]

https://i.postimg.cc/kgbgJTrD/Boot-Manager-via-ESC-key.gif

It's one of those tab and arrow key things, <cr> when you
land on the desired entry.

Paul

Re: Can't access boot drive (vdi)

<qpeNL.937811$MVg8.48745@fx12.iad>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5607&group=alt.os.linux.mint#5607

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx12.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Subject: Re: Can't access boot drive (vdi)
Content-Language: en-US
Newsgroups: alt.os.linux.mint
References: <_JGML.1676663$vBI8.591869@fx15.iad>
<ttvfuu$2q1mc$1@paganini.bofh.team> <vAVML.249463$5S78.76396@fx48.iad>
<weYML.1796355$GNG9.1299386@fx18.iad> <tu1o14$19dqj$1@dont-email.me>
<Hk1NL.1014944$Tcw8.523180@fx10.iad> <tu3qvv$1jp43$1@dont-email.me>
From: nonegi...@att.net (Bill)
In-Reply-To: <tu3qvv$1jp43$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: Avast (VPS 230305-10, 3/5/2023), Outbound message
X-Antivirus-Status: Clean
Lines: 53
Message-ID: <qpeNL.937811$MVg8.48745@fx12.iad>
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Mon, 06 Mar 2023 04:57:58 UTC
Date: Sun, 5 Mar 2023 23:57:59 -0500
X-Received-Bytes: 2861
 by: Bill - Mon, 6 Mar 2023 04:57 UTC

On 3/5/2023 11:42 PM, Paul wrote:
> On 3/5/2023 9:05 AM, Bill wrote:
>> On 3/5/2023 4:39 AM, Paul wrote:
>>> On 3/5/2023 3:17 AM, Bill wrote:
>>>
>>>>
>>>> Didn't work.  Next time I'll try "installing" in EFI mode.
>>>
>>> The EFI popup boot key is <esc>, and depending on the hosting
>>> software, you have to hammer the living shit out of that key,
>>> to meet the tiny timing window.
>>>
>>> If successful, you can select a storage device in the Guest
>>> as the boot device.
>>>
>>> This covers cases where the machine throws a "No bueno" and
>>> refuses to admit anything bootable is in there.
>>>
>>> Look in the Guest settings, for the tick box to turn on EFI support.
>>>
>>>         Enable EFI (special OSes only)
>>>
>>> You would turn that on, before the install, and boot your hybrid ISO
>>> with that enabled.
>>>
>>>     Paul
>>
>> It brings me into "UEFI mode", and while I tried alot of things, I
>> couldn't proceed through it (with "continue") to do the install. I
>> presume I was to try to boot the virtual "optical" driver so that it
>> would see my iso file. Is there a command, besides "exit" from the
>> UEFI mode I might find useful?
>>
>
> Does it look like this, when you hammer <esc> key ?
>
>    [Picture]
>
>    https://i.postimg.cc/kgbgJTrD/Boot-Manager-via-ESC-key.gif
>
> It's one of those tab and arrow key things, <cr> when you
> land on the desired entry.
>
>    Paul
>

Yes, I was able to do the install through the (virtual) optical drive.
Vut after trying to boot again I can't get passed that "boot
manager"--unless I direct it to reboot from the optical drive (iso). I
tried the process again today using an "admin" account, but that didn't
seem to help. Something I read made me wonder whether "Windows Defender"
could be getting in the way.

Re: Can't access boot drive (vdi)

<tu4d8t$1lff2$1@dont-email.me>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5609&group=alt.os.linux.mint#5609

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Can't access boot drive (vdi)
Date: Mon, 6 Mar 2023 04:54:37 -0500
Organization: A noiseless patient Spider
Lines: 74
Message-ID: <tu4d8t$1lff2$1@dont-email.me>
References: <_JGML.1676663$vBI8.591869@fx15.iad>
<ttvfuu$2q1mc$1@paganini.bofh.team> <vAVML.249463$5S78.76396@fx48.iad>
<weYML.1796355$GNG9.1299386@fx18.iad> <tu1o14$19dqj$1@dont-email.me>
<Hk1NL.1014944$Tcw8.523180@fx10.iad> <tu3qvv$1jp43$1@dont-email.me>
<qpeNL.937811$MVg8.48745@fx12.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 6 Mar 2023 09:54:38 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="d078ebf8b302532ebd0dfea6b1896328";
logging-data="1752546"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19+WCO5MNOq3s7yIJbBUf9JY99rCcFAOzM="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:xUWHF0GIGZp1le7dOgvnsSdh/8o=
Content-Language: en-US
In-Reply-To: <qpeNL.937811$MVg8.48745@fx12.iad>
 by: Paul - Mon, 6 Mar 2023 09:54 UTC

On 3/5/2023 11:57 PM, Bill wrote:
> On 3/5/2023 11:42 PM, Paul wrote:
>> On 3/5/2023 9:05 AM, Bill wrote:
>>> On 3/5/2023 4:39 AM, Paul wrote:
>>>> On 3/5/2023 3:17 AM, Bill wrote:
>>>>
>>>>>
>>>>> Didn't work.  Next time I'll try "installing" in EFI mode.
>>>>
>>>> The EFI popup boot key is <esc>, and depending on the hosting
>>>> software, you have to hammer the living shit out of that key,
>>>> to meet the tiny timing window.
>>>>
>>>> If successful, you can select a storage device in the Guest
>>>> as the boot device.
>>>>
>>>> This covers cases where the machine throws a "No bueno" and
>>>> refuses to admit anything bootable is in there.
>>>>
>>>> Look in the Guest settings, for the tick box to turn on EFI support.
>>>>
>>>>         Enable EFI (special OSes only)
>>>>
>>>> You would turn that on, before the install, and boot your hybrid ISO
>>>> with that enabled.
>>>>
>>>>     Paul
>>>
>>> It brings me into "UEFI mode", and while I tried alot of things, I couldn't proceed through it (with "continue") to do the install. I presume I was to try to boot the virtual "optical" driver so that it would see my iso file. Is there a command, besides "exit" from the UEFI mode I might find useful?
>>>
>>
>> Does it look like this, when you hammer <esc> key ?
>>
>>     [Picture]
>>
>>     https://i.postimg.cc/kgbgJTrD/Boot-Manager-via-ESC-key.gif
>>
>> It's one of those tab and arrow key things, <cr> when you
>> land on the desired entry.
>>
>>     Paul
>>
>
> Yes, I was able to do the install through the (virtual) optical drive.
> Vut after trying to boot again I can't get passed that "boot manager"--unless I direct it to reboot from the optical drive (iso).  I tried the process again today using an "admin" account, but that didn't seem to help. Something I read made me wonder whether "Windows Defender" could be getting in the way.
>

I don't think Windows would interfere with VirtualBox internal operations.

Here, you can see the GRUB points to GPT2, which agrees with gnome-disks.

[Picture]

https://i.postimg.cc/8zb2Cgzy/EFI-LM211-in-Virtualbox.gif

Booting (with EFI enabled) was uneventful.

The shutdown of the install session froze on me (did not seem
to answer ping), so the ending of that was abnormal, but I think
it likely the partition was put away, before it blew.

Booting my new install, it shut down normally.

You can see I used "testdisk" and "gnome-disks" to check out my
boot materials. The EFI has a Ubuntu folder, which is used by
LinuxMint. No other OSes were present (the demo is a uni-boot).

Those are tools you can use from the LiveDVD, should you choose
to boot it inside that environment again.

You could also use the Boot Rescue inside that environment,
but I don't see a reason to get excited just yet..

Paul

Re: Can't access boot drive (vdi)

<A1BNL.1449373$iU59.114817@fx14.iad>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=5625&group=alt.os.linux.mint#5625

  copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.uzoreto.com!peer01.ams4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx14.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Subject: Re: Can't access boot drive (vdi)
Content-Language: en-US
Newsgroups: alt.os.linux.mint
References: <_JGML.1676663$vBI8.591869@fx15.iad>
From: nonegi...@att.net (Bill)
In-Reply-To: <_JGML.1676663$vBI8.591869@fx15.iad>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: Avast (VPS 230306-0, 3/5/2023), Outbound message
X-Antivirus-Status: Clean
Lines: 22
Message-ID: <A1BNL.1449373$iU59.114817@fx14.iad>
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Tue, 07 Mar 2023 06:42:40 UTC
Date: Tue, 7 Mar 2023 01:42:40 -0500
X-Received-Bytes: 1628
 by: Bill - Tue, 7 Mar 2023 06:42 UTC

On 3/4/2023 7:22 AM, Bill wrote:
> I did a clean install of VirtualBox 7.06 (on Windows 10 Pro), and
> installed LM 21.1.
>
> All went well. On subsequent restart I get the error (copied from the Log)
>
> 00:00:08.027292 VMMDev: Guest Log: BIOS: Boot from Hard Disk 0 failed
> 00:00:08.027878 VMMDev: Guest Log: BIOS: No bootable medium found!

I watched a YouTube video on how to do this install. I thought, not much
new here. Then when I tried again, I recalled that the person in the
video clicked on the "Install Linux Mint" icon on the virtual desktop...

Color me, :::embarrassed::: !

I apologize, especially to Paul.

I'm going to do it all over again, and get the installation "just right".

Thank you for your support!

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor