Thursday Jul 14, 2005
Thursday Apr 21, 2005
By jmcp-Oracle on Apr 21, 2005
I figured I should boot it to see what it thought was going on. That was ok, but running partition magic was when things went downhill fast. PM decided that my partition table had errors, and would I like it to fix them? I was really stupid at this point, and clicked yes.
Not only could I not boot back to MS-Windows, but I was unable to boot Solaris either...
Fortunately my desktop Solaris box was unaffected, so with a bit of digging I was able to find the System Rescue CD iso, pull it down, burn it and boot from it. That was great, but sfdisk and cfdisk both told me I had a bodgy partition table (duh! I knew that already!) and refused to help. By this point I was getting quite frantic, and googled again and again, eventually coming up with a hit on gpart.
I am very pleased to say that gpart saved my laptop. It was included on the linux System Rescue CD as /usr/bin/gpart.
Gpart has a scan option where it looks at where your partition table should be, and tries to interpret the data which it finds. I used this first, and wrote down exactly what it produced. Fortunately for me it matched what I remembered of my disk layout, so I re-ran it with the "-W" option to write the corrected partition table to disk.
Then deep breaths, sync, sync, sync, reboot..... grub menu.... YAY!!! I'm back to life!
Of course MS-Windows still won't boot properly -- gets to a certain point and hard-hangs, or just reboots the laptop entirely.... but that's a topic for another day.
Now I'm doing another backup of my data to a workstation in the office..... because you never know.
I'm also emailing the author of gpart to thank him for his utility, and request that he enhance the list of known partition types to include Solaris2 (== 0xbf by the way) which is what Solaris10 installations use now.
Thursday Apr 14, 2005
By jmcp-Oracle on Apr 14, 2005
By jmcp-Oracle on Apr 14, 2005
Wednesday Apr 06, 2005
By jmcp-Oracle on Apr 06, 2005
Friday Mar 11, 2005
By jmcp-Oracle on Mar 11, 2005
Friday Feb 18, 2005
By jmcp-Oracle on Feb 18, 2005
I couldn't really think of an "interesting" name to call it, but at the time I got it I was playing with some code which was decidedly broken. So that's what the laptop's called.
Of course, given that I bfu it every week or so in order to keep mostly current with new builds of Solaris, I have "warm-brickified" it several times so calling it "broken" seems appropriate.
The main error that I tend to make with bfu is forgetting to correctly merge or update the driver aliases and driver classes. Sometimes I forget the major number too.
I work at Oracle in the Solaris group. The opinions expressed here are entirely my own, and neither Oracle nor any other party necessarily agrees with them.
- Oracle Instant Client: now available in IPS
- help! Non-aligned writes are killing my zpool!
- My own private crash-n-burn farm: using kernel zones for speedy testing
- Please update your address book
- Announcement: inaugural meeting of Brisbane Oracle Solaris User Group
- And before I forget it \*again\* ...
- This blog is moving
- Migrating from Solaris Express to OpenSolaris
- Vodafone Mobile Broadband with a Huawei K3520/E169
- Presentations and flickrstream of KCA2009 available