Re: udev memory problem when trying to plug a disk with corrupted partition table
- To: <firstname.lastname@example.org>
- Subject: Re: udev memory problem when trying to plug a disk with corrupted partition table
- From: email@example.com
- Date: Tue, 02 Dec 2014 18:48:42 +0100
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <546E5C7E.email@example.com>
- References: <firstname.lastname@example.org> <20141117165515.GB24756@khazad-dum.debian.net> <email@example.com> <20141117183207.GE24756@khazad-dum.debian.net> <firstname.lastname@example.org> <546CFA85.email@example.com> <firstname.lastname@example.org> <546D3DF0.email@example.com> <546D47A2.firstname.lastname@example.org> <546D4EF8.email@example.com> <546DB0AB.firstname.lastname@example.org> <546DC4A8.email@example.com> <546E44D7.firstname.lastname@example.org> <546E5C7E.email@example.com>
Le 20.11.2014 22:26, Scott Ferguson a écrit :
On 21/11/14 06:45, Pascal Hambourg wrote:
Good question - because I didn't spend much time thinking about it,
because I haven't used ms-dos partition tables for a very long time?
Scott Ferguson a écrit :
Might be worth fscking the disk first in case that's where the
Why ? fsck works on filesystems, not disks or partition tables.
Regardless - maybe badblocks would be a better way of checking if the
problem is a result of damage to where the E(P)BRs are written?
Certainly simpler than examining the E(P)BRs for errors which would
my next course of action if I had no backups of the disk.
(I suspect) There are at least two possible scenarios(?) which would
result in a problem that the OP is experiencing[*1]:-
;the OP accidentally overwrote an EBR i.e. created another extended
partition at some later point (1st sector of the extended partition?)
;a damaged sector containing an EBR
In the first case parted rescue may/should be able to fix the
The OP could probably get more info by checking the E(P)BRs. The
'might' be in the first or last E(P)BR (again, I 'suspect' Martin is
right about the looping)
Perhaps (from unreliable memory):-
dd if=/dev/sdc bs=512 count=1 skip=22026238 | hexdump -C
likewise with the last extended partition, and then the same on the
E(P)BRs 'might' show the error?
I note that's a lot of suspicions, mights, and guesses - but again, I
welcome input and correction.
[*1] I'm guessing, and welcome input - as I suspect would the OP
An interesting problem, sadly the person most likely to know the
hasn't been seen on the lists for some time.
First, sorry for delay and thanks for replies. I won't have time to fix
this for now, I will try to find time ASAP. Not that I really mind the
data which were on that disk, but it will allow me to tinker with
partition tables and such things on which I do not have a good
I had even no idea that logical partitions were a chained list, but now
that you say it, it makes sense.
Also, what is EBR (or EPBR, which seems to be some sort of enhanced
whatever may be a EBR)? To fix things, I tried to take a look at
testdisk, which was able to find partitions. Lot of them, in facts,
included lot of... removed partitions (I did a lot of experiments on
that disk before). Plus, I have no idea about how to ask it (testdisk)
to fix, apply things?
Any document about how to use it? Not the man, I already have read it,
and it's plain useless.