• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Linux can't read my partition table?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Can you explain it?

Not without seeing the before and after partition tables, but partition tables and drive geometry stuff is weird and it's easy for one system to see a drive one way and another to see it differently.
 
Originally posted by: Nothinman
Not without seeing the before and after partition tables, but partition tables and drive geometry stuff is weird and it's easy for one system to see a drive one way and another to see it differently.
True, that! :thumbsup:

The first HD I owned had a PerStor controller - talk about weird geometry! I still don't understand how it worked - used some sort of pseudo-RLL encoding on MFM HDs. You had to format it with proprietary software (using their special controller) and it would turn a 20MB HD into 60MB... if I remember correctly.

And, remember those virus-like 'disk managers', such as Ontrack - trying to beat the 137GB limit?!?!? One hiccup and your data was toast!

Okay, now I get it!

MediaDirect is probably in that genre, corrupted the MBR, the other partitions, reported phony cylinder boundaries to fdisk, or whatever... and Linux said "FU"! 😉

How's that for ghetto forensics?
 
Back
Top