Re: Openbsd broke my hard drive twice! Getting frustrated

[Gabriel Guzman]

On 05/04, Andrew Gwozdziewycz wrote:
> Hi Gabe,
> 
> I found it possible to boot and install 5.9 on an XPS 13" (9333)[0], but
> had problems getting the all important suspend to RAM (or anything which
> allowed me to close the lid and reopen to resume work) to work. Were you
> successful in getting this necessary laptop functionality working correctly?
> 
> If so, would you mind sharing your configs? I'd love to reinstall OpenBSD
> on this machine, but can't sacrifice that.

Hi Andrew -- 

Suspend just works for me.  No config necessary.  I just made sure apmd
was running and then either typing zzz, or closing the lid suspends the
machine and opening it wakes it back up. Maybe it was an issue that has
since been fixed?  My machine is also an XPS 13 9333. dmesg included for
good measuere.

gabe.


OpenBSD 5.9-current (GENERIC.MP) #2002: Sun May  1 06:35:58 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8474284032 (8081MB)
avail mem = 8212860928 (7832MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0fc0 (69 entries)
bios0: vendor Dell Inc. version "A06" date 11/07/2014
bios0: Dell Inc. XPS13 9333
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP ASF! HPET LPIT APIC MCFG SSDT SSDT SSDT SSDT SSDT UEFI 
POAT BATB FPDT SLIC UEFI SSDT BGRT CSRT
acpi0: wakeup devices P0P1(S4) GLAN(S4) EHC1(S4) EHC2(S4) XHC_(S4) HDEF(S4) 
TPD4(S4) TPD7(S0) TPD8(S0) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) 
RP03(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.56 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 1596.31 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP03)
acpiprt4 at acpi0: bus -1 (PEG0)
acpiprt5 at acpi0: bus -1 (PEG1)
acpiprt6 at acpi0: bus -1 (PEG2)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@332 mwait.1@0x50), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
"PNP0C14" at acpi0 not configured
"INT3F0D" at acpi0 not configured
"ACPI0008" at acpi0 not configured
"MSFT0001" at acpi0 not configured
"SYN0608" at acpi0 not configured
dwiic0 at acpi0: I2C1 addr 

Re: Openbsd broke my hard drive twice! Getting frustrated

[Gabriel Guzman]

On 05/04, Christoph Viethen wrote:
> Hello,
> 
> on 04.05.2016 05:30, Gabriel Guzman wrote:
> 
> > I figured out the issue.  On my machine (DEL XPS 13) it was the "Intel
> > Rapid Boot" option in BIOS.  Disabling that resolved all my boot issues.
> > I can now boot with MBR or GPT off the internal SSD.  And, I can also
> > access the BIOS with the internal SSD installed in the system (this was
> > not possible before)
> 
> Ooouuhh ... Intel Rapid Start still messing up machines?
> 
> I'm aware your problem may be related to a different phenomenon. Just
> meaning to say: Lenovo (and probably other large vendors as well) released
> BIOS updates during 2014 to fix some rather nasty Intel Rapid Start issues,
> so in case your machine is of sufficient age, you might like to look into
> this.

Thanks for the info!  Yeah, my machine is from right around then. My
BIOS version is from 2014, so it's possible this was fixed with a BIOS
update. 

Thanks,
gabe.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Christoph Viethen]

Hello,

on 04.05.2016 05:30, Gabriel Guzman wrote:


I figured out the issue.  On my machine (DEL XPS 13) it was the "Intel
Rapid Boot" option in BIOS.  Disabling that resolved all my boot issues.
I can now boot with MBR or GPT off the internal SSD.  And, I can also
access the BIOS with the internal SSD installed in the system (this was
not possible before)


Ooouuhh ... Intel Rapid Start still messing up machines?

There was a well-publicised series of problems with a number of 
ThinkPad models (T440p and many relatives) around the end of 2013 / 
early 2014. If I recall correctly, one needed to turn off some sort of 
UEFI mode (which disabled Intel Rapid Start at the same time) to 
prevent bricking the mainboard when installing OSs which were not 
sufficiently micro and soft. Seemed that the "feature" would read some 
data from a particular area of the harddisk, expecting that "the right 
data"(tm) would be there (why verify input, right?), and then just 
flash it to NVRAM.


I'm aware your problem may be related to a different phenomenon. Just 
meaning to say: Lenovo (and probably other large vendors as well) 
released BIOS updates during 2014 to fix some rather nasty Intel Rapid 
Start issues, so in case your machine is of sufficient age, you might 
like to look into this.



Hope it helps ...

  Christoph

--
 open...@aixplosive.net

Re: Openbsd broke my hard drive twice! Getting frustrated

[Andrew Gwozdziewycz]

Hi Gabe,

I found it possible to boot and install 5.9 on an XPS 13" (9333)[0], but
had problems getting the all important suspend to RAM (or anything which
allowed me to close the lid and reopen to resume work) to work. Were you
successful in getting this necessary laptop functionality working correctly?

If so, would you mind sharing your configs? I'd love to reinstall OpenBSD
on this machine, but can't sacrifice that.

Cheers,

Andrew

[0]: To be fair, I suffered the same problems you did, where I thought the
drive was dead. But, in reality, I just had to repartition it with EFI in
mind from a thumb drive booted Linux installer, and try again.

On Tue, May 3, 2016 at 8:30 PM, Gabriel Guzman 
wrote:

> On 12/29, Gabriel Guzman wrote:
> > I've been seeing a similar issue on a DELL XPS 13" Developer edition I
> got
> > back in June -- ran fine with ubuntu as shipped with Dell, and then I
> > wiped and installed OpenBSD and now can't even access the BIOS.
>
> I figured out the issue.  On my machine (DEL XPS 13) it was the "Intel
> Rapid Boot" option in BIOS.  Disabling that resolved all my boot issues.
> I can now boot with MBR or GPT off the internal SSD.  And, I can also
> access the BIOS with the internal SSD installed in the system (this was
> not possible before)
>
> gabe.
>
>


-- 
http://apgwoz.com

Re: Openbsd broke my hard drive twice! Getting frustrated

[Gabriel Guzman]

On 12/29, Gabriel Guzman wrote:
> I've been seeing a similar issue on a DELL XPS 13" Developer edition I got
> back in June -- ran fine with ubuntu as shipped with Dell, and then I 
> wiped and installed OpenBSD and now can't even access the BIOS.  

I figured out the issue.  On my machine (DEL XPS 13) it was the "Intel
Rapid Boot" option in BIOS.  Disabling that resolved all my boot issues.
I can now boot with MBR or GPT off the internal SSD.  And, I can also
access the BIOS with the internal SSD installed in the system (this was
not possible before)

gabe. 

Re: Openbsd broke my hard drive twice! Getting frustrated

[Mihai Popescu]

 Openbsd broke my hard drive twice!

No, you have failed twice getting a proper hardware.

 Getting frustrated

Go talk to a specialist, OpenBSD cannot help you with this.

Will this thread with a really stupid name continue for much longer?
It looks very much like a troll's job.

Thanks.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Dmitrij D. Czarkoff]

Daniel Dickman said:
 The firmware on my laptop reads all the partitions in the MBR except
 ones marked as type EE (EFI). It then seems to try to read into those
 partitions for something else. If there is even 1 OpenBSD partition,
 it chokes on something in it. No idea why the firmware is reading past
 the MBR and into the actual disk partitions, seems strange.

Firmware may be trying to verify integrity of ntldr just like UEFI
firmware would.  Makes sense as security feature in PR department's
view.

-- 
Dmitrij D. Czarkoff

Re: Openbsd broke my hard drive twice! Getting frustrated

[Daniel Dickman]

On Thu, Feb 5, 2015 at 3:22 AM, Daniel Dickman didick...@gmail.com wrote:


 On Monday, December 22, 2014, Ted Unangst t...@tedunangst.com wrote:

 On Tue, Dec 23, 2014 at 00:53, Henrique Lengler wrote:
  On 2014-12-23 00:50, Edgar Pettijohn III wrote:
  Have you tried installing something other than OpenBSD since you ran
  into this issue?
 
  Since I ran into this issue I can't even access my bios with the HDD
  sata connected.

 That can only be a problem with your BIOS. Update it? Get a better
 one? I don't know. But if your BIOS doesn't work with some drive
 attached, your BIOS is broken.


 I just bought a system with what seems like the same problem as in this
 thread (dell laptop). I upgraded the drive to an ssd. the laptop firmware
 and the ssd firmware were both upgraded to the latest versions.

 with windows installed I can press F2 and get into the firmware menu just
 fine. with openbsd I just get a black screen when I press F2 at boot.

 I did a test. after i installed openbsd, I overwrote the mbr with all
 zeroes. when I rebooted I could access the bios menu via F2 again.

 does seem like a firmware bug based on the contents of the mbr. will see if
 I can diagnose further.

After some more digging. It's not the MBR itself that's the problem.

The firmware on my laptop reads all the partitions in the MBR except
ones marked as type EE (EFI). It then seems to try to read into those
partitions for something else. If there is even 1 OpenBSD partition,
it chokes on something in it. No idea why the firmware is reading past
the MBR and into the actual disk partitions, seems strange.

Dunno if this helps anyone else with a similar problem, but at least
for my system I know for sure it's a firmware bug.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Christopher Barry]

On Sun, 8 Feb 2015 00:21:27 -0500
Daniel Dickman didick...@gmail.com wrote:

On Thu, Feb 5, 2015 at 3:22 AM, Daniel Dickman didick...@gmail.com
wrote:


 On Monday, December 22, 2014, Ted Unangst t...@tedunangst.com
 wrote:

 On Tue, Dec 23, 2014 at 00:53, Henrique Lengler wrote:
  On 2014-12-23 00:50, Edgar Pettijohn III wrote:
  Have you tried installing something other than OpenBSD since you
  ran into this issue?
 
  Since I ran into this issue I can't even access my bios with the
  HDD sata connected.

 That can only be a problem with your BIOS. Update it? Get a better
 one? I don't know. But if your BIOS doesn't work with some drive
 attached, your BIOS is broken.


 I just bought a system with what seems like the same problem as in
 this thread (dell laptop). I upgraded the drive to an ssd. the
 laptop firmware and the ssd firmware were both upgraded to the
 latest versions.

 with windows installed I can press F2 and get into the firmware menu
 just fine. with openbsd I just get a black screen when I press F2 at
 boot.

 I did a test. after i installed openbsd, I overwrote the mbr with all
 zeroes. when I rebooted I could access the bios menu via F2 again.

 does seem like a firmware bug based on the contents of the mbr. will
 see if I can diagnose further.

After some more digging. It's not the MBR itself that's the problem.

The firmware on my laptop reads all the partitions in the MBR except
ones marked as type EE (EFI). It then seems to try to read into those
partitions for something else. If there is even 1 OpenBSD partition,
it chokes on something in it. No idea why the firmware is reading past
the MBR and into the actual disk partitions, seems strange.

Dunno if this helps anyone else with a similar problem, but at least
for my system I know for sure it's a firmware bug.


I have no clue here, but I'm interested about this. Is it possible the
BIOS is trying to identify the filesystem type, so it's save bios to
harddrive, or restore from harddrive, or other functionality that may
require disk access can work? they likely never tested on *bsd, so
the borken error path never got taken before? just throwing that out
there as it came to mind as a possibility. assumptions happen(TM)


--
Regards,
Christopher Barry

Random geeky fortune:
Protect from light.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Daniel Dickman]

On Monday, December 22, 2014, Ted Unangst t...@tedunangst.com wrote:

 On Tue, Dec 23, 2014 at 00:53, Henrique Lengler wrote:
  On 2014-12-23 00:50, Edgar Pettijohn III wrote:
  Have you tried installing something other than OpenBSD since you ran
  into this issue?
 
  Since I ran into this issue I can't even access my bios with the HDD
  sata connected.

 That can only be a problem with your BIOS. Update it? Get a better
 one? I don't know. But if your BIOS doesn't work with some drive
 attached, your BIOS is broken.


I just bought a system with what seems like the same problem as in this
thread (dell laptop). I upgraded the drive to an ssd. the laptop firmware
and the ssd firmware were both upgraded to the latest versions.

with windows installed I can press F2 and get into the firmware menu just
fine. with openbsd I just get a black screen when I press F2 at boot.

I did a test. after i installed openbsd, I overwrote the mbr with all
zeroes. when I rebooted I could access the bios menu via F2 again.

does seem like a firmware bug based on the contents of the mbr. will see if
I can diagnose further.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Gene]

On Thu, Feb 5, 2015 at 12:22 AM, Daniel Dickman didick...@gmail.com wrote:

 On Monday, December 22, 2014, Ted Unangst t...@tedunangst.com wrote:

  On Tue, Dec 23, 2014 at 00:53, Henrique Lengler wrote:
   On 2014-12-23 00:50, Edgar Pettijohn III wrote:
   Have you tried installing something other than OpenBSD since you ran
   into this issue?
  
   Since I ran into this issue I can't even access my bios with the HDD
   sata connected.
 
  That can only be a problem with your BIOS. Update it? Get a better
  one? I don't know. But if your BIOS doesn't work with some drive
  attached, your BIOS is broken.


 I just bought a system with what seems like the same problem as in this
 thread (dell laptop). I upgraded the drive to an ssd. the laptop firmware
 and the ssd firmware were both upgraded to the latest versions.

 with windows installed I can press F2 and get into the firmware menu just
 fine. with openbsd I just get a black screen when I press F2 at boot.

 I did a test. after i installed openbsd, I overwrote the mbr with all
 zeroes. when I rebooted I could access the bios menu via F2 again.

 does seem like a firmware bug based on the contents of the mbr. will see if
 I can diagnose further.


It's not a bug.  It's a security feature...

-Gene

Re: Openbsd broke my hard drive twice! Getting frustrated

[Nick Holland]

On 02/05/15 03:26, Gene wrote:
 On Thu, Feb 5, 2015 at 12:22 AM, Daniel Dickman didick...@gmail.com wrote:
 
...
 does seem like a firmware bug based on the contents of the mbr. will see if
 I can diagnose further.

 
 It's not a bug.  It's a security feature...

or maybe
very effective exploit mitigation technique countermeasure

but yes...if something written on the MBR causes the system to lock
hard, that's a BIOS problem, plain and simple...and if no update is
available, it should be considered defective hardware.  It would be one
thing if the MBR code were being RUN (i.e., part of the boot process)
and hanging (we had this problem long, long ago), but the problem being
described is the BIOS is just looking at the disk's MBR BEFORE TRYING TO
BOOT and freaking out in such a way that it couldn't be fixed without
using another computer to alter the MBR..sounds like a potential DoS
attack vector.  Imagine a disgruntled employee dropping this or similar
code on a bunch of servers on his way out the door and the fun that
would happen on the next patch day.  Sure, someone could simply zero the
MBR and prevent systems from rebooting, but any remote management
solution could fix that.  If you can WEDGE the BIOS, that would require
physical dissassembly of the computer to fix the problem.

Now...if someone figures out a trivial change to the boot code that
fixes this without potentially breaking some other system, maybe it
would be considered for commit, but I think this still qualifies as a
serious hardware defect that manufacturers need to be aware of and fix.

(Using an old DOS boot disk to do an FDISK /MBR will probably render
these machines bootable, but I'd still consider the machine broken.)

Nick.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Maurice McCarthy]

On 2014-12-30 16:38, Mark - Syminet wrote:
On Dec 29, 2014, at 5:02 PM, Eric Furman ericfur...@fastmail.net 
wrote:



Linux supports the UEFI boot loader. OpenBSD does not.


...and that is all we need to know.

Shame on them!  Shame Shame Shame!


Maybe my knowledge is outdated but you've got things wrong here. UEFI 
boot code is binary only and owned by Microsoft. This was decided by 
whatever board controls the standard. (Standard ?!) To my knowledge, 
though it is dated, only Red Hat and Ubuntu have a license from 
Microsoft and therefore have created the necessary 'shim code,' as it is 
called, to interface with UEFI.


Regards
Moss

Re: Openbsd broke my hard drive twice! Getting frustrated

[Jason Adams]

On 01/01/2015 02:43 AM, Maurice McCarthy wrote:
 On 2014-12-30 16:38, Mark - Syminet wrote:
 On Dec 29, 2014, at 5:02 PM, Eric Furman ericfur...@fastmail.net wrote:

 Linux supports the UEFI boot loader. OpenBSD does not.

 ...and that is all we need to know.

 Shame on them!  Shame Shame Shame!

 Maybe my knowledge is outdated but you've got things wrong here. UEFI boot 
 code is binary only and
 owned by Microsoft. This was decided by whatever board controls the standard. 
 (Standard ?!) To my
 knowledge, though it is dated, only Red Hat and Ubuntu have a license from 
 Microsoft and therefore
 have created the necessary 'shim code,' as it is called, to interface with 
 UEFI.

 Regards
 Moss


Opensuse as well, as of about 3 releases ago.
I don't know if an actual license is involved, but you do have to get microsoft 
to sign some
piece of code, which costs 99 bucks per trial (apparently it used to takes a 
few tries to get
it right).  The association of Microsoft and hardware manufacturers have been 
looking for
other signing authorities but no one has stepped up yet.

http://www.linuxjournal.com/content/growing-role-uefi-secure-boot-linux-distributions

-- 
Those who do not understand Unix are condemned to reinvent it, poorly.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Mark - Syminet]

On Dec 29, 2014, at 5:02 PM, Eric Furman ericfur...@fastmail.net wrote:

 Linux supports the UEFI boot loader. OpenBSD does not.

...and that is all we need to know.  

Shame on them!  Shame Shame Shame!  

-- 
Mark 

[demime 1.01d removed an attachment of type application/pgp-signature which had 
a name of signature.asc]

Re: [probably solved] Re: Openbsd broke my hard drive twice! Getting frustrated

[Calvin]

I had a machine that didn't like OpenBSD either, it froze during POST or Plop, 
basically when BIOS services were still usable. It was a BIOS-based system 
though, and I didn't patch it either. Luckily, I installed on an external disk.

-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of 
Henrique Lengler
Sent: December 23, 2014 12:56 PM
To: misc@openbsd.org
Subject: [probably solved] Re: Openbsd broke my hard drive twice! Getting 
frustrated

I figured that my BIOS have a old firmware from 2013. So I decided to update it.
At least this my motherboard did good, I easily updated the firmware by 
plugging a USB with the new firmware.
Then It rebooted and yes, it worked as it should. Booted normally with the HDD 
sata connected. I cannot get satisfied yet, I will install a OS and see if it 
will still
  working.
I'm in doubt about try openBSD again, I'm afraid everything could happen again.

Also is there a explanation to this shitty behavior? My motherboard acted like 
having a short circuit, making everything stop working because a bad formatted 
HDD, this is a really unexpected behavior, which made me think the problem was 
openBSD.

By now, thanks for helping.
I expect don't need to post anything more here.

Regards,
--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Gabriel Guzman]

I've been seeing a similar issue on a DELL XPS 13 Developer edition I got
back in June -- ran fine with ubuntu as shipped with Dell, and then I 
wiped and installed OpenBSD and now can't even access the BIOS.  

I'm *sure* it's a BIOS issue as the BIOS is probably trying to do 
something silly with the hardisk.  Haven't gotten around to flashing the 
BIOS to a newer version as I'm fairly sure
I'll need to remove the harddisk before the system will even let me
boot (and that involves taking apart most of the laptop).  It's sad that 
BIOSes are so buggy these days, and a bit crazy that something you do to 
the disk would cause the BIOS to freak out.  Oh well, whenever the Dell 
support people pick up the phone, I'll complain to them for all the good 
it will do. 

The Dell had no problem booting the install media from usb, was just
when it came time to try and boot from HD that the BIOS freaked, and now
won't allow me to access the BIOS settings or the choose which media to
boot from menu.

To the OP -- This is definitely not OpenBSD breaking your system, it's
OpenBSD doing one of the things it does best... exposing bugs in *other*
places (: and I feel your pain, it's quite frustrating when hardware
we've paid for can't handle something that should be easy.

gabe. 

Re: Openbsd broke my hard drive twice! Getting frustrated

[Wade, Daniel]

 -Original Message-
 From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On
 Behalf Of Gabriel Guzman
 Sent: Monday, December 29, 2014 9:49 AM
 To: misc@openbsd.org
 Subject: Re: Openbsd broke my hard drive twice! Getting frustrated
 
 I've been seeing a similar issue on a DELL XPS 13 Developer edition I got
 back in June -- ran fine with ubuntu as shipped with Dell, and then I
 wiped and installed OpenBSD and now can't even access the BIOS.
 
 I'm *sure* it's a BIOS issue as the BIOS is probably trying to do
 something silly with the hardisk.  Haven't gotten around to flashing the
 BIOS to a newer version as I'm fairly sure
 I'll need to remove the harddisk before the system will even let me
 boot (and that involves taking apart most of the laptop).  It's sad that
 BIOSes are so buggy these days, and a bit crazy that something you do to
 the disk would cause the BIOS to freak out.  Oh well, whenever the Dell
 support people pick up the phone, I'll complain to them for all the good
 it will do.
 
 The Dell had no problem booting the install media from usb, was just
 when it came time to try and boot from HD that the BIOS freaked, and now
 won't allow me to access the BIOS settings or the choose which media to
 boot from menu.
 
 To the OP -- This is definitely not OpenBSD breaking your system, it's
 OpenBSD doing one of the things it does best... exposing bugs in *other*
 places (: and I feel your pain, it's quite frustrating when hardware
 we've paid for can't handle something that should be easy.
 
 gabe.


I've got a Dell latitude E5440 that exhibits the same problem.  But only with 
certain hard drives. I have some that work just fine and then some that will 
freeze the BIOS. I would recommend trying a different drive

Re: Openbsd broke my hard drive twice! Getting frustrated

[VaZub]

Got exactly the same issue with my Acer Aspire v5-573G several months ago.
Drove me crazy like hell. Nice to know that I wasn't the only one facing
this problem. Updating Acer BIOS didn't help, I had to remove HDD from
SATA-connected slot altogether to be able to boot past BIOS check.
Interesting observation, though - USB-booting worked without a hitch, both
from a flash drive and from the same HDD connected externally through
SATA-to-USB converter. I hope this helps with further investigation.

On Mon, Dec 29, 2014 at 5:57 PM, Wade, Daniel dw...@meridium.com wrote:

  -Original Message-
  From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On
  Behalf Of Gabriel Guzman
  Sent: Monday, December 29, 2014 9:49 AM
  To: misc@openbsd.org
  Subject: Re: Openbsd broke my hard drive twice! Getting frustrated
 
  I've been seeing a similar issue on a DELL XPS 13 Developer edition I
 got
  back in June -- ran fine with ubuntu as shipped with Dell, and then I
  wiped and installed OpenBSD and now can't even access the BIOS.
 
  I'm *sure* it's a BIOS issue as the BIOS is probably trying to do
  something silly with the hardisk.  Haven't gotten around to flashing the
  BIOS to a newer version as I'm fairly sure
  I'll need to remove the harddisk before the system will even let me
  boot (and that involves taking apart most of the laptop).  It's sad that
  BIOSes are so buggy these days, and a bit crazy that something you do to
  the disk would cause the BIOS to freak out.  Oh well, whenever the Dell
  support people pick up the phone, I'll complain to them for all the good
  it will do.
 
  The Dell had no problem booting the install media from usb, was just
  when it came time to try and boot from HD that the BIOS freaked, and now
  won't allow me to access the BIOS settings or the choose which media to
  boot from menu.
 
  To the OP -- This is definitely not OpenBSD breaking your system, it's
  OpenBSD doing one of the things it does best... exposing bugs in *other*
  places (: and I feel your pain, it's quite frustrating when hardware
  we've paid for can't handle something that should be easy.
 
  gabe.


 I've got a Dell latitude E5440 that exhibits the same problem.  But only
 with certain hard drives. I have some that work just fine and then some
 that will freeze the BIOS. I would recommend trying a different drive

Re: Openbsd broke my hard drive twice! Getting frustrated

[Eric Furman]

Linux supports the UEFI boot loader. OpenBSD does not.
Before installing OpenBSD you need to enter its setup and enable legacy
support.
You don't need to do that with Linux.
https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface

On Mon, Dec 29, 2014, at 09:49 AM, Gabriel Guzman wrote:
 I've been seeing a similar issue on a DELL XPS 13 Developer edition I
 got
 back in June -- ran fine with ubuntu as shipped with Dell, and then I 
 wiped and installed OpenBSD and now can't even access the BIOS.  
 
 I'm *sure* it's a BIOS issue as the BIOS is probably trying to do 
 something silly with the hardisk.  Haven't gotten around to flashing the 
 BIOS to a newer version as I'm fairly sure
 I'll need to remove the harddisk before the system will even let me
 boot (and that involves taking apart most of the laptop).  It's sad that 
 BIOSes are so buggy these days, and a bit crazy that something you do to 
 the disk would cause the BIOS to freak out.  Oh well, whenever the Dell 
 support people pick up the phone, I'll complain to them for all the good 
 it will do. 
 
 The Dell had no problem booting the install media from usb, was just
 when it came time to try and boot from HD that the BIOS freaked, and now
 won't allow me to access the BIOS settings or the choose which media to
 boot from menu.
 
 To the OP -- This is definitely not OpenBSD breaking your system, it's
 OpenBSD doing one of the things it does best... exposing bugs in *other*
 places (: and I feel your pain, it's quite frustrating when hardware
 we've paid for can't handle something that should be easy.
 
 gabe. 

Re: Openbsd broke my hard drive twice! Getting frustrated

[Gregory Edigarov]

On 12/23/2014 04:04 AM, Henrique Lengler wrote:
 Hi,
 
  I decided to install openbsd by the first time a month ago, How I was
  with no internet connection I needed to shutdown the computer in the
  part that I need to download the packages, because I hadn't it on the
  cd. I could not acess the command line so I clicked the reset button
  on the front panel. When I tried to turn on again, the system didn't
  boot. I discovered that it only worked if I remove the hard drive.
  Thinking that the problem was the harddrive I sent it to warranty to
  be repleaced. I took 10 long days (withou my computer) to arrive a
  new one. When it arrived, I tested and I saw that now it is working.
  I prepared a cable connection, and I started again the openbsd
  setup. It sucefully downloaded and installed everything, so I
  rebooted the system to boot my new fresh install. AND SHIT,
  everything happened as before, the system don't boot as before, I
  can't open the bios as before, and I got really mad.
 
  I don't know if I will be able to sent it to warranty again, but this
  isn't the right thing to do now that I discovered that the problem
  isn't with it, the problem is with Openbsd.
 
  Could someone please explain me why this happened? Can you think
  about a way to fix this without send it to warranty? Any other
  questions? send me a reply, I'm really in need of help
 
Hi,

I can remember similar problems when I first tried to install OpenBSD on 
my current computer.
The problem were performance settings in BIOS, that were somehow set to 
high performance profile.
After setting that to Standard Profile - things went smoothly.

--
With best regards,
Gregory Edigarov

Re: Openbsd broke my hard drive twice! Getting frustrated

[L.R. d S.]

The BIOS have nothing to do with the OS, it's other coding layer, and the OS 
can't disable the HDD since it have their own firmware on microcontroller.
I would suggest: if you can boot from CD like you say, you can:
- Flash the BIOS. See your board and download from oficial site;
- Reboot and make a low-level dump of your HDD (you can use diskdump for this);
- Set your BIOS to standard config's, but legacy boot and the SATA port that 
your HDD where;
- Download the image of 5.6 from Calgary mirror (don't download from US 
mirrors);
- Try install.

If you can't, so: your HDD are broken or your hardware (maybe motherboard) are 
broken.

Greeting,
Luiz.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Peter N. M. Hansteen]

Henrique Lengler henriquel...@openmailbox.org writes:

 I decided to install openbsd by the first time a month ago, How I
 was with no internet connection I needed to shutdown the computer in
 the part that I need to download the packages, because I hadn't it
 on the cd. I could not acess the command line so I clicked the reset
 button on the front panel. When I tried to turn on again, the system
 didn't boot. I discovered that it only worked if I remove the hard
 drive.  Thinking that the problem was the harddrive I sent it to
 warranty to be repleaced. I took 10 long days (withou my computer)
 to arrive a new one.  When it arrived, I tested and I saw that now
 it is working. I prepared a cable connection, and I started again
 the openbsd setup.  It sucefully downloaded and installed
 everything, so I rebooted the system to boot my new fresh install.
 AND SHIT, everything happened as before, the system don't boot as
 before, I can't open the bios as before, and I got really mad.

Did you in fact complete the install at all, or did you just partition
the disk and press reset before installing any sets?

While you're on an internet connected computer, please look up the
installation parts of the FAQ http://www.openbsd.org/faq/faq4.html and
see if you can't find the part where things started going wrong. I
strongly suspect that you did not in fact complete the install.

That said, since you're revealing next to no information about the
system you are trying to install on, I'll offer this by way of
historical anecdotes from times better forgotten: I've seen systems
that were Windows-specific to the point that large chunks of the
system setup software including a point'n'click interface to BIOS were
stored in a special partition on the system's hard disk. Destroying
that partition (such as choosing to use the whole disk for OpenBSD
while running the OpenBSD installer) could lead to odd behavior on
some machines, while on others you would be stuck with whatever
settings the system had before you wiped the magic partition.

The latter included some late-noughties cheapo-thinkpads such as my
now retired SL500 
(http://bsdly.blogspot.no/2010/01/goodness-of-men-and-machinery.html,
which also offers a rough idea of how an OpenBSD install proceeds).
Pressing the big blue button on that laptop after installing OpenBSD lead
to exactly zero results, but the machine ran OpenBSD fine as its only
operating system and so I did not waste too much energy on what the blue
button might have given me.

It's possible (but not very likely) you are the victim of something
like this, but I strongly suspect that you simply pressed the reset
button after partitioning the disk but before installing an operating
system.  Pressing the reset button insistently at the wrong moment can
even leave you with a hard disk without valid partitioning, which
means that the system is in a state that does not let it boot easily.

But once again, your best option right now is to look up the install
part of the FAQ, get hold of a valid install medium that include the
install sets (both CD images and USB thumbdrive images are available)
and go from there.

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 04:06, Brent Cook wrote:

There have been a couple of reports similar to this one that were fixed
with a firmware update from the motherboard or system vendor. I would
presume the firmware basically crashes if it sees a boot code written
on the hard drive it does not expect, even if it follows the
standards:

http://marc.info/?t=13988430601r=1w=2

http://marc.info/?l=openbsd-miscw=2r=1s=Axiomtek+NA570q=b

I worked on a new-ish laptop recently that would not boot from a CD or
any non-Windows partition unless I first removed the hard drive,
entered the EFI/Bios setup, set a password, then disabled EFI secure
boot.


Good, you're giving me hope. Good links, I will try this.

Also found a very similar with a similar motherboard, but have no 
answer.


Regards,
--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 04:27, Dmitrij D. Czarkoff wrote:

Unlikely until you mention the model of your laptop and describe the
problem in more detail.


Ok, it is not a laptop. It have a ASUS Z87-k motherboard, 8GB CRUCIAL 
RAM, Intel Core i7 4770k processor.

My HDD is a Seagate Barracuda 1TB.

Regards

--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 10:33, pe...@bsdly.net wrote:

Did you in fact complete the install at all, or did you just partition
the disk and press reset before installing any sets?


As I said, everything I can expect from a bad uncompleted install is the 
system trying

to load the HDD and it fails.
But what really happen is that if I tur on the computer with the HDD 
connected, all other
hardware stop working. Even the keyboard lights stop blinking when 
clicking

Caps/Num Lock.

--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Robert Blacquiere]

Hi,

On Tue, Dec 23, 2014 at 12:04:25AM -0200, Henrique Lengler wrote:
 Hi,
 
 I decided to install openbsd by the first time a month ago, How I
 was with no internet
 connection I needed to shutdown the computer in the part that I need
 to download the packages,
 because I hadn't it on the cd. I could not acess the command line so
 I clicked the reset button
 on the front panel. When I tried to turn on again, the system didn't
 boot. I discovered that it
 only worked if I remove the hard drive.
 Thinking that the problem was the harddrive I sent it to warranty to
 be repleaced. I took
 10 long days (withou my computer) to arrive a new one.
 When it arrived, I tested and I saw that now it is working. I
 prepared a cable connection, and I
 started again the openbsd setup.
 It sucefully downloaded and installed everything, so I rebooted the
 system to boot my new fresh install.
 AND SHIT, everything happened as before, the system don't boot as
 before, I can't open the bios as before, and
  I got really mad.
 
 I don't know if I will be able to sent it to warranty again, but
 this isn't the right thing to do now that
  I discovered that the problem isn't with it, the problem is with
 Openbsd.
 
 Could someone please explain me why this happened? Can you think
 about a way to fix this without send it to warranty?
 Any other questions? send me a reply, I'm really in need of help
 
 -- 
 Henrique Lengler
 

Please send us the model, brand etc of your pc. This would be helpful
for everyone. 

Also my own experience with EFI and secureboot systems show unable to
detect a openbsd installation. Only when bios is set to CSM or CSM an
UEFI OS (Samsung AtivPro type) it will see a bootable OpenBSD disk. 

Please send us this type of information. Without it it would be guesing
1000's possible issues.

Regards

Re: Openbsd broke my hard drive twice! Getting frustrated

[Peter N. M. Hansteen]

Henrique Lengler henriquel...@openmailbox.org writes:

 Ok, it is not a laptop. It have a ASUS Z87-k motherboard, 8GB CRUCIAL
 RAM, Intel Core i7 4770k processor.

http://www.asus.com/Motherboards/Z87K/HelpDesk_Download/ appears to be
the source of BIOS updates and utilities, and do poke around the FAQ
section too.

- P
-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Sonic]

On Tue, Dec 23, 2014 at 10:48 AM, Henrique Lengler
henriquel...@openmailbox.org wrote:
 As I said, everything I can expect from a bad uncompleted install is the
 system trying
 to load the HDD and it fails.

It's worth double checking but my guess is that you have the Secure
Boot feature in the BIOS set to Other OS (which is mandatory) as if
was set set to Windows UEFI Mode it would be odd that you could boot
the OpenBSD install media.

Another thing to check is the BIOS version. If you're not at version
1401 (released 2014.09.12) it would behoove you to do so. After the
update load the defaults then after a reboot go back in and set
Secure Boot to Other OS.

Chris

Re: Openbsd broke my hard drive twice! Getting frustrated

[Peter N. M. Hansteen]

Henrique Lengler henriquel...@openmailbox.org writes:

 On 2014-12-23 10:33, pe...@bsdly.net wrote:
  Did you in fact complete the install at all, or did you just partition
  the disk and press reset before installing any sets?
 
 As I said, everything I can expect from a bad uncompleted install is
 the system trying to load the HDD and it fails.  

Your expectations are irrelevant. How far your botched installation
proceeded before you pushed the reset button is.

There are several ways to break setups by misusing powerful tools. And
of course there is a very real possibility that hardware or firmware
bugs are what's tripping you up.

How far did you install proceed before you pushed the reset button?

Have you tried attaching the disk to a different machine?

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Sonic]

On Tue, Dec 23, 2014 at 11:02 AM, Sonic sonicsm...@gmail.com wrote:
 Another thing to check is the BIOS version. If you're not at version
 1401 (released 2014.09.12) it would behoove you to do so. After the
 update load the defaults then after a reboot go back in and set
 Secure Boot to Other OS.

Note on the Asus site (in the BIOS-Utilities section) that you need
to use the BIOS updater for New 4th Gen Intel Core Processors before
updating the BIOS:

Before using the new Intel 4th Gen Core processors, we suggest that
you first download the BIOS updater for new Intel 4th Gen Core
Processors and then update the BIOS using this tool.

Chris

Re: Openbsd broke my hard drive twice! Getting frustrated

[Sonic]

On Tue, Dec 23, 2014 at 11:05 AM, Peter N. M. Hansteen pe...@bsdly.net wrote:
 How far did you install proceed before you pushed the reset button?

In general pushing the reset button is a very bad idea. If you're
really stuck holding in the power button is a better option just in
case the system is in a state where an ACPI shutdown can occur.

Chris

Re: Openbsd broke my hard drive twice! Getting frustrated

[Sonic]

On Tue, Dec 23, 2014 at 11:02 AM, Sonic sonicsm...@gmail.com wrote:
 It's worth double checking but my guess is that you have the Secure
 Boot feature in the BIOS set to Other OS (which is mandatory) as if
 was set set to Windows UEFI Mode it would be odd that you could boot
 the OpenBSD install media.

Note some other BIOS settings you may want to examine:

Boot Devices Control [UEFI and Legacy OpROM]

Allows you to select the type of devices that you want to boot up.
Configuration options:
[UEFI and Legacy OpROM] [Legacy OpROM only] [UEFI only]


Boot from Storage Devices [Legacy OpROM first]

Allows you to select the type of storage devices that you want to
launch. Configuration
options: [Both, Legacy OpROM first] [Both, UEFI first] [Legacy OpROM
first] [UEFI driver first]
[Ignore]


Probably best to set both of those to [Legacy OpROM first].

At any rate a properly updated BIOS and a reading of the latest
version of the user manual (most likely not the one that came printed
with your board) should go a long way toward resolving the problem.

Chris

[probably solved] Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

I figured that my BIOS have a old firmware from 2013. So I decided to 
update it.
At least this my motherboard did good, I easily updated the firmware by 
plugging

a USB with the new firmware.
Then It rebooted and yes, it worked as it should. Booted normally with 
the HDD sata
connected. I cannot get satisfied yet, I will install a OS and see if it 
will still

 working.
I'm in doubt about try openBSD again, I'm afraid everything could happen 
again.


Also is there a explanation to this shitty behavior? My motherboard 
acted like having a
short circuit, making everything stop working because a bad formatted 
HDD, this is a

really unexpected behavior, which made me think the problem was openBSD.

By now, thanks for helping.
I expect don't need to post anything more here.

Regards,
--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Josh Grosse]

On 2014-12-23 10:48, Henrique Lengler wrote:

On 2014-12-23 10:33, pe...@bsdly.net wrote:

Did you in fact complete the install at all, or did you just partition
the disk and press reset before installing any sets?


As I said, everything I can expect from a bad uncompleted install is
the system trying
to load the HDD and it fails.
But what really happen is that if I tur on the computer with the HDD
connected, all other
hardware stop working. Even the keyboard lights stop blinking when 
clicking

Caps/Num Lock.


I am aware of one prior instance of a BIOS failing to complete POST 
after

installing a FreeBSD OS.

http://daemonforums.org/showthread.php?t=7238

Root cause was never isolated, but in hindsight I would guess EUFI.

Re: [probably solved] Re: Openbsd broke my hard drive twice! Getting frustrated

[John Merriam]

On Tue, 23 Dec 2014, Henrique Lengler wrote:

 I figured that my BIOS have a old firmware from 2013. So I decided to update
 it.
 At least this my motherboard did good, I easily updated the firmware by
 plugging
 a USB with the new firmware.
 Then It rebooted and yes, it worked as it should. Booted normally with the HDD
 sata
 connected. I cannot get satisfied yet, I will install a OS and see if it will
 still
  working.
 I'm in doubt about try openBSD again, I'm afraid everything could happen
 again.
 
 Also is there a explanation to this shitty behavior? My motherboard acted like
 having a
 short circuit, making everything stop working because a bad formatted HDD,
 this is a
 really unexpected behavior, which made me think the problem was openBSD.
 
 By now, thanks for helping.
 I expect don't need to post anything more here.
 
 Regards,
 -- 
 Henrique Lengler
 
 

I would guess that you hit a bug (or multiple bugs) in the BIOS.  Probably 
something related to UFEI.

I generally try to update the BIOS on my machines when I'm starting over 
from scratch with them.  When I recently changed my home server to OpenBSD 
I upgraded the motherboard BIOS before starting the process even though I 
was not experiencing any problems with the previous BIOS with Linux 
installed on the machine.

I don't have any UFEI machines except at work (thank goodness).  It 
doesn't surprise me that a UFEI BIOS would be buggy and produce behavior 
like that.

-- 

John Merriam

Re: [probably solved] Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 14:55, Henrique Lengler wrote:
I figured that my BIOS have a old firmware from 2013. So I decided to 
update it.
At least this my motherboard did good, I easily updated the firmware by 
plugging

a USB with the new firmware.
Then It rebooted and yes, it worked as it should. Booted normally with
the HDD sata
connected. I cannot get satisfied yet, I will install a OS and see if
it will still
 working.
I'm in doubt about try openBSD again, I'm afraid everything could 
happen again.


Also is there a explanation to this shitty behavior? My motherboard
acted like having a
short circuit, making everything stop working because a bad formatted
HDD, this is a
really unexpected behavior, which made me think the problem was 
openBSD.


By now, thanks for helping.
I expect don't need to post anything more here.

Regards,


UPDATE:

It also loaded OpenBSD from the harddrive, now I don't need to install 
it again. This evidence that I did install it right!


Regards,
--
Henrique Lengler

Re: [probably solved] Re: Openbsd broke my hard drive twice! Getting frustrated

[Peter N. M. Hansteen]

Henrique Lengler henriquel...@openmailbox.org writes:

 It also loaded OpenBSD from the harddrive, now I don't need to install
 it again. This evidence that I did install it right!

So likely it was a buggy BIOS then. 

Excellent to hear that you got the thing running, best of luck with the new 
system!

- Peter

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
Remember to set the evil bit on all malicious network traffic
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: Openbsd broke my hard drive twice! Getting frustrated

[OpenBSD lists]

On Tue, Dec 23, 2014 at 12:04:25AM -0200, Henrique Lengler wrote:
 Could someone please explain me why this happened? Can you think about a way
 to fix this without send it to warranty?
 Any other questions? send me a reply, I'm really in need of help

# cd /usr/src/distrib/miniroot/
# grep -B3 'inconsistent state' install.sub
At any prompt except password prompts you can escape to a shell by
typing '!'. Default answers are shown in []'s and are selected by
pressing RETURN.  You can exist this program at any time by pressing
Control-C, but this can leave your system in an inconsistent state.

Did you not see this warning while installing?

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 00:12, OpenBSD lists wrote:

# cd /usr/src/distrib/miniroot/
# grep -B3 'inconsistent state' install.sub
At any prompt except password prompts you can escape to a shell by
typing '!'. Default answers are shown in []'s and are selected by
pressing RETURN.  You can exist this program at any time by pressing
Control-C, but this can leave your system in an inconsistent state.

Did you not see this warning while installing?


What about my second attempt, in which I did everything normally and the
same problem happened?

--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Edgar Pettijohn III]

Have you tried installing something other than OpenBSD since you ran into this 
issue?

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 00:50, Edgar Pettijohn III wrote:

Have you tried installing something other than OpenBSD since you ran
into this issue?


Since I ran into this issue I can't even access my bios with the HDD 
sata connected.

--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 00:53, Edgar Pettijohn III wrote:

So if you stick in a disk with an iso from some other os it won't boot
from the cd without you accessing bios?


I didn't and I can't try this because I don't have any other HDD here.
But it can boot my CD/DVD reader with a cd containing Linux, wich is
connected via a SATA cable too.
I tried to change HDD the cable and the port, and anything solved.
--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Ted Unangst]

On Tue, Dec 23, 2014 at 00:53, Henrique Lengler wrote:
 On 2014-12-23 00:50, Edgar Pettijohn III wrote:
 Have you tried installing something other than OpenBSD since you ran
 into this issue?
 
 Since I ran into this issue I can't even access my bios with the HDD
 sata connected.

That can only be a problem with your BIOS. Update it? Get a better
one? I don't know. But if your BIOS doesn't work with some drive
attached, your BIOS is broken.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 01:02, Ted Unangst wrote:

That can only be a problem with your BIOS. Update it? Get a better
one? I don't know. But if your BIOS doesn't work with some drive
attached, your BIOS is broken.


How can you say this? The problem isn't my BIOS don't booting with a
broke HDD. I have evidences it work if I put a working drive.
My motherboard is very new and it every worked good in any type of 
system.

--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[martin]

Henrique Lengler henriquel...@openmailbox.org wrote:

 On 2014-12-23 00:50, Edgar Pettijohn III wrote:
  Have you tried installing something other than OpenBSD since you ran
  into this issue?
 
 Since I ran into this issue I can't even access my bios with the HDD 
 sata connected.
 -- 
 Henrique Lengler

It would be exceedingly odd for OpenBSD to be able to break that.

Has anything ever been installed successfully on this machine? Perhaps
the motherboard or power supply causes damage after extended use.

-- Martin

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 01:08, mar...@martinbrandenburg.com wrote:

Has anything ever been installed successfully on this machine? Perhaps
the motherboard or power supply causes damage after extended use.

-- Martin


Yes, my motherboard and power supply have 1 year of use, it every 
worked, and still
working good. The evidence is that after try to install OpenBSD by the 
second time, I did
a test, I reboot my system three times, accessed bios and everything 
worked.

--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 01:11, Henrique Lengler wrote:


Yes, my motherboard and power supply have 1 year of use, it every
worked, and still
working good. The evidence is that after try to install OpenBSD by the


I mean before
--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[martin]

Henrique Lengler henriquel...@openmailbox.org wrote:

 On 2014-12-23 01:08, mar...@martinbrandenburg.com wrote:
  Has anything ever been installed successfully on this machine? Perhaps
  the motherboard or power supply causes damage after extended use.
  
  -- Martin
 
 Yes, my motherboard and power supply have 1 year of use, it every 
 worked, and still
 working good. The evidence is that after try to install OpenBSD by the 
 second time, I did
 a test, I reboot my system three times, accessed bios and everything 
 worked.
 -- 
 Henrique Lengler

Does the disk that you claim OpenBSD damaged still work in a different
computer?

I was being nice when I said exceedingly odd. It's more like impossible.
You come here with an impossible problem and no information. You haven't
even said what type of computer this is. I realize a dmesg is impossible
when it won't boot (though you could unplug the offending disk and get a
dmesg from the CD), but some information would be nice.

-- Martin

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 01:18, mar...@martinbrandenburg.com wrote:

Does the disk that you claim OpenBSD damaged still work in a different
computer?


Will be difficult to me can do this, I don't have any other desktop in 
my house.

I will see if I can do this later.

I was being nice when I said exceedingly odd. It's more like 
impossible.
You come here with an impossible problem and no information. You 
haven't
even said what type of computer this is. I realize a dmesg is 
impossible
when it won't boot (though you could unplug the offending disk and get 
a

dmesg from the CD), but some information would be nice.


Isn't the operating system responsible to recognize and use with a 
correct

driver my HDD?
Linux is like this, the kernel have the SATA driver wich handle the 
drivers.


Regards,
--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Jonathon Sisson]

On Tue, Dec 23, 2014 at 12:42:25AM -0200, Henrique Lengler wrote:
 On 2014-12-23 00:12, OpenBSD lists wrote:
 # cd /usr/src/distrib/miniroot/
 # grep -B3 'inconsistent state' install.sub
 At any prompt except password prompts you can escape to a shell by
 typing '!'. Default answers are shown in []'s and are selected by
 pressing RETURN.  You can exist this program at any time by pressing
 Control-C, but this can leave your system in an inconsistent state.
 
 Did you not see this warning while installing?
 
 What about my second attempt in which I did everything normally?
 -- 
 Henrique Lengler

Here's a silly question...is it an EFI system?  I would think
the installer wouldn't boot properly if so, but you may have
to go into your BIOS and set it up for legacy boot?

I don't know.  I've never heard of an OS install causing
physical damage to a machine (though a few FreeBSD installs
I performed around the 6.X/7.X timeframe caused *me* to harm
a computer =).

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 02:00, Jonathon Sisson wrote:


Here's a silly question...is it an EFI system?  I would think
the installer wouldn't boot properly if so, but you may have
to go into your BIOS and set it up for legacy boot?

Yes, it's a EFI system.
How this would help if it can't even recognize the disk.
Just in case, I already used Linux with a totally BIOS setup and it 
worked.



I don't know.  I've never heard of an OS install causing
physical damage to a machine (though a few FreeBSD installs
I performed around the 6.X/7.X timeframe caused *me* to harm
a computer =).


I'm also surprised with this, but I'm almost sure that it happened.
I think we should study this and find the real problem cause.

Regards,
--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Eric Furman]

On Mon, Dec 22, 2014, at 10:23 PM, Henrique Lengler wrote:
 On 2014-12-23 01:18, mar...@martinbrandenburg.com wrote:
  Does the disk that you claim OpenBSD damaged still work in a different
  computer?
 
 Will be difficult to me can do this, I don't have any other desktop in 
 my house.
 I will see if I can do this later.
 
  I was being nice when I said exceedingly odd. It's more like 
  impossible.
  You come here with an impossible problem and no information. You 
  haven't
  even said what type of computer this is. I realize a dmesg is 
  impossible
  when it won't boot (though you could unplug the offending disk and get 
  a
  dmesg from the CD), but some information would be nice.
 
 Isn't the operating system responsible to recognize and use with a 
 correct
 driver my HDD?
 Linux is like this, the kernel have the SATA driver wich handle the 
 drivers.

No. This is done by the BIOS.
After the computer boots the BIOS then hands over control to the OS.
And yes, that is a gross over simplification of what actually happens.
There is no way that any OS can 'break' a hard drive.
And since your computer is fairly new it probably uses UEFI.
You might try to go into your BIOS settings and try a 'Legacy' boot
option.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Joel Rees]

Ouch.

On Tue, Dec 23, 2014 at 11:04 AM, Henrique Lengler
henriquel...@openmailbox.org wrote:
 Hi,

 I decided to install openbsd by the first time a month ago, How I was with
 no internet
 connection

I guess you mean, no other way to access the internet.

By the way, how are you accessing the internet now?

 I needed to shutdown the computer

Don't do that. It hurts. I promise. Avoid it if at all possible by
planning ahead.

 in the part that I need to
 download the packages,

Yeah. This is where you need to plan ahead.

 because I hadn't it on the cd.

So, you downloaded the wrong CD image. Perhaps it was cd56.iso?

Getting the right CD is part of planning ahead.

Or perhaps you forgot to write down the URL for a nearby mirror before
you started, so you could tell the installer to get the stuff from a
mirror. For example,

   http://ftp.jaist.ac.jp/pub/OpenBSD/

is a mirror in Japan, which is sort of close to where I am. I have to
admit, I hate to write those urls down, too. But this is also part of
planning ahead. The file sets for a 32 bit intel or AMD CPU would be
in

   http://ftp.jaist.ac.jp/pub/OpenBSD/5.5/i386/

for the above mirror.

Buying the CD set would solve that problem, although you'd have to
wait for shipping.

Or you could download the install56.iso image, to have enough packages
for a working command-line system.

As another aside, these pages in the FAQ should help you plan ahead better:

http://www.openbsd.org/faq/index.html

 I could not acess the command line so I
 clicked the reset button
 on the front panel.

ctrl-C might have gotten you to a command line?

 When I tried to turn on again, the system didn't boot.

That's not too surprising. Although, I wonder, did you notice how far
it got in the boot process before it stopped?

You might want to read through these, to help you describe how far you
are getting:

http://en.wikipedia.org/wiki/Booting
http://www.openbsd.org/faq/faq14.html#Boot386

 I
 discovered that it
 only worked if I remove the hard drive.

I suppose you mean that it would boot the install CD?

There could be boot device order issues.

 Thinking that the problem was the harddrive I sent it to warranty to be
 repleaced.

Definitely a drastic step.

 I took
 10 long days (withou my computer) to arrive a new one.
 When it arrived, I tested and I saw that now it is working. I prepared a
 cable connection, and I
 started again the openbsd setup.
 It sucefully downloaded and installed everything, so I rebooted the system
 to boot my new fresh install.

I see from your later posts that you have installed Linux before. You
should understand there is a difference between Linux and openbsd.
Openbsd does not install a bootloader for you.

This part of the FAQ should provide some useful information:

http://www.openbsd.org/faq/faq4.html#Multibooting

 AND SHIT, everything happened as before, the system don't boot as before, I
 can't open the bios as before,

How did you open the BIOS when you were able to open the BIOS?

 and
  I got really mad.

 I don't know if I will be able to sent it to warranty again, but this isn't
 the right thing to do now that
  I discovered that the problem isn't with it, the problem is with Openbsd.

Or something.

 Could someone please explain me why this happened?

You are the only person at this time with enough information to
explain it, but you need to be able to tell us more than you are
teling us.

 Can you think about a way
 to fix this without send it to warranty?

I'm guessing you need to read through FAQ 14.7, on booting, that I
mentioned above:

http://www.openbsd.org/faq/faq14.html#Boot386

and then back to FAQ 4.9, again:

http://www.openbsd.org/faq/faq4.html#Multibooting

 Any other questions?

Did you do anything to tell your BIOS where to find your openbsd install?

How did you partition the disks?

How many partitions do you have?

Are you trying to multiboot with a Linux OS or MSWindows?

What kind of motherboard is it? Is the CPU 32 bit or 64 bit?

 send me a reply, I'm really in need of help

:-/

-- 
Joel Rees

Be careful when you look at conspiracy.
Look first in your own heart,
and ask yourself if you are not your own worst enemy.
Arm yourself with knowledge of yourself, as well.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 03:01, Joel Rees wrote:

By the way, how are you accessing the internet now?


My mother's notebook via wireless connection.

Or perhaps you forgot to write down the URL for a nearby mirror before
you started, so you could tell the installer to get the stuff from a
mirror. For example,

   http://ftp.jaist.ac.jp/pub/OpenBSD/


How this would help me if I had no internet connection?


When I tried to turn on again, the system didn't boot.


That's not too surprising. Although, I wonder, did you notice how far
it got in the boot process before it stopped?


This is the point had confusion.
It stopped on the bios screen. It even began to load the disc, because 
it didn't recognize it.
It didn't booted because my hard drive isn't more recognized. Not 
because
the system isn't correct installed. If the only problem was the system 
installation

I would be able to at least enter the BIOS.


I
discovered that it
only worked if I remove the hard drive.


I suppose you mean that it would boot the install CD?

There could be boot device order issues.


As I said before, my computer does nothing with the hard drive attached,
Thinking that the problem was the harddrive I sent it to warranty to 
be

repleaced.


Definitely a drastic step.
Definitely not a drastic step, since my test showed that it was the 
problem
and it really was because it worked the first time I tried when it 
arrived new

from warranty.


I took
10 long days (withou my computer) to arrive a new one.
When it arrived, I tested and I saw that now it is working. I prepared 
a

cable connection, and I
started again the openbsd setup.
It sucefully downloaded and installed everything, so I rebooted the 
system

to boot my new fresh install.


I see from your later posts that you have installed Linux before. You
should understand there is a difference between Linux and openbsd.
Openbsd does not install a bootloader for you.


Does a bad OpenBSD install would change how my BIOS detect my HDD, and 
make all the
rest hardware stop working when it is plugged, exactly as it happen when 
you put

a drive in short circuit?

AND SHIT, everything happened as before, the system don't boot as 
before, I

can't open the bios as before,


How did you open the BIOS when you were able to open the BIOS?



Pressing DEL or F2 on boot.

Regards,

--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Henrique Lengler]

On 2014-12-23 02:55, Eric Furman wrote:

No. This is done by the BIOS.
After the computer boots the BIOS then hands over control to the OS.


So this it the time the OS is able to do whatfuck it wants with my HDD, 
and

so the OS have control over HDD. Right?


And yes, that is a gross over simplification of what actually happens.
There is no way that any OS can 'break' a hard drive.


So why this happened when using OpenBSD?
--
Henrique Lengler

Re: Openbsd broke my hard drive twice! Getting frustrated

[Brent Cook]

On Mon, Dec 22, 2014 at 11:22 PM, Henrique Lengler
henriquel...@openmailbox.org wrote:
 On 2014-12-23 02:55, Eric Furman wrote:

 No. This is done by the BIOS.
 After the computer boots the BIOS then hands over control to the OS.


 So this it the time the OS is able to do whatfuck it wants with my HDD, and
 so the OS have control over HDD. Right?

 And yes, that is a gross over simplification of what actually happens.
 There is no way that any OS can 'break' a hard drive.


 So why this happened when using OpenBSD?
 --
 Henrique Lengler


I forgot to CC the list in the reply, sorry for the duplication:

Sometimes vendors do not do extensive testing, and do things like
hardcode strings in the firmware to expect Windows or Linux. Here is
an article discussing a problem with a Lenovo Thinkcentre that only
worked with Windows, Redhat or Fedora:

http://mjg59.dreamwidth.org/20187.html

There have been a couple of reports similar to this one that were fixed
with a firmware update from the motherboard or system vendor. I would
presume the firmware basically crashes if it sees a boot code written
on the hard drive it does not expect, even if it follows the
standards:

http://marc.info/?t=13988430601r=1w=2

http://marc.info/?l=openbsd-miscw=2r=1s=Axiomtek+NA570q=b

I worked on a new-ish laptop recently that would not boot from a CD or
any non-Windows partition unless I first removed the hard drive,
entered the EFI/Bios setup, set a password, then disabled EFI secure
boot.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Jonathon Sisson]

On Tue, Dec 23, 2014 at 03:22:51AM -0200, Henrique Lengler wrote:
 On 2014-12-23 02:55, Eric Furman wrote:
 No. This is done by the BIOS.
 After the computer boots the BIOS then hands over control to the OS.
 
 So this it the time the OS is able to do whatfuck it wants with my HDD, and
 so the OS have control over HDD. Right?
 
 And yes, that is a gross over simplification of what actually happens.
 There is no way that any OS can 'break' a hard drive.
 
 So why this happened when using OpenBSD?
 -- 
 Henrique Lengler
 
OpenBSD does not support UEFI secure boot.  I'm not a developer, so I won't
offer an answer as to why support is lacking, but I suspect it has something
to do with UEFI being a metric fuckton of bullshit.

That said, I'm willing to bet if you disable secure boot, it'll act differently
than what it is now.  And, depending on what distro of Linux you installed, it
may support UEFI (and hence the BIOS boot of Linux may not have been with 
UEFI disabled).

Re: Openbsd broke my hard drive twice! Getting frustrated

[Joel Rees]

On Tue, Dec 23, 2014 at 2:19 PM, Henrique Lengler
henriquel...@openmailbox.org wrote:
 On 2014-12-23 03:01, Joel Rees wrote:

 By the way, how are you accessing the internet now?


 My mother's notebook via wireless connection.

Would she mind too much if you took the time to read through the FAQs
I suggested?

 Or perhaps you forgot to write down the URL for a nearby mirror before
 you started, so you could tell the installer to get the stuff from a
 mirror. For example,

http://ftp.jaist.ac.jp/pub/OpenBSD/

 How this would help me if I had no internet connection?

Do you plan on accessing the internet once the OS is running?

How is that gong to work?

But that's not a question for now, I guess.

 When I tried to turn on again, the system didn't boot.

 That's not too surprising. Although, I wonder, did you notice how far
 it got in the boot process before it stopped?

 This is the point had confusion.
 It stopped on the bios screen.

So, it was booting to the BIOS.

 It even began to load the disc, because it
 didn't recognize it.

Yeah. You have to tell the BIOS where to look or it doesn't know where
to look. If it doesn't know where to look, how can it see enough to
recognize anything?

 It didn't booted because my hard drive isn't more recognized. Not because
 the system isn't correct installed.

This much, you could well be right about.

 If the only problem was the system
 installation
 I would be able to at least enter the BIOS.

Why do you want to go back to the BIOS without re-booting?

 I
 discovered that it
 only worked if I remove the hard drive.


 I suppose you mean that it would boot the install CD?

 There could be boot device order issues.

Or partition/master boot record, or, as others have mentioned, UEFI
issues, although I'm guessing you got UEFI worked out (switched to
legacy) when you installed a Linux OS a year ago.

Something you might try, re-install the Linux OS, but make sure you
leave about half the HD for openbsd. Then tell the Linux OS installer
you will be multibooting, if it asks. But I think you want to re-read
those FAQs first.

And while it it installing, read those FAQs I gave you the links to:

http://www.openbsd.org/faq/faq14.html#Boot386

http://www.openbsd.org/faq/faq4.html#Multibooting

Even if they are hard to understand, reading them again woud be a good idea.

 As I said before, my computer does nothing with the hard drive attached,

Except that it is showing you that is is attempting to boot.

It couldn't even attempt to boot if it weren't getting to the BIOS,
because it is the BIOS that is going looking for the OS telling you it
can't find it.

 Thinking that the problem was the harddrive I sent it to warranty to be
 repleaced.

 Definitely a drastic step.

 Definitely not a drastic step,

Okay, we'll pretend I didn't say it was a drastic step.

 since my test showed that it was the problem
 and it really was because it worked the first time I tried when it arrived
 new
 from warranty.

We can talk about that later.

 I took
 10 long days (withou my computer) to arrive a new one.
 When it arrived, I tested and I saw that now it is working. I prepared a
 cable connection, and I
 started again the openbsd setup.
 It sucefully downloaded and installed everything, so I rebooted the
 system
 to boot my new fresh install.

 I see from your later posts that you have installed Linux before. You
 should understand there is a difference between Linux and openbsd.
 Openbsd does not install a bootloader for you.

 Does a bad OpenBSD install would change how my BIOS detect my HDD, and make
 all the
 rest hardware stop working when it is plugged, exactly as it happen when you
 put
 a drive in short circuit?

Yeah. Let's talk about that later, too.

Except, I'm wondering whether I might be able to set the active
partition on the disk and it would then boot for you. If I were there.

The problem, I am sure, is not that the install is messed up. I'm
pretty sure you just

(1) don't have a boot loader,

(2) haven't written the master boot record,

and/or (3) haven't set the active parttion.

 AND SHIT, everything happened as before, the system don't boot as before,
 I
 can't open the bios as before,

 How did you open the BIOS when you were able to open the BIOS?

 Pressing DEL or F2 on boot.

Most BIOSses won't let you do that once they decide they can't find an
OS to boot. It's normal.

-- 
Joel Rees

Be careful when you look at conspiracy.
Look first in your own heart,
and ask yourself if you are not your own worst enemy.
Arm yourself with knowledge of yourself, as well.

Re: Openbsd broke my hard drive twice! Getting frustrated

[Steve Litt]

On Tue, 23 Dec 2014 03:22:51 -0200
Henrique Lengler henriquel...@openmailbox.org wrote:

 On 2014-12-23 02:55, Eric Furman wrote:
  No. This is done by the BIOS.
  After the computer boots the BIOS then hands over control to the OS.
 
 So this it the time the OS is able to do whatfuck it wants with my
 HDD, and
 so the OS have control over HDD. Right?
 
  And yes, that is a gross over simplification of what actually
  happens. There is no way that any OS can 'break' a hard drive.
 
 So why this happened when using OpenBSD?

There are so many variables here that the *only* way to find the root
cause is the process of eliminations. Guessing that OpenBSD did it will
only get you more mad.

If this were *my* computer I'd grab a couple blank CDs, go somewhere
where you can download, and download and burn System Rescue CD. You can
boot that and examine your computer, including the disk.

Start ruling out sections of the root cause scope, and pretty soon
you'll know the exact root cause. By the way, I think System Rescue CD
has SMART programs, so you can see whether your hard disk is damaged,
or just has lost its file system or GPT or MBR.

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance

Re: Openbsd broke my hard drive twice! Getting frustrated

[Maurice McCarthy]

On 2014-12-23 05:22, Henrique Lengler wrote:

On 2014-12-23 02:55, Eric Furman wrote:

No. This is done by the BIOS.
After the computer boots the BIOS then hands over control to the OS.


So this it the time the OS is able to do whatfuck it wants with my 
HDD, and

so the OS have control over HDD. Right?

And yes, that is a gross over simplification of what actually 
happens.

There is no way that any OS can 'break' a hard drive.


So why this happened when using OpenBSD?


I stand to be corrected but I do not think that OpenBSD can support 
UEFI nor GPT partitions, not yet anyhow.