Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
On Thu, 27 Mar 2008 08:36:28 -0400 Matthew Gillen <[hidden email]> wrote: > That sounds more like a BIOS level problem: you should be able tell the system > which drive to boot from. But it's trying to be smart and figure it out on > it's own, then getting tripped up. I'ts an Intel Whitebox. Yes, that is probably the case. > There's a quicker way to clear the MBR: > dd if=/dev/zero of=/dev/sda bs=512 count=1 I was unable to do that on the x86-64 system, even when I booted gparted. And yes, I did that from the ia64 box. But I also wanted a complete diagnostic on the drive. The badblock utility was able to give me the confidence. I mentioned that I also used dd. It is interesting that with that drive in the slot in the x86-64 system. I was able to boot gparted and Ubuntu (only once). In any case, the drive is back and working. This will be my last post since I am leaving for a trip in 10 minutes. -- -- Jerry Feldman <[hidden email]> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846 _______________________________________________ Discuss mailing list [hidden email] http://lists.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |