Can't mount (obviously intact) Reiser partitions

Hi all,

I include a description and several outputs below, throwing some light on the problem.

Does anybody have an idea ?

Many thanks in advance
Mike


Description

I’m running openSUSE 11.2.

The partitions are on a seperate SCSI disk.

The partitioner (under YAST) finds them and lists them
as Reiser partitions.

The disk isn’t just some old errorneous drive:
it was a spare disk not used very even after putting it in use,
and smartctl gives

(host):~ # smartctl -a /dev/sdb
smartctl 5.39 2009-08-08 r2872~ [i686-pc-linux-gnu] (openSUSE RPM)
Copyright (C) 2002-9 by Bruce Allen, http://smartmontools.sourceforge.net                             
                                                                                                      
Device: IBM      DNES-318350W     Version: SAH0                                                       
Serial number:         AKLT7642                                                                       
Device type: disk                                                                                     
Local Time is: Fri Mar  4 15:41:58 2011 CET                                                           
Device supports SMART and is Enabled                                                                  
Temperature Warning Disabled or Not Supported                                                         
SMART Health Status: OK                                                                               

Current Drive Temperature:     41 C
Drive Trip Temperature:        85 C
Elements in grown defect list: 0   

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors     
read:          0        0         0         0          0         39.704           0     
write:         0        0         0         0          0         75.599           0     

Non-medium error count:        0
Device does not support Self Test logging

Here’s what mount says:

(host):~ # mount /home102
mount: wrong fs type, bad option, bad superblock on /dev/sdb6,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

and dmesg:

(host):~ # dmesg | tail
 3580.662429] REISERFS (device sdb6): journal params: device sdb6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
 3580.667893] REISERFS (device sdb6): checking transaction log (sdb6)
 3580.704982] sd 0:0:1:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
 3580.705105] sd 0:0:1:0: [sdb] Sense Key : Aborted Command [current]
 3580.705203] sd 0:0:1:0: [sdb] Add. Sense: Scsi parity error
 3580.705305] end_request: I/O error, dev sdb, sector 10138498
 3580.706227] end_request: I/O error, dev sdb, sector 10138498
 3580.706408] REISERFS warning (device sdb6): journal-837 _update_journal_header_block: IO error during journal replay
 3580.706509] REISERFS warning (device sdb6): reiserfs-2006 journal_init: Replay Failure, unable to mount
 3580.706898] REISERFS warning (device sdb6): sh-2022 reiserfs_fill_super: unable to initialize journal space

The reporting of a ‘Scsi parity error’ in this puzzles me,
because the disk can be accessed and scanned
without any problem:

a subsequent reiserfsck (after scanning for some time) gives

(host):~ # reiserfsck --check /dev/sdb6
reiserfsck 3.6.21 (2009 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/sdb6
Will put log info to 'stdout'                                  

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########                                                                  
reiserfsck --check started at Fri Mar  4 15:45:48 2011                       
###########                                                                  
Replaying journal: Done.                                                     
Reiserfs journal '/dev/sdb6' in blocks [18..8211]: 0 transactions replayed   
Checking internal tree.. finished                                            
Comparing bitmaps..finished                                                  
Checking Semantic tree:                                                      
finished                                                                       
No corruptions found                                                           
There are on the filesystem:                                                   
        Leaves 3428                                                            
        Internal nodes 25                                                      
        Directories 2780                                                       
        Other files 17114                                                      
        Data block pointers 2471951 (898 of them are zero)                     
        Safe links 0                                                           
###########                                                                    
reiserfsck finished at Fri Mar  4 15:46:26 2011                                
###########                                                                    

The output with respect to the other partition (/dev/sdb5)
is absolutely similar.

Finally the output of debugreiserfs:

(host):~ # debugreiserfs /dev/sdb6
debugreiserfs 3.6.21 (2009 www.namesys.com)


Filesystem state: consistent

Reiserfs super block in block 16 on 0x816 of format 3.6 with standard journal
Count of blocks on the device: 3221024
Number of bitmaps: 99
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 738209
Root block: 655424
Filesystem is clean
Tree height: 4
Hash function used to sort names: "r5"
Objectid map size 50, max 972
Journal parameters:
        Device [0x0]
        Magic [0x787be56]
        Size 8193 blocks (including 1 for journal header) (first block 18)
        Max transaction length 1024 blocks
        Max batch size 900 blocks
        Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x0:
sb_version: 2
inode generation number: 194946
UUID: d32cd784-2380-4f07-a99d-1c39b1aced4d
LABEL: home102
Set flags in SB:
        ATTRIBUTES CLEAN
Mount count: 28
Maximum mount count: Disabled. Run fsck.reiserfs(8) or use tunefs.reiserfs(8) to enable.
Last fsck run: Never with a version that supports this feature.
Check interval in days: Disabled. Run fsck.reiserfs(8) or use tunefs.reiserfs(8) to enable.

Summary: The quite fresh disk can be accessed and scanned without errors.
The partitions are seen by the partitioner and reiserfsck etc.
But mount fails. :frowning:

ratzi wrote:
> Summary: The quite fresh disk can be accessed and scanned without
> errors.
> The partitions are seen by the partitioner and reiserfsck etc.
> But mount fails. :frowning:

(a) run the mount command with all options shown explicitly (or show us
fstab!)

(b) add -v to mount and see what it says

Hi djh,

Thanks for the reply.

What do you mean with

>
> run the mount command with all options shown explicitly
>

In the listings, in the first line,
a copy of the command line that gave the output
is respectively included, so you directly see all the options
that I used and which I didn’t use.

OK, mount -v :

(host):/etc # mount -v /dev/sdb6
mount: wrong fs type, bad option, bad superblock on /dev/sdb6,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

(host):/etc # mount -v /home102
mount: wrong fs type, bad option, bad superblock on /dev/sdb6,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

And here’s for /etc/fstab :

(host):/etc # more fstab
/dev/sda5                                             /                    ext3       acl,user_xattr
      1 1
/dev/sda6                                             /home                ext3       acl,user_xattr
      1 2
/dev/disk/by-id/scsi-SIBM_DNES-318350W_AKL08656-part1 swap                 swap       defaults
      0 0
/dev/disk/by-id/ata-IBM-DTTA-351010_WF0KFTZ4177-part1 /windows/C           vfat       users,gid=users,
umask=0002,utf8=true 0 0
/dev/disk/by-id/ata-IBM-DTTA-351010_WF0KFTZ4177-part5 /windows/D           vfat       users,gid=users,
umask=0002,utf8=true 0 0
/dev/disk/by-id/ata-IBM-DTTA-351010_WF0KFTZ4177-part6 /windows/E           vfat       users,gid=users,
umask=0002,utf8=true 0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
/dev/sdb6            /home102             reiserfs   user,noauto,acl,user_xattr 0 0
/dev/sdb5            /sys102              reiserfs   user,noauto,acl,user_xattr 0 0


Mike

On 2011-03-04 20:06, ratzi wrote:
>
> Hi djh,
>
> Thanks for the reply.
>
> What do you mean with
>
>>
>> run the mount command with all options shown explicitly
>>
>

That you did not. You entered a mount command that doesn’t have both mount
directory and device, which would work if there is a corresponding fstab
line - but you failed to post fstab, you did now.

> (host):/etc # mount -v /home102
> mount: wrong fs type, bad option, bad superblock on /dev/sdb6,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so

> /dev/sdb6 /home102 reiserfs user,noauto,acl,user_xattr 0 0

It should be 0 1, but it would not change things.

Your problem is this:

> 3580.706408] REISERFS warning (device sdb6): journal-837 _update_journal_header_block: IO error during journal replay

The disk has a problem with writes, at least in the region where the log sits.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Dear Carlos,

I’m not yet convinced that this disk is bad.

The simplest thing would be to re-format it
(probably with ext3 this time),
and to re-install some system on it,
which obviously requires writes.

Maybe in the end, I’ll do just that.

But I’m willing to make some experiment, because
there is no critical data on that disk - or I have a backup
of that data :wink:

So, any risky suggestions ?

Yours
Mike

On 2011-03-04 22:06, ratzi wrote:
>
> Dear Carlos,
>
> I’m not yet convinced that this disk is bad.

I haven’t said that.

You have a problem with operations writing to a at least a region of the
disk. It can be the disk, the cable, the motherboard, or even the software.

Notice that the SMART test does not test the cable nor the board - and that
disk is so old that the SMART testing is weak. You need external testing.

> The simplest thing would be to re-format it

It will fail.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

resolved !

Dear Carlos,

This morning I took the time to open the PC.

You were absolutely right, it was a hardware problem.

The motherboard was unlikely to be the cause,
like the SCSI controller, because this and a 2nd SCSI HD
(still working, running 11.2 from it) are attached at the same SCSI
adapter/controler, at the same bus (i.e. at the same SCSI cable).

It was the plug of the SCSI cable which got a loose fit !

I then recalled that someone once gave me the tip that obscure errors
in many cases are caused by contact problems, and that unplugging
and re-plugging the device in many cases solves the problem …

I didn’t get to the point where I would have tried that,
because the volumes mount fine again now,
but you obviously were very right in this as well.

Thank you very much for your helpful advice.

Mike

On 03/06/2011 03:36 PM, ratzi wrote:
>
> Dear Carlos,
>
> You were absolutely right, it was a hardware problem.
>
> you obviously were very right in this as well.
>
> Thank you very much for your helpful advice.

please don’t be so gushy…already Carlos thinks he is the smartest
one here!! :wink:


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

On 2011-03-06 16:12, DenverD wrote:
> On 03/06/2011 03:36 PM, ratzi wrote:
>>
>> Dear Carlos,
>>
>> You were absolutely right, it was a hardware problem.
>>
>> you obviously were very right in this as well.
>>
>> Thank you very much for your helpful advice.
>
> please don’t be so gushy…already Carlos thinks he is the smartest
> one here!! :wink:

ROTFL! X’-)


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)