Re: Saving Partition tables and boot records
- From: Whoever <nobody@xxxxxxxxxxxx>
- Date: Sat, 21 Jan 2006 11:33:52 -0800
On Fri, 20 Jan 2006, Ari Rankum wrote:
Whoever wrote:My first thought for this posting was "Windows trashed my Linux install", because that seems to be what has happened.
I'd say it rather sounds like *you* trashed your Linux box.
From the above, I deduce that the partition table is trashed. I think this happened while running some MPEG rendering (getting home movies onto DVD). I had noticed a lot of segementation faults while compiling stuff under Linux after installing additional memory.
Think about what a segmentation fault means - you're trying to access memory you shouldn't be trying to access. Why could that be? Oh, what? you just added more memory? Hmm. You added more memory and suddenly a new phenomenon of lots of seg faults. Let's see, your computer stores data and instructions in memory. You have unreliable memory access. Does that mean that you could be executing instructions other than the instructions you intend? Does that mean you could be accessing data other than the data you intend? Yes to both. Now, if you are trying to access particular regions on a disk, does that mean you could be accessing other regions on the disk than the ones you intend? Yes.
Thank you for your comments. Apparently you did not notice the attempt at some slight humor and instead decided to launch into a flame.
Just to make matters worse, you completely ignore much of my posting: ie. that I already checked the memory with memtest and it was OK. So, you can hardly suggest I ignored the problem, can you?
So: my questions are: 1. Assuming the partition table is trashed, is there any possible means to recover it? 2. In the event that I completely re-build, how can I save the partiton table and boot records (including Windows' boot record) so that I can recover from similar situations? 3. Why should I be getting these problems if Memtest86 thinks the memory is OK?
First, remove the additional memory and see if you get lucky and can boot the system.
As I mentioned, if you had cared to read my posting, the system boots -- it boots LILO, but the only images that will boot from that stage are the Memetest images.
If you've got a rescue disk, or Partition Magic, I'd try that next.
Alternatively, you could get a Linux LiveCD and boot from that and see if you can mount your hard drive in order to recover whatever files didn't get clobbered before any more damage is done.
* make a mount point (mkdir /foo)
* mount the hard drive (IDE: mount /dev/hdaX /foo) [assuming 1 IDE]
(SATA: mount /dev/sdaX /foo) [assuming 1 SATA]
X in the device name is likely 1, 2, or 3
* list the contents of the directory at the mount point
* if you can read sensible stuff like filenames you recognize, you can recover some of your loss.
* you can either shutdown and load another hard drive with a filesystem on it and copy stuff from the fragged drive to another, or network the fragged machine to another and copy stuff over.
Please read what you wrote again. If the partition table is trashed then I am not going to be able to mount the partitions, am I?
Did you answer ANY of the questions I posed? Or just the questions YOU THOUGHT I asked? (hint: did I ask for help recovering files, or help recovering partions?)
So, to summarize, you ignore much of what I wrote, launched into a childish flame and then did not provide any information relevant to my
situation.
.
- References:
- Saving Partition tables and boot records
- From: Whoever
- Re: Saving Partition tables and boot records
- From: Ari Rankum
- Saving Partition tables and boot records
- Prev by Date: Re: Mactels and linux?
- Next by Date: Re: REALLY cheep very compatible video card?
- Previous by thread: Re: Saving Partition tables and boot records
- Next by thread: Re: Saving Partition tables and boot records
- Index(es):
Relevant Pages
|
