> On 15 Jul 2023, at 22:51, Michael Hennebry
> wrote:
>
> I was expecting that there would be some time between
> the first corrupt block and an irreparable filing system.
> From subsequent reading, there is,
> but the SSD does a good job of hiding corrupt blocks.
> A better tactic would be
On Thu, 13 Jul 2023, Samuel Sieb wrote:
On 7/13/23 21:08, Michael Hennebry wrote:
If you really want a warning and all else fails,
use your own checksums.
Have a process walk the filesystem.
If a file is open for writing, skip it.
If a file is older than the recorded checksum,
test the
On 7/14/23 03:29, Michael D. Setzer II via users wrote:
Not very happy with WD support, was actually looking for info to
figure out what happened with drive versus trying to get a
replacement, but that seems all they are concerned about NOT
DOING.
There's no way they could tell how or why it
On 14 Jul 2023 at 15:08, Barry wrote:
From: Barry
Subject:Re: WD BLUE SSD died. Not even seen in BIOS or
via USB? Bad Response from WD Support.
Date sent: Fri, 14 Jul 2023 15:08:56 +0100
To: mi...@guam.net,
Community
> On 14 Jul 2023, at 11:29, Michael D. Setzer II via users
> wrote:
>
> The two WD Black drives I just ordered and
> seller sent serial numbers without being asked. WD Support comes
> back that those serial numbers were meant for drives installed in
> systems, so WD provides no warranty.
On Fri, Jul 14, 2023 at 7:29 AM Michael D. Setzer II via users <
users@lists.fedoraproject.org> wrote:
> Not very happy with WD support, was actually looking for info to
> figure out what happened with drive versus trying to get a
> replacement, but that seems all they are concerned about NOT
>
On 13 Jul 2023 at 21:43, Samuel Sieb wrote:
Date sent: Thu, 13 Jul 2023 21:43:34 -0700
Subject:Re: WD BLUE SSD died. Not even seen in BIOS or
via USB?
To: users@lists.fedoraproject.org
From: Samuel Sieb
Send reply
On 7/13/23 21:08, Michael Hennebry wrote:
If you really want a warning and all else fails,
use your own checksums.
Have a process walk the filesystem.
If a file is open for writing, skip it.
If a file is older than the recorded checksum,
test the checksum.
Write a new checksum.
Where to put the
If you really want a warning and all else fails,
use your own checksums.
Have a process walk the filesystem.
If a file is open for writing, skip it.
If a file is older than the recorded checksum,
test the checksum.
Write a new checksum.
Where to put the checksums is left as an exercise for the
On 7/13/23 07:40, Michael D. Setzer II via users wrote:
Drives where purchase via ebay. Found I had 18 messages in my
ebay folder that had WD BLUE in them. Seems there are usually 3
messages for each order, once for order, shipping, an then when
received. some orders were single drives, while
On Wed, Jul 12, 2023 at 6:53 PM Michael D. Setzer II via users <
users@lists.fedoraproject.org> wrote:
> Had the WD SSD just die in one of my 5 Home Fedora 37
> machines. Reply from WD is just it is out of warranty.
>
> Wondering if others are seeing this or it is just one bad drive.
>
According
On 13 Jul 2023 at 17:38, Barry Scott wrote:
From: Barry Scott
Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB?
Date sent: Thu, 13 Jul 2023 17:38:28 +0100
Copies to: "George N. White III"
To: "Michael D. Setzer" ,
Community supp
> On 13 Jul 2023, at 15:40, Michael D. Setzer II via users
> wrote:
>
> Drives where purchase via ebay.
I personally would be concerned to by critical components from ebay.
Its bad enough trusting the disk makers...
What I have been doing for years is buying so-called enterprise HDD that
On 13 Jul 2023 at 10:09, George N. White III wrote:
From: "George N. White III"
Date sent: Thu, 13 Jul 2023 10:09:08 -0300
Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB?
To: mi...@guam.net,
Community support for Fedora users
Send reply to:
On 13 Jul 2023 at 9:50, George N. White III wrote:
From: "George N. White III"
Date sent: Thu, 13 Jul 2023 09:50:57 -0300
Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB?
To: mi...@guam.net,
Community support for Fedora users
Send reply to:
On Thu, Jul 13, 2023 at 3:19 AM Michael D. Setzer II via users <
users@lists.fedoraproject.org> wrote:
> Hopefully, this is just a random failure and others will be running
> for years. Had some maxtor drives that were still running after 10
> years. Drive was made in 09Sep2022 so isn't even a
On Wed, Jul 12, 2023 at 7:53 PM Michael D. Setzer II via users <
users@lists.fedoraproject.org> wrote:
> Had the WD SSD just die in one of my 5 Home Fedora 37
> machines. Reply from WD is just it is out of warranty.
>
I've had the same reply many times -- I always hope for a secret extension
for
On Thu, 2023-07-13 at 16:18 +1000, Michael D. Setzer II wrote:
> Never opened an ssd drive, or even it it is possible.
I have, it just looks like a circuit board with RAM chips on it, like a
squarer version of the motherboard RAM cards.
I reckon you'd need a special rig for each board and have
On 7/12/23 23:18, Michael D. Setzer II via users wrote:
On 12 Jul 2023 at 21:49, ToddAndMargo via users wrote:
Date sent: Wed, 12 Jul 2023 21:49:34 -0700
Subject:Re: WD BLUE SSD died. Not even seen in BIOS or
via USB?
To: users
On 12 Jul 2023 at 21:49, ToddAndMargo via users wrote:
Date sent: Wed, 12 Jul 2023 21:49:34 -0700
Subject:Re: WD BLUE SSD died. Not even seen in BIOS or
via USB?
To: users@lists.fedoraproject.org
Send reply to: Community support
it
reported machine was down. Check machine, and it was showing
errors. So went to reboot it to run fsck, but on reboot, it doesn't
even see the disk in bios.
Tried different cables, and different ports, and even hooked it to
other computers, but no response at all. dmesg doesn't even show
anything when
, and it was showing
errors. So went to reboot it to run fsck, but on reboot, it doesn't
even see the disk in bios.
Tried different cables, and different ports, and even hooked it to
other computers, but no response at all. dmesg doesn't even show
anything when hooked with a USB adapter..
Hooked the old
Roger Heflin:
>> And the bios will have no way to know what is hot-swappable as that is
>> an external case feature/add-on enclosure.
Philip Rhoades:
> Not sure what you mean - I can set "Hot Swappable" in the BIOS.
For something to be hotswappable, everything has to
On 8/21/22 23:23, Philip Rhoades via users wrote:
I think he is stuck with booting into BIOS
It does look like it . . a bit sad . .
Just out of curiosity, is there some reason why
you can't reboot? User have hot tar and feathers
waiting for you
It generally is worse than that.
It should be almost trivial to code, if you have the internal document
for each bios version laying out the structure that is stored in the
nvram. The other issue is even though it is trivial, the structure
could be different between bios versions in the same MB
drives are
hot-swappable
but dmidecode does not supply that information - is there some way of
getting the info without rebooting into the BIOS setup screen? I am
running F36.
Tangential approach - download the manual for the board.
That won't help. They could be set either way.
Correct.
I
Roger,
On 2022-08-22 06:40, Roger Heflin wrote:
Generally there is no standard for how anything is encoded/decoded in
the bios.
Ah . .
Each vendor does it a slightly different way even on different bios
versions. You would need a vendor tool that works for the specific
motherboard
- is there some way of
getting the info without rebooting into the BIOS setup screen? I am
running F36.
Tangential approach - download the manual for the board.
That won't help. They could be set either way.
I think he is stuck with booting into BIOS
> getting the info without rebooting into the BIOS setup screen? I am
> running F36.
Tangential approach - download the manual for the board.
--
uname -rsvp
Linux 3.10.0-1160.76.1.el7.x86_64 #1 SMP Wed Aug 10 16:21:17 UTC 2022 x86_64
Boilerplate: All unexpected mail to my mailbox i
Generally there is no standard for how anything is encoded/decoded in the bios.
Each vendor does it a slightly different way even on different bios
versions. You would need a vendor tool that works for the specific
motherboard.
And the bios will have no way to know what is hot-swappable
People,
I have a fairly recent ASUS ROG motherboard that I want to interrogate
from the CLI - specifically to see which SATA drives are hot-swappable
but dmidecode does not supply that information - is there some way of
getting the info without rebooting into the BIOS setup screen? I am
media.
It's commonly used for BIOS PXE booting as well.
*shudders at the memories of dealing with pxelinux*
GRUB is way better for that. Yes, you can use GRUB for PXE and UEFI netboot too.
That's what I use for both.
Would you care to document your set-ups?
It's pretty simple. I just
On Tue, May 25, 2021 at 9:43 PM Samuel Sieb wrote:
> On 2021-05-25 6:10 p.m., Fulko Hew wrote:
> > I'm trying to do some Y2038 testing, using VMs.
> > So what I'd like to do is have the time pre-set to after the Y2038 time
> > and then boot an OS/VM (to have the 'BIOS' provi
On 2021-05-25 6:10 p.m., Fulko Hew wrote:
I'm trying to do some Y2038 testing, using VMs.
So what I'd like to do is have the time pre-set to after the Y2038 time
and then boot an OS/VM (to have the 'BIOS' provide the post 2038 time).
(In this case I'm trying to test an application under Win XP
I'm trying to do some Y2038 testing, using VMs.
So what I'd like to do is have the time pre-set to after the Y2038 time
and then boot an OS/VM (to have the 'BIOS' provide the post 2038 time).
(In this case I'm trying to test an application under Win XP.)
[Please, no emails about upgrading the OS
so, you probably need to
disable "fastboot" in Windows (to install Fedora and again when Windows
is updated).
>
> At boot time, I can see the menu:
> Install Fedora 33
> Test this media...
> troubleshooting
>
> But that's all... nothing happens if I choose any of the
Le 22/12/2020 à 15:41, Jorge Fábregas a écrit :
On 12/22/20 5:23 AM, François Patte wrote:
What is the right config in the bios to perform a linux install with
these "new" motherboard.
Hi,
There's nothing special really. Either you boot in UEFI mode or Legacy
mode (appea
On 12/22/20 5:23 AM, François Patte wrote:
> What is the right config in the bios to perform a linux install with
> these "new" motherboard.
Hi,
There's nothing special really. Either you boot in UEFI mode or Legacy
mode (appears as "CSM" in firmware options). If you
is the right config in the bios to perform a linux install with
these "new" motherboard.
Thank you for any help.
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6
involve a 2nd disk drive, but now,
these new laptops no longer have easily accessible drives,
and that just makes it all the more difficult and tedious.
P.S. Now that I have the new install, I'm seeing that my CPU fan
is no longer spinning. The Dell/BIOS test program can control
the fan, but Fedor
kup for
it to restore then ...
2) try to enable CSM in your UEFI setup so that your system can boot in
BIOS mode hoping you still have a working MBR and GRUB is installed
there (see if it boots). If that doesn work...
3) grab what you need from booting off the USB stick and be done with
it. Install Fedora
On Sun, Nov 29, 2020 at 8:23 AM Jorge Fábregas
wrote:
> On 11/28/20 11:48 PM, Fulko Hew wrote:
> >
> > 'DEVNAME': '/dev/sda1',
> > 'DEVPATH':
> >
> '/devices/pci:00/:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1',
> > 'ID_FS_TYPE': 'vfat',
> > 'ID_PART_ENTRY_NAME':
On 11/28/20 11:48 PM, Fulko Hew wrote:
>
> 'DEVNAME': '/dev/sda1',
> 'DEVPATH':
> '/devices/pci:00/:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1',
> 'ID_FS_TYPE': 'vfat',
> 'ID_PART_ENTRY_NAME': 'EFI\\x20System\\x20Partition',
> 'ID_PART_ENTRY_NUMBER': '1',
>
On Sat, 2020-11-28 at 22:48 -0500, Fulko Hew wrote:
> What I forgot to say, was that this is a F26 system,
> so I can't find an efibootmgr string.
That's a pretty important detail. F26 was EOLed at the end of May 2018.
You really need to update to at least F32.
poc
On Sat, Nov 28, 2020 at 9:17 PM Jorge Fábregas
wrote:
> On 11/28/20 9:27 PM, Fulko Hew wrote:
> > Any idea what happened to my HD boot info in my BIOS, or how to restore
> it?
> > PS. It is a Dell laptop.
>
> Hi,
>
> I'm assuming you're booting off a UEFI-
On 11/28/20 9:27 PM, Fulko Hew wrote:
> Any idea what happened to my HD boot info in my BIOS, or how to restore it?
> PS. It is a Dell laptop.
Hi,
I'm assuming you're booting off a UEFI-based system and that you lost
the menu entry stored in NVRAM corresponding to "Fedora".
You
and performed my backup.
Now I wanted to go back and try to diagnose/fix my root filesystem issue.
Sadly, my BIOS no longer knows about the bootable entity on the HD,
and only shows me the Flash drive (even if it's not plugged in).
Any idea what happened to my HD boot info in my BIOS, or how
On 5/7/19 7:43 PM, S. Bob wrote:
Oddly enough the slow boot / shutdowns have dissappeared, the only
remaining issue is the bios setting weirdness, including the fact that
Linux will not boot without legacy OS Boot = on
That's not weird. You don't have an EFI boot partition, so you can only
On Tue, May 7, 2019 at 8:44 PM S. Bob wrote:
>
> Oddly enough the slow boot / shutdowns have dissappeared, the only
> remaining issue is the bios setting weirdness, including the fact that
> Linux will not boot without legacy OS Boot = on
>
>
> Thoughts?
F
Oddly enough the slow boot / shutdowns have dissappeared, the only
remaining issue is the bios setting weirdness, including the fact that
Linux will not boot without legacy OS Boot = on
Thoughts?
On 5/7/19 8:08 PM, Chris Murphy wrote:
On Tue, May 7, 2019 at 3:54 PM S. Bob wrote:
root
On 05/07/2019 08:08 PM, Chris Murphy wrote:
You can add '> journal.log' to output to a file and post
it somewhere
Or, you can use | tee journal.log so you can keep a copy and see the
results yourself if you prefer.
___
users mailing list --
On Tue, May 7, 2019 at 3:54 PM S. Bob wrote:
>
> root@F30-host # cat /etc/fstab
>
> #
> # /etc/fstab
> # Created by anaconda on Wed Dec 31 19:25:43 1997
> #
> # Accessible filesystems, by reference, are maintained under '/dev/disk/'.
> # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8)
howing several options, like this:
1. ATA HDD1: HFS512G39TNF-N3A0A
2. ATA HDD2: CT1000MX500SSD4
3. Windows Boot Manager
Then I need to power off again and change the following bios settings,
they always get changed when I hard power off:
Legacy OS Boot - (Gets set to Disabled, Fedora won't boot unle
s to what seems to be a
> windows boot manager, showing several options, like this:
>
> 1. ATA HDD1: HFS512G39TNF-N3A0A
>
> 2. ATA HDD2: CT1000MX500SSD4
>
> 3. Windows Boot Manager
>
>
> Then I need to power off again and change the following bios settings,
> they
to persistent storage
3) If I ever do a hard power off then it boots to what seems to be a
windows boot manager, showing several options, like this:
1. ATA HDD1: HFS512G39TNF-N3A0A
2. ATA HDD2: CT1000MX500SSD4
3. Windows Boot Manager
Then I need to power off again and change the following
that is.
> >> e.g. if something with the Fedora bootloader gets nerfed then it'd
> >> boot Windows.
> >
> >
> > I'm pressing F12 and manually selecting Fedora, but I did later try to
> change the boot order, both with efibootmgr and in the BIOS to no avail.
erything in bootorder, you can just
>> have one. The idea of populating it fully is to have exactly the
>> predictable fallback boot behavior the user wants, whatever that is.
>> e.g. if something with the Fedora bootloader gets nerfed then it'd
>> boot Windows.
>
ack boot behavior the user wants, whatever that is.
> e.g. if something with the Fedora bootloader gets nerfed then it'd
> boot Windows.
>
I'm pressing F12 and manually selecting Fedora, but I did later try to
change the boot order, both with efibootmgr and in the BIOS to no avail.
> > Bo
On Wed, Apr 24, 2019 at 8:02 AM Richard Shaw wrote:
>
> While I had to run it through the shredder I finally sat down and went
> through all the passwords I've ever used and figured it out :)
>
> I turned off Secure Boot but it still won't boot Fedora.
>
> I finally figured out I had to use -v
While I had to run it through the shredder I finally sat down and went
through all the passwords I've ever used and figured it out :)
I turned off Secure Boot but it still won't boot Fedora.
I finally figured out I had to use -v to get what I wanted from efibootmgr:
BootCurrent: 0001
Timeout: 0
; I assume one is for the old system and one for the new.
>
> When I try to go into advanced settings in Win10 to change UEFI settings
> it reboots me but there is a password on the BIOS. I can't remember if I
> set a password of maybe the kids did somehow but I have tried every
to change UEFI settings it
reboots me but there is a password on the BIOS. I can't remember if I set a
password of maybe the kids did somehow but I have tried every password I
have ever used and it won't let me in.
Anyone got any ideas?
Thanks,
Richard
I recently built a new computer from components and decided to see if I
could convert my install from BIOS to UEFI...
I decided against a manual conversion since I had already seen email
traffic that it wasn't a good idea. Instead I decided to do a new install
on the new M.2 SSD and then tie
ng to use it as
> > a VM, or occasionally dual-booting directly into Windows. The VM is set
> > up to use UEFI but my host is running under BIOS, so I need to change
> > one of them to match the other. I prefer to change the host to UEFI as
> > that is the preferred metho
Windows. The VM is set
> up to use UEFI but my host is running under BIOS, so I need to change
> one of them to match the other. I prefer to change the host to UEFI as
> that is the preferred method for running VMs.
>
> So how do I go about it? If I simply boot using UEFI I get the EF
On Mon, 2017-10-23 at 06:47 +0200, fedora wrote:
> That page may be helpful:
>
> http://falstaff.agner.ch/2012/11/20/convert-mbr-partition-table-to-gpt-ubuntu/
Interesting. I'll take a look, thanks.
poc
___
users mailing list --
directly into Windows. The VM is set
up to use UEFI but my host is running under BIOS, so I need to change
one of them to match the other. I prefer to change the host to UEFI as
that is the preferred method for running VMs.
So how do I go about it? If I simply boot using UEFI I get the EFI menu
to use UEFI but my host is running under BIOS, so I need to change
> one of them to match the other. I prefer to change the host to UEFI as
> that is the preferred method for running VMs.
>
> So how do I go about it? If I simply boot using UEFI I get the EFI menu
> with a bunch o
I have a new external drive with Windows 10, cloned from my working
QEMU/KVM setup under F26. I want the option of continuing to use it as
a VM, or occasionally dual-booting directly into Windows. The VM is set
up to use UEFI but my host is running under BIOS, so I need to change
one of them
On Fri, Nov 25, 2016 at 8:44 AM, <octy...@gmail.com> wrote:
> So I am currently having this issues : my hdd is not listed in the bios
> boot menu after installing Fedora in dual boot with Windows 10. To check if
> all the partitions are ok, I used the Fedora live and ever
So I am currently having this issues : my hdd is not listed in the bios boot
menu after installing Fedora in dual boot with Windows 10. To check if all the
partitions are ok, I used the Fedora live and everything seems ok. It lists
both windows and the freshly created Fedora partitions. Still
On Mon, Jul 18, 2016 at 5:18 PM, Samuel Sieb <sam...@sieb.net> wrote:
> On 07/18/2016 01:07 PM, Chris Murphy wrote:
>>
>> On Mon, Jul 18, 2016, 1:40 PM Samuel Sieb <sam...@sieb.net
>> <mailto:sam...@sieb.net>> wrote:
>> Since you are crea
On 07/18/2016 01:07 PM, Chris Murphy wrote:
On Mon, Jul 18, 2016, 1:40 PM Samuel Sieb <sam...@sieb.net
<mailto:sam...@sieb.net>> wrote:
Since you are creating a bios boot partition, you must be using the
non-GPT partition table.
BIOS Boot is where the core.img is embedded wh
On Mon, 2016-07-18 at 20:04 +, Chris Murphy wrote:
> Use gdisk, partition type code EF02. Do this on both disks, install
> normally, post install do
>
> grub2-install /dev/SDA /dev/and
>
> Done.
>
Setting the partition type using gdisk was the necessary step to make
grub2-install happy.
I
On Mon, Jul 18, 2016, 1:40 PM Samuel Sieb <sam...@sieb.net> wrote:
>
> Since you are creating a bios boot partition, you must be using the
> non-GPT partition table.
BIOS Boot is where the core.img is embedded when using GPT partitioning
with BIOS firmware.
---
Chris Murphy
-
Use gdisk, partition type code EF02. Do this on both disks, install
normally, post install do
grub2-install /dev/SDA /dev/and
Done.
---
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
and not the
whole disk?
I was not able to write bios boot twice (sda and sdb), it was only
written on sda (there is plenty of space on sdb as well).
Anaconda partitioner did not allow to define two biosboot partitions.
Yes, anaconda has to draw a line somewhere on how complicated it can
get
Hi
I did a f24 installation using swraid on 4TB disks (predefined swraid
because I am still unhappy with complex tasks and the level disk
abstraction in anaconda, but thats not the point).
I was not able to write bios boot twice (sda and sdb), it was only
written on sda (there is plenty of space
),
all I get is a cursor at upper left corner.
If I disconnect the drive, reboot, then I get the Fedora boot menu,
almost instantly.
Before I select which kernel to boot, I connect this external drive
and boot the latest kernel.
All is well.
So, what has remained on the external drive to cause bios
On Tue, Mar 17, 2015 at 6:45 PM, Rick Stevens ri...@alldigital.com wrote:
It's pretty common for the BIOS to, by default, try to boot external
media (CD ROM, USB, eSATA and such) BEFORE booting a local hard disk.
If it's common, it's a good reason to consider parted's behavior a bug
these days
On 03/17/2015 06:43 PM, Chris Murphy wrote:
No bootloader code.
It has no partition 1 or 2 entry, they're in 3 and 4.
Ooosp! Right.
They are indeed.
there are no other partitions.
I guess you already saw my response to Joe Zeff??
--
users mailing list
users@lists.fedoraproject.org
To
On 03/17/2015 04:23 PM, jd1008 wrote:
Partition 2 is 8GB swap partition.
I formatted partition 2 ext4.
Why, and how? I don't think I've ever seen anaconda ask how a swap
partition is to be formatted, because the kernel doesn't use a
filesystem when reading/writing swap so the partition is
On 03/17/2015 05:58 PM, Chris Murphy wrote:
The solution is to go to firmware setup and define a different drive
as primary. Or zero the first 440 bytes of the external drive e.g. dd
if=/dev/zero of=/dev/sdX bs=440 count=1
Interesting.
I used fdisk.
I guess fdisk does not clear those first
On 03/17/2015 05:04 PM, jd1008 wrote:
Sorry, my bad!!
I meant partition 1 as ext4.
Thank you; that seems much more reasonable.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code
On Tue, Mar 17, 2015 at 5:23 PM, jd1008 jd1...@gmail.com wrote:
Partition 2 is 8GB swap partition.
I formatted partition 2 ext4.
I'm confused because this seems like partition 2 is swap and ext4.
Now, if I power up with this external drive connected (usb3),
all I get is a cursor at upper
On 03/17/2015 05:56 PM, Joe Zeff wrote:
On 03/17/2015 04:23 PM, jd1008 wrote:
Partition 2 is 8GB swap partition.
I formatted partition 2 ext4.
Why, and how? I don't think I've ever seen anaconda ask how a swap
partition is to be formatted, because the kernel doesn't use a
filesystem when
On Tue, Mar 17, 2015 at 6:08 PM, jd1008 jd1...@gmail.com wrote:
On 03/17/2015 05:58 PM, Chris Murphy wrote:
The solution is to go to firmware setup and define a different drive
as primary. Or zero the first 440 bytes of the external drive e.g. dd
if=/dev/zero of=/dev/sdX bs=440 count=1
On 03/17/2015 06:19 PM, Chris Murphy wrote:
dd if=/dev/sdX count=1 2/dev/null | hexdump -C
# dd if=/dev/sdb bs=440 count=1 2/dev/null | hexdump -C
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
||
*
01b0 00 00 00 00 00 00 00 00
On Tue, 17 Mar 2015 17:23:30 -0600
jd1008 wrote:
Now, if I power up with this external drive connected (usb3),
all I get is a cursor at upper left corner.
Sounds to me like the bios is trying to boot from that
drive and can't handle it gracefully. I'd see if you
can change the BIOS boot
On 03/17/2015 06:31 PM, Joe Zeff wrote:
On 03/17/2015 05:04 PM, jd1008 wrote:
Sorry, my bad!!
I meant partition 1 as ext4.
Thank you; that seems much more reasonable.
Well, I just rebooted. I looked into the bios, and the boot order
was to boot from
1. cd/dvd
2. usb drive
3. internal
On Tue, Mar 17, 2015 at 6:28 PM, jd1008 jd1...@gmail.com wrote:
On 03/17/2015 06:19 PM, Chris Murphy wrote:
dd if=/dev/sdX count=1 2/dev/null | hexdump -C
# dd if=/dev/sdb bs=440 count=1 2/dev/null | hexdump -C
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
get the Fedora boot menu,
almost instantly.
Before I select which kernel to boot, I connect this external drive
and boot the latest kernel.
All is well.
So, what has remained on the external drive to cause bios
to hang like that?
This is the partition info:
Disk /dev/sdb: 1.8 TiB
.
The solution is to go to firmware setup and define a different drive
as primary. Or zero the first 440 bytes of the external drive e.g. dd
if=/dev/zero of=/dev/sdX bs=440 count=1
Also, fdisk does not show any boot flag being set on either partition.
I will look into bios settings to see how
.
If I disconnect the drive, reboot, then I get the Fedora boot menu,
almost instantly.
Before I select which kernel to boot, I connect this external drive
and boot the latest kernel.
All is well.
So, what has remained on the external drive to cause bios
to hang like that?
It's pretty common
On Oct 17, 2014, at 5:57 PM, sean darcy seandar...@gmail.com wrote:
I updated the BIOS on an acer EFI laptop. Now there's no grub boot menu, it
just boots to W 8.1.
How do I reinstall grub ?
You don't reinstall it. The problem almost certainly is that the firmware
update blew away
On 10/18/2014 01:57 AM, Robin Laing wrote:
On 2014-10-17 16:45, Pete Travis wrote:
On Oct 17, 2014 3:57 PM, sean darcy seandar...@gmail.com wrote:
I updated the BIOS on an acer EFI laptop. Now there's no grub boot menu,
it just boots to W 8.1.
How do I reinstall grub ?
sean
Maybe you
I updated the BIOS on an acer EFI laptop. Now there's no grub boot menu,
it just boots to W 8.1.
How do I reinstall grub ?
sean
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code
On Oct 17, 2014 3:57 PM, sean darcy seandar...@gmail.com wrote:
I updated the BIOS on an acer EFI laptop. Now there's no grub boot menu,
it just boots to W 8.1.
How do I reinstall grub ?
sean
Maybe you just need to change the boot order?
If not, the next steps vary depending on how you
On 2014-10-17 16:45, Pete Travis wrote:
On Oct 17, 2014 3:57 PM, sean darcy seandar...@gmail.com wrote:
I updated the BIOS on an acer EFI laptop. Now there's no grub boot menu,
it just boots to W 8.1.
How do I reinstall grub ?
sean
Maybe you just need to change the boot order
as many copies as you add
member devices.
Yes, that was what I ended up doing.
I partitioned /dev/sda as I wanted, with space for BIOS boot partition,
and also an EFI partition if I ever would need one (more or less a setup
as described in https://bugzilla.redhat.com/show_bug.cgi?id=1061478 I
1 - 100 of 186 matches
Mail list logo
