Unexpected bios behavior??? due to connection of an external drive.
jd1008
jd1008 at gmail.com
Wed Mar 18 00:08:28 UTC 2015
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 440 bytes?
I am a bit concerned about dd'ing 440 zeros from /dev/zero
into this drive, as it has about 0.5 TB of data on it, and I have
no room (yet) to back it up to :)
More information about the users
mailing list