Unformatted disk

I already checked the forums here and noticed this is pretty much a recurring problem, but didn't really find an answer.

The problem is that I get an unformatted disk and and I executed reiserfsck --rebuild-sb, than it tells me to run with --check and the check tells me to rerun --rebuild-sb. So I'm stuck in a loop.

Any advice would be really appreciated.

root@Trauma-unRaid:/# reiserfsck --rebuild-sb /dev/md1

reiserfsck 3.6.21 (2009 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 check superblock and rebuild it if needed

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/md1.

 

what the version of ReiserFS do you use[1-4]

        (1)  3.6.x

        (2) >=3.5.9 (introduced in the middle of 1999) (if you use linux 2.2, choose this one)

        (3) < 3.5.9 converted to new format (don't choose if unsure)

        (4) < 3.5.9 (this is very old format, don't choose if unsure)

        (X)  exit

1

 

Enter block size [4096]:

 

 

No journal device was specified. (If journal is not available, re-run with --no-journal-available option specified).

Is journal default? (y/n)[y]:

 

Did you use resizer(y/n)[n]:

rebuild-sb: no uuid found, a new uuid was generated (8e98e22e-86fe-45a2-943d-2d2fb5f57725)

 

rebuild-sb: You either have a corrupted journal or have just changed

the start of the partition with some partition table editor. If you are

sure that the start of the partition is ok, rebuild the journal header.

Do you want to rebuild the journal header? (y/n)[n]: y

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

Count of blocks on the device: 488378624

Number of bitmaps: 14905

Blocksize: 4096

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

Root block: 0

Filesystem is NOT clean

Tree height: 0

Hash function used to sort names: not set

Objectid map size 0, max 972

Journal parameters:

        Device [0x0]

        Magic [0x0]

        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: 0x1:

        some corruptions exist.

sb_version: 2

inode generation number: 0

UUID: 8e98e22e-86fe-45a2-943d-2d2fb5f57725

LABEL:

Set flags in SB:

Mount count: 1

Maximum mount count: 30

Last fsck run: Sat Apr  7 02:22:35 2012

Check interval in days: 180

Is this ok ? (y/n)[n]: y

The fs may still be unconsistent. Run reiserfsck --check.

 

root@Trauma-unRaid:/# reiserfsck --check /dev/md1

reiserfsck 3.6.21 (2009 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/md1

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/md1.

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.

 

If you cannot get to the disk via the /dev/mdX device, you will probably need to get to it through its physical disk device.

The only issue is, doing it that way will invalidate parity. (or rather, parity will not be updated with your fixes)

You can try running reiserfsck --check on the /dev/sdX1 partition of the disk affiliated with the disk1 assignment on your server.

Note the "1" at the end of the device name, as the file system is on the first partition.

If it can find a superblock, great.  If not, there might be other issues.  DO NOT rebuild the superblock unless you know for sure the partition points to the correct start sector on the disk.

Joe L.

I did that, and it returned clean.

root@Trauma-unRaid:/# reiserfsck --check /dev/sde1

reiserfsck 3.6.21 (2009 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/sde1

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 Sat Apr  7 16:08:30 2012

###########

Replaying journal: No transactions found

Checking internal tree.. finished

Comparing bitmaps..finished

Checking Semantic tree:

finished

No corruptions found

There are on the filesystem:

        Leaves 1

        Internal nodes 0

        Directories 2

        Other files 0

        Data block pointers 0 (0 of them are zero)

        Safe links 0

###########

reiserfsck finished at Sat Apr  7 16:10:27 2012

###########

But I still seem unable to format the disk.

(The weird thing is, I've tried it with another new disk, which I also precleared, and I recieve the same thing)

Otherwise, when I redo the check on /dev/md1 it still says superblock cannot be found and I remain in the loop where it says to rebuild-sb and afterwards do the check where it tells me to run the rebuild-sb again.

Any advise would be appreciated.

post a system log.

http://pastebin.com/xRkqZ2EH

Here's a pastebin from my log.

I hope this helps..

any ideas?

It's because I have the same problem with 2 of my new 2TB disks.

The only thing I did, was preclear the disks before adding them to the array.

Just find it pretty weird that I can't format them,

since it's the build of a new FS on the disks.

Still, any advice/suggestions would be welcome.

I'm willing to test a lot, as long as it doesn't involve clearing my 6TB of data.

bump

According to the syslog disk1 is sdf.

it advised me to do a rebuild-tree, so that's now already running for 2 days and still ain't finished.

Is that normal?

it advised me to do a rebuild-tree, so that's now already running for 2 days and still ain't finished.

Is that normal?

It's a 2TB disk.

And it said "488355509 will be read"

and it still has 469383675 blocks left

and I see that number dropping

(and we're at day 3 now)

just go to the computer that read the floppy disc files. off load the files. then format it.