* reiaserfsck core dumps
@ 2004-01-11 22:39 B. J. Zolp
2004-01-12 7:40 ` reiserfsck " B. J. Zolp
2004-01-12 10:15 ` reiaserfsck " Vitaly Fertman
0 siblings, 2 replies; 6+ messages in thread
From: B. J. Zolp @ 2004-01-11 22:39 UTC (permalink / raw)
To: reiserfs-list
I have a LVM partition that I cannot seem to mount anymore. Mount tells
me the standard "Too many mounted files systems.... " message. So I
decided to run reiserfsck on it, well when i do that it soon crashes
with this output:
[root@orion root]# reiserfsck /dev/vg0/logical0
reiserfsck, 2002 - reiserfsprogs 3.6.3Will read-only check consistency
of the filesystem on /dev/vg0/logical0
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes):Yes
###########
reiserfsck --check started at Sun Jan 11 15:19:58 2004
###########
bread: Cannot read a block # 119472128.
Aborted (core dumped)
Now, I am pretty sure the LVM is intact, all the drives are added
correctly and all that is ok. I ran badblocks on the partition and it
gave me a list of about ~1000 badblocks. Is there a way I can use this
list of blocks to my advantage to recover this partition, I would like
to get data from it.
Thanks
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiserfsck core dumps
2004-01-11 22:39 reiaserfsck core dumps B. J. Zolp
@ 2004-01-12 7:40 ` B. J. Zolp
2004-01-12 10:15 ` reiaserfsck " Vitaly Fertman
1 sibling, 0 replies; 6+ messages in thread
From: B. J. Zolp @ 2004-01-12 7:40 UTC (permalink / raw)
To: B. J. Zolp; +Cc: reiserfs-list
BTW, this is on a Mandrake 9.0 machine using the stock reiserfsck 3.6.3
version.
B. J. Zolp wrote:
> I have a LVM partition that I cannot seem to mount anymore. Mount
> tells me the standard "Too many mounted files systems.... " message.
> So I decided to run reiserfsck on it, well when i do that it soon
> crashes with this output:
>
> [root@orion root]# reiserfsck /dev/vg0/logical0
> reiserfsck, 2002 - reiserfsprogs 3.6.3Will read-only check consistency
> of the filesystem on /dev/vg0/logical0
> Will put log info to 'stdout'
>
> Do you want to run this program?[N/Yes] (note need to type Yes):Yes
> ###########
> reiserfsck --check started at Sun Jan 11 15:19:58 2004
> ###########
>
> bread: Cannot read a block # 119472128.
>
>
>
> Aborted (core dumped)
>
>
>
> Now, I am pretty sure the LVM is intact, all the drives are added
> correctly and all that is ok. I ran badblocks on the partition and it
> gave me a list of about ~1000 badblocks. Is there a way I can use
> this list of blocks to my advantage to recover this partition, I would
> like to get data from it.
>
>
> Thanks
>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiaserfsck core dumps
2004-01-11 22:39 reiaserfsck core dumps B. J. Zolp
2004-01-12 7:40 ` reiserfsck " B. J. Zolp
@ 2004-01-12 10:15 ` Vitaly Fertman
2004-01-12 18:28 ` B. J. Zolp
1 sibling, 1 reply; 6+ messages in thread
From: Vitaly Fertman @ 2004-01-12 10:15 UTC (permalink / raw)
To: B. J. Zolp, reiserfs-list
On Monday 12 January 2004 01:39, B. J. Zolp wrote:
> I have a LVM partition that I cannot seem to mount anymore. Mount tells
> me the standard "Too many mounted files systems.... " message. So I
> decided to run reiserfsck on it, well when i do that it soon crashes
> with this output:
>
> [root@orion root]# reiserfsck /dev/vg0/logical0
> reiserfsck, 2002 - reiserfsprogs 3.6.3
Please update the version of reiserfsprogs.
> Will read-only check consistency
> of the filesystem on /dev/vg0/logical0
> Will put log info to 'stdout'
>
> Do you want to run this program?[N/Yes] (note need to type Yes):Yes
> ###########
> reiserfsck --check started at Sun Jan 11 15:19:58 2004
> ###########
>
> bread: Cannot read a block # 119472128.
Do you see anything related in the syslog? Looks like a bad block
or an access beyond end of device.
> Aborted (core dumped)
>
>
>
> Now, I am pretty sure the LVM is intact, all the drives are added
> correctly and all that is ok. I ran badblocks on the partition and it
> gave me a list of about ~1000 badblocks. Is there a way I can use this
> list of blocks to my advantage to recover this partition, I would like
> to get data from it.
>
>
> Thanks
--
Thanks,
Vitaly Fertman
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiaserfsck core dumps
2004-01-12 10:15 ` reiaserfsck " Vitaly Fertman
@ 2004-01-12 18:28 ` B. J. Zolp
2004-01-12 21:59 ` Vitaly Fertman
0 siblings, 1 reply; 6+ messages in thread
From: B. J. Zolp @ 2004-01-12 18:28 UTC (permalink / raw)
To: Vitaly Fertman; +Cc: reiserfs-list
Vitaly Fertman wrote:
>On Monday 12 January 2004 01:39, B. J. Zolp wrote:
>
>
>>I have a LVM partition that I cannot seem to mount anymore. Mount tells
>>me the standard "Too many mounted files systems.... " message. So I
>>decided to run reiserfsck on it, well when i do that it soon crashes
>>with this output:
>>
>>[root@orion root]# reiserfsck /dev/vg0/logical0
>>reiserfsck, 2002 - reiserfsprogs 3.6.3
>>
>>
>
>Please update the version of reiserfsprogs.
>
>
Ok, I am runninf 3.6.11 now. Still getting the same crash though, but
new info:
The problem has occurred looks like a hardware problem.
If you have bad blocks, we advise you to get a new hard
drive, because once you get one bad block that the disk
drive internals cannot hide from your sight, the chances
of getting more are generally said to become much higher
(precise statistics are unknown to us), and this disk drive
is probably not expensive enough for you to risk your time
and data on it. If you don't want to follow that advice,
then if you have just a few bad blocks, try writing to the
bad blocks and see if the drive remaps the bad blocks (that
means it takes a block it has in reserve and allocates it
for use for requests of that block number). If it cannot
remap the block, this could be quite bad, as it may mean
that so many blocks have gone bad that none remain in
reserve to allocate.
bread: Cannot read the block (119472128): (Input/output error).
Aborted (core dumped)
>
>
>>Will read-only check consistency
>>of the filesystem on /dev/vg0/logical0
>>Will put log info to 'stdout'
>>
>>Do you want to run this program?[N/Yes] (note need to type Yes):Yes
>>###########
>>reiserfsck --check started at Sun Jan 11 15:19:58 2004
>>###########
>>
>>bread: Cannot read a block # 119472128.
>>
>>
>
>Do you see anything related in the syslog? Looks like a bad block
>or an access beyond end of device.
>
>
Syslog is giving me:
Jan 12 11:07:45 orion kernel: hdb: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Jan 12 11:07:45 orion kernel: hdb: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=10158456, high=0, low=10158456,
sector=10158456
Jan 12 11:07:45 orion kernel: end_request: I/O error, dev 03:40 (hdb),
sector 10158456
I did smartctl -a /dev/hdb and found this in the output:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 008 001
063 Pre-fail FAILING_NOW 616
If I was to dd this drive to a new one would reiserfsck be more
cooperative? The odd thing is that my /dev/hda gave me a the same error
a few weeks back and used dd to copy it to a new drive and things worked
ok again. I find it odd that two drives would have this error within
such a short length of time.
Well thanks for your help
>
>
>>Aborted (core dumped)
>>
>>
>>
>>Now, I am pretty sure the LVM is intact, all the drives are added
>>correctly and all that is ok. I ran badblocks on the partition and it
>>gave me a list of about ~1000 badblocks. Is there a way I can use this
>>list of blocks to my advantage to recover this partition, I would like
>>to get data from it.
>>
>>
>>Thanks
>>
>>
>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiaserfsck core dumps
2004-01-12 18:28 ` B. J. Zolp
@ 2004-01-12 21:59 ` Vitaly Fertman
2004-01-12 22:27 ` B. J. Zolp
0 siblings, 1 reply; 6+ messages in thread
From: Vitaly Fertman @ 2004-01-12 21:59 UTC (permalink / raw)
To: B. J. Zolp; +Cc: reiserfs-list
> Jan 12 11:07:45 orion kernel: hdb: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> Jan 12 11:07:45 orion kernel: hdb: dma_intr: error=0x40 {
> UncorrectableError }, LBAsect=10158456, high=0, low=10158456,
> sector=10158456
> Jan 12 11:07:45 orion kernel: end_request: I/O error, dev 03:40 (hdb),
> sector 10158456
So your harddrive has bad blocks, have a look at
http://www.namesys.com/bad-block-handling.html
to get the info how to handle them.
If you need our further assistance visit please our support
page in terms of which we deal with hardware problems:
http://www.namesys.com/support.html
--
Thanks,
Vitaly Fertman
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: reiaserfsck core dumps
2004-01-12 21:59 ` Vitaly Fertman
@ 2004-01-12 22:27 ` B. J. Zolp
0 siblings, 0 replies; 6+ messages in thread
From: B. J. Zolp @ 2004-01-12 22:27 UTC (permalink / raw)
Cc: reiserfs-list
The site suggests doing this:
reiserfsck --badblocks file device
but as far as I can tell "--badblocks" is no longer supported.
Vitaly Fertman wrote:
>>Jan 12 11:07:45 orion kernel: hdb: dma_intr: status=0x51 { DriveReady
>>SeekComplete Error }
>>Jan 12 11:07:45 orion kernel: hdb: dma_intr: error=0x40 {
>>UncorrectableError }, LBAsect=10158456, high=0, low=10158456,
>>sector=10158456
>>Jan 12 11:07:45 orion kernel: end_request: I/O error, dev 03:40 (hdb),
>>sector 10158456
>>
>>
>
>So your harddrive has bad blocks, have a look at
> http://www.namesys.com/bad-block-handling.html
>to get the info how to handle them.
>If you need our further assistance visit please our support
>page in terms of which we deal with hardware problems:
> http://www.namesys.com/support.html
>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-01-12 22:27 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-11 22:39 reiaserfsck core dumps B. J. Zolp
2004-01-12 7:40 ` reiserfsck " B. J. Zolp
2004-01-12 10:15 ` reiaserfsck " Vitaly Fertman
2004-01-12 18:28 ` B. J. Zolp
2004-01-12 21:59 ` Vitaly Fertman
2004-01-12 22:27 ` B. J. Zolp
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.