some troubles with mounting reiserfs

some troubles with mounting reiserfs

[Serge Rodrigues]

[-- Attachment #1: Type: text/plain, Size: 1780 bytes --]

Hi all,

 

            I have some troubles when I want to mount a reiserfs
partition I use the command :

 

            Mount -t reiserfs /dev/hdb1 /mnt/xxx

 

            The result is

 

            Mount : wrong fs type, bad options, bad superblock on
/dev/hdb1 or too many mounted file systems

 

            I've tried 

 

fsck.reiserfs -check

 

            The result :

 

                        The problem has occurred looks like a hardware
problem

                        Check your hard drive badblocks

 

                        Bread : Cannot read the block (17760256)

 

            Try :

 

            Badblocks -n -s -b 4096 /dev/hdb1 18000000 17700000

 

            The Result :

 

            All seems ok

 

            When I use : 

 

debug.reiserfs /dev/hdb1

 

The Result :

 

<-------------debugreiserfs, 2002------------->

reiserfsprogs 3.6.4

 

 

Filesystem state: consistent

 

Reiserfs super block in block 16 on 0x341 of format 3.6 with standard
journal

Count of blocks on the device: 20010808

Number of bitmaps: 611

Blocksize: 4096

Free blocks (count of blocks - used [journal, bitmaps, data, reserved]
blocks): 11317287

Root block: 8384

Filesystem is cleanly umounted

Tree height: 4

Hash function used to sort names: "r5"

Objectid map size 2, max 972

Journal parameters:

        Device [0x0]

        Magic [0x0]

        Size 8193 blocks (including 1 for journal header) (first block
18)

        Max transaction length 0 blocks

        Max batch size 0 blocks

        Max commit age 0

Blocks reserved by journal: 0

Fs state field: 0x0

sb_version: 2

inode generation number: 94

UUID: 00000000-0000-0000-0000-000000000000

LABEL:

Set flags in SB:

 

 

How to solve this problem ??

 

 

Thx a lot

 

Re: some troubles with mounting reiserfs

[Oleg Drokin]

Hello!

On Sun, Apr 27, 2003 at 12:25:18PM +0200, Serge Rodrigues wrote:
>             I have some troubles when I want to mount a reiserfs
> partition I use the command :
>             Mount -t reiserfs /dev/hdb1 /mnt/xxx
>             The result is
>             Mount : wrong fs type, bad options, bad superblock on
> /dev/hdb1 or too many mounted file systems

Well, what kernel version do you use?
What are the messages in kernel log? (e.g. run dmesg to see)

>             I've tried 
> fsck.reiserfs -check
>             The result :
>                         The problem has occurred looks like a hardware
> problem
>                         Check your hard drive badblocks
>                         Bread : Cannot read the block (17760256)

Hm, sounds like your partition is bigger than underlying block device and you recently have upgraded your kernel
to 2.4.21rc1 or something like that, no?

>             When I use : 
> debug.reiserfs /dev/hdb1
> The Result :
> <-------------debugreiserfs, 2002------------->
> reiserfsprogs 3.6.4
> Reiserfs super block in block 16 on 0x341 of format 3.6 with standard
> journal
> Count of blocks on the device: 20010808

Hm, but then debugfs should have complained too?

> How to solve this problem ??

We need to see what are the kernel messages.
also output of "fdisk -l /dev/hdb"

Bye,
    Oleg

RE : some troubles with mounting reiserfs

[Serge Rodrigues]

-----Message d'origine-----
De : Oleg Drokin [mailto:green@namesys.com] 
Envoyé : lundi 28 avril 2003 7:38
À : Serge Rodrigues
Cc : reiserfs-list@namesys.com
Objet : Re: some troubles with mounting reiserfs

Hello!

On Sun, Apr 27, 2003 at 12:25:18PM +0200, Serge Rodrigues wrote:
>             I have some troubles when I want to mount a reiserfs
> partition I use the command :
>             Mount -t reiserfs /dev/hdb1 /mnt/xxx
>             The result is
>             Mount : wrong fs type, bad options, bad superblock on
> /dev/hdb1 or too many mounted file systems

>> Well, what kernel version do you use?
>> What are the messages in kernel log? (e.g. run dmesg to see)

The Kernel is 2.4.20 with grsec security patch

Dmseg (resierfs)

reiserfs: checking transaction log (device 03:05) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 124k freed
Adding Swap: 530104k swap-space (priority -1)
reiserfs: checking transaction log (device 03:01) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
reiserfs: checking transaction log (device 03:06) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
reiserfs: checking transaction log (device 03:07) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
reiserfs: checking transaction log (device 03:08) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
reiserfs: checking transaction log (device 03:09) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
reiserfs: checking transaction log (device 03:0a) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
reiserfs: checking transaction log (device 03:0c) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=142082111,
sector=142082048
end_request: I/O error, dev 03:41 (hdb), sector 142082048
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=147587135,
sector=147587072
end_request: I/O error, dev 03:41 (hdb), sector 147587072
sh-2029: reiserfs read_bitmaps: bitmap block (#17760256) reading failed
reiserfs_read_super: unable to read bitmap
blk: queue c034fae4, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c034fc20, I/O limit 4095Mb (mask 0xffffffff)



>             I've tried 
> fsck.reiserfs -check
>             The result :
>                         The problem has occurred looks like a hardware
> problem
>                         Check your hard drive badblocks
>                         Bread : Cannot read the block (17760256)

>> Hm, sounds like your partition is bigger than underlying block device
and >> you recently have upgraded your kernel
>> to 2.4.21rc1 or something like that, no?

Yes but from 2.4.19 to 2.4.20 and exactly I have perform an new install
of this machine and put the HDD after the install

>             When I use : 
> debug.reiserfs /dev/hdb1
> The Result :
> <-------------debugreiserfs, 2002------------->
> reiserfsprogs 3.6.4
> Reiserfs super block in block 16 on 0x341 of format 3.6 with standard
> journal
> Count of blocks on the device: 20010808

Hm, but then debugfs should have complained too?

> How to solve this problem ??

>>We need to see what are the kernel messages.
>>also output of "fdisk -l /dev/hdb"

fdisk -l /dev/hdb :

Disk /dev/hdb: 81.9 GB, 81964302336 bytes
16 heads, 63 sectors/track, 158816 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdb1             1    158816  80043232+  83  Linux



>>Bye,
>>    Oleg


Thx oleg

Serge

Re: RE : some troubles with mounting reiserfs

[Oleg Drokin]

Hello!

On Mon, Apr 28, 2003 at 09:33:20PM +0200, Serge Rodrigues wrote:

> ReiserFS version 3.6.25
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=142082111,
> sector=142082048
> end_request: I/O error, dev 03:41 (hdb), sector 142082048
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=147587135,
> sector=147587072
> end_request: I/O error, dev 03:41 (hdb), sector 147587072
> sh-2029: reiserfs read_bitmaps: bitmap block (#17760256) reading failed
> reiserfs_read_super: unable to read bitmap

These are sure sign of something cannot be read from your disk.
Though I am not sure why badblocks outputs no info.
How about running badblocks without specifying start offset and device size?

Bye,
    Oleg

RE : RE : some troubles with mounting reiserfs

[Serge Rodrigues]

Hello,


-----Message d'origine-----
De : Oleg Drokin [mailto:green@namesys.com] 
Envoyé : mardi 29 avril 2003 7:41
À : Serge Rodrigues
Cc : reiserfs-list@namesys.com
Objet : Re: RE : some troubles with mounting reiserfs

Hello!

On Mon, Apr 28, 2003 at 09:33:20PM +0200, Serge Rodrigues wrote:

> ReiserFS version 3.6.25
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=142082111,
> sector=142082048
> end_request: I/O error, dev 03:41 (hdb), sector 142082048
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=147587135,
> sector=147587072
> end_request: I/O error, dev 03:41 (hdb), sector 147587072
> sh-2029: reiserfs read_bitmaps: bitmap block (#17760256) reading
failed
> reiserfs_read_super: unable to read bitmap

>>These are sure sign of something cannot be read from your disk.
>>Though I am not sure why badblocks outputs no info.
>>How about running badblocks without specifying start offset and device
size?


After a very very very long badblocks -n -s -b 4096 /dev/hdb1, it found
some badblocks. What I need to do for recover my HDD if any solution
exist ?



>>Bye,
>>    Oleg


Thx
Serge

Re: some troubles with mounting reiserfs

[Anders Widman]

> After a very very very long badblocks -n -s -b 4096 /dev/hdb1, it found
> some badblocks. What I need to do for recover my HDD if any solution
> exist ?

  The  best  thing is to use dd_rescue to copy the disk to a new drive
  of at least the same size, or to an imagefile that fits onto another
  drive.  Then you can run fsck on that imagefile or the new drive and
  send  your  old  one back for warranty service. DO NOT try to fsck a
  faulty drive. It will only cause more damage.

  //Anders


--------
PGP public key: https://tnonline.net/secure/pgp_key.txt

Re: RE : RE : some troubles with mounting reiserfs

[Oleg Drokin]

Hello!

On Thu, May 01, 2003 at 07:55:22PM +0200, Serge Rodrigues wrote:
> > ReiserFS version 3.6.25
> > hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=142082111,
> > sector=142082048
> > end_request: I/O error, dev 03:41 (hdb), sector 142082048
> > hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=147587135,
> > sector=147587072
> > end_request: I/O error, dev 03:41 (hdb), sector 147587072
> > sh-2029: reiserfs read_bitmaps: bitmap block (#17760256) reading
> failed
> > reiserfs_read_super: unable to read bitmap
> >>These are sure sign of something cannot be read from your disk.
> >>Though I am not sure why badblocks outputs no info.
> >>How about running badblocks without specifying start offset and device
> size?
> After a very very very long badblocks -n -s -b 4096 /dev/hdb1, it found
> some badblocks. What I need to do for recover my HDD if any solution
> exist ?

Well, you can read reiserfs-list archives for a solution that are posted there from 
time to time, or you can go to http://www.namesys.com/support.html and
use our paid services if you prefer to get direct instructions from us.

Bye,
    Oleg