News Enthusiast's motherboard BIOS update is taking more than 24 hours — somehow it's still going

Do SATA SSDs fall back into a slower read, like ATA-33, when the drive has read errors?

Alternatively, watch it turn out this was a BIOS bug and Biostar patches it in a few months.
 
  • Like
Reactions: artk2219
Do SATA SSDs fall back into a slower read, like ATA-33, when the drive has read errors?

Alternatively, watch it turn out this was a BIOS bug and Biostar patches it in a few months.
I wondered if it was something like that as well, but using your specific example, even ATA-33 at just under 33 MB/sec, it would be able to write the entire BIOS bin file in about a second, which obviously wouldn't happen that fast as these EEPROM chips can't write nearly that quickly.

That said, it does seem like there's a bug that's causing data to bus from the SSD to the EEPROM at practically bits per second, but I'd love to here my hypotheses on this.

Either way, wild!! Floppy flashing wasn't nearly that slow either, in case anyone was wondering that has never experienced such.
 
That said, it does seem like there's a bug that's causing data to bus from the SSD to the EEPROM at practically bits per second, but I'd love to here my hypotheses on this.

Either way, wild!! Floppy flashing wasn't nearly that slow either, in case anyone was wondering that has never experienced such.
That was my first thought - I've been building computers since even before Computer Shopper was an inch-thick Bible we got at the newsstand... Updating BIOS from a 5.25 floppy never took more than a few minutes.

Something's gone really wonky with this update, I will be really surprised if it's functional after. He might have to go with the way we updated BIOS before the floppy days - replacing the chip! (or flashing it in place, if possible)
 
Geez that'd be nerve wracking. BIOS updates always make me a bit nervous but usually only for 5 minutes. I'm with those who think it may be reading the SSD at some insanely low speed. Best of luck to them!
 
  • Like
Reactions: artk2219
That was my first thought - I've been building computers since even before Computer Shopper was an inch-thick Bible we got at the newsstand... Updating BIOS from a 5.25 floppy never took more than a few minutes.

Something's gone really wonky with this update, I will be really surprised if it's functional after. He might have to go with the way we updated BIOS before the floppy days - replacing the chip! (or flashing it in place, if possible)
Computer Shopper! Thanks for the memory.
 
  • Like
Reactions: artk2219
Watch it finish and it still has the old bios on and didn't even flash. That would be the time it goes up for sale on marketplace. Someone else can deal with the cursed machine.
 
  • Like
Reactions: artk2219
Oh, oh, I had a very similar experience with my ASRock A320M (the cheapest motherboard I could find back then)...

Tried to update the BIOS when I wanted to upgrade from a Ryzen 3 1200 to a Ryzen 5 2600... It was still stuck at 30% after waiting for 12+ hours.. Cue me perusing countless forum posts on "Can you shut down the PC when the BIOS update seems stuck?".. I probably still have pictures of it somewhere...

It ended up failing due to power outage. I simply took it as a sign.... and an excuse to upgrade to an X370 platform..
 
  • Like
Reactions: artk2219
Do SATA SSDs fall back into a slower read, like ATA-33, when the drive has read errors?

Alternatively, watch it turn out this was a BIOS bug and Biostar patches it in a few months.
You're referring to the interface speed. Back then if your cable couldn't negotiate a faster speed then yes, it will fallback to a slower speed.

Within the SSD (or CD-ROM... or anything) itself, if it has read errors it will also attempt to re-read. Check out Samsung SSD charge loss incident.
 
  • Like
Reactions: artk2219
Although not hurting the BIOS update process, the 4 gig of RAM is hurting. Everything else. This guy ought to add two 8 gig sticks if he could find them. Decent quality used ones. Probably wouldn't be much more than 30 bucks.
 
  • Like
Reactions: artk2219
Oh, oh, I had a very similar experience with my ASRock A320M (the cheapest motherboard I could find back then)...

Tried to update the BIOS when I wanted to upgrade from a Ryzen 3 1200 to a Ryzen 5 2600... It was still stuck at 30% after waiting for 12+ hours.. Cue me perusing countless forum posts on "Can you shut down the PC when the BIOS update seems stuck?".. I probably still have pictures of it somewhere...

It ended up failing due to power outage. I simply took it as a sign.... and an excuse to upgrade to an X370 platform..

I also had a similar problem with an older Biostar MB, don't remember the board# but it was back in the AM3 days...turned out the CMOS battery was dead, making the BIOS update fail after a couple of hours (didn't brick anything, though). Replaced the battery and then all was well. I think I donated that MB to a school or something.
 
Seriously … this is what constitute news today? Or advertisement views for your viral video … my process on my PC doesn’t work as expected …. I’m sure everyone who has built, manages, updates or is an enthusiast has experienced this isht a long running process, a bios update that doesn’t go as planned … or whatever … how and why is this news worthy … the bait is that this is the bait.
 
I also had a similar problem with an older Biostar MB, don't remember the board# but it was back in the AM3 days...turned out the CMOS battery was dead, making the BIOS update fail after a couple of hours (didn't brick anything, though). Replaced the battery and then all was well. I think I donated that MB to a school or something.

I... didn't check the CMOS battery back then.. For me though, mine's probably bricked, or something is horribly wrong with it.. No signs of life at all, as if the power isn't even plugged in..

It was a cheapo motherboard though, so I didn't care about it really... Still, the only time I tried fiddling with the BIOS, and it ended up really badly...