Not sure if this is the right place for this question...anyway, here goes.

 

I've set my unRAID array up fine, and copied lots of data to it. 2x1TB and 1TB Parity, all lovely. However, I just wanted to reassure myself that if that machine ever died I'd be able to read the drives on their own somewhere else.

 

So...I have Centos 5.5 installed, and added reiserfs support from the CentosPlus repo.

 

I add the module :-

modprobe reiserfs

 

/proc/filesystems shows reiserfs as available.

 

If I then try :-

mount -t reiserfs /dev/sda1 /mnt/SATA1

 

the machine hangs and kb/mouse are useless, and it needs to be switched off.

 

Checking the filesystem shows the following :-

root@cerbera bin]# /sbin/sfdisk -l /dev/sda

 

Disk /dev/sda: 121601 cylinders, 255 heads, 63 sectors/track

Warning: The partition table looks like it was made

  for C/H/S=*/1/0 (instead of 121601/255/63).

For this listing I'll assume that geometry.

Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

 

  Device Boot Start  End    MiB    #blocks  Id  System

/dev/sda1        0+ 953869- 953870- 976762552+  83  Linux

/dev/sda2        0      -      0          0    0  Empty

/dev/sda3        0      -      0          0    0  Empty

/dev/sda4        0      -      0          0    0  Empty

 

[root@cerbera bin]# /sbin/fsck.reiserfs /dev/sda

reiserfsck 3.6.19 (2003 www.namesys.com)

 

*************************************************************

** If you are using the latest reiserfsprogs and  it fails **

** please  email bug reports to [email protected], **

** 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/sda

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

 

reiserfs_open: the reiserfs superblock cannot be found on /dev/sda.

Failed to open the filesystem.

 

If the partition table has not been changed, and the partition is

valid  and  it really  contains  a reiserfs  partition,  then the

superblock  is corrupted and you need to run this utility with

--rebuild-sb.

 

It seems to think that the drive has a superblock problem. Have I missed a step here when trying to read the raw array drive from another os or machine? Should I really have to use --rebuild-sb? Sounds a bit risky to me.

 

I really want to be able to mount these drives (read only of course) elsewhere as and when I need to, but it seems not to work for me.

 

Cheers,

Spence

 

The kernels differ between Centos5.5 and unraid. Although that should not be the issue.

This should work.

 

Also consider the mount command on unraid.

mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime

 

maybe those options are required on Centos5.5?

I've set my unRAID array up fine, and copied lots of data to it. 2x1TB and 1TB Parity, all lovely. However, I just wanted to reassure myself that if that machine ever died I'd be able to read the drives on their own somewhere else.

 

I've swapped out the motherboard on my unRAID server more than once, actually I'm on my 3rd one (each one different make/model).  It's possible that any new motherboard alters the position in the hard drive lineup but the serial numbers identifying each drive will be the same.  It takes a few minutes to configure the hard drives back into the array (from the unraid web menu) and then you're back in business.  

You can see your hard drive's serial numbers in /dev/disk/by-id.  So if the hardware on your machine dies it's no problem replacing that.

You would run reiserfsck on partition1, not on the entire disk

 

So...

 

reiserfsck --check /dev/sda1

 

not /dev/sda

You would run reiserfsck on partition1, not on the entire disk

 

So...

 

reiserfsck --check /dev/sda1

 

not /dev/sda

 

Ok. Unfortunately the output is the same. Superblock problems.

 

[root@cerbera bin]# /sbin/reiserfsck --check /dev/sda1

reiserfsck 3.6.19 (2003 www.namesys.com)

 

*************************************************************

** If you are using the latest reiserfsprogs and  it fails **

** please  email bug reports to [email protected], **

** 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/sda1

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

 

reiserfs_open: the reiserfs superblock cannot be found on /dev/sda1.

Failed to open the filesystem.

 

If the partition table has not been changed, and the partition is

valid  and  it really  contains  a reiserfs  partition,  then the

superblock  is corrupted and you need to run this utility with

--rebuild-sb.

 

That disk wouldn't have been your parity drive, would it?

That disk wouldn't have been your parity drive, would it?

Doh! I can't believe I did that. Could have sworn I'd checked the drive assignments and got a data drive.

 

Cheers...all fine now.