Disk appear unformatted

[josywong]

I had 4.7 running but got transmission error.

and formatted my usb.

 

after i boot up from clean 4.7, it appears tat my 2nd disk is unformatted.

is there anyway i can get it back?

all my other disks show green.

 

and the files showed only from 1 disk, i thought it shud shw 2nd disk since my parity is on the work?

syslog.txt

[dgaschk]

Are you sure that parity was not assigned as disk2 and disk2 as parity?

[josywong]

Are you sure that parity was not assigned as disk2 and disk2 as parity?

 

I'm very sure.

I had ss, parity check anf USB back up before I format my usb.

[dgaschk]

I had ss, parity check anf USB back up before I format my usb.

What is "ss"?

 

Did you do clean install or use the backup?

 

EDIT: OK, ss is screenshot.

 

You could rebuild disk2 but since its contents are also missing so there is something else wrong as well. That's why I thought they might be switched. I hope that you have not written anything to the array.

 

Stop the array and try switching them. Don't start the array. Just see what happens to the colors.

[josywong]

I had ss, parity check anf USB back up before I format my usb.

What is "ss"?

 

Did you do clean install or use the backup?

 

EDIT: OK, ss is screenshot.

 

You could rebuild disk2 but since its contents are also missing so there is something else wrong as well. That's why I thought they might be switched. I hope that you have not written anything to the array.

 

Stop the array and try switching them. Don't start the array. Just see what happens to the colors.

 

i remember the 1s time i boot it up, parity was in red.

had parity sync, but disk2 stil unformatted and untouched since i boot up.

 

its building data up, weird thing is unformatted drive "write" increasing while parity and disk1 "reads" keep increasing.

shud i stop it and switch? the format tick box stil available...  data built on unformatted disk?

[dgaschk]

Yes stop it. Parity can not be generated with a red data disk in place. The array should never have been started without all drives green. Are you rebuilding disk2 or generating parity?

[josywong]

i had it stopped.

 

i think i had lost all the datas. i did parity sync when they were in red last nite.

[dgaschk]

There may be a way to recover the data on disk2 using reiserfsk. I don't know the exact commands though. Search the forum and wiki for reiserfsk. Someone who knows more than me will hopefully post the command here.

[josywong]

thanks for the info.

 

after

 

reiserfsck --check /dev/md2

 

 

Tower login: root

Password:

Linux 2.6.32.9-unRAID.

root@Tower:~# cd

root@Tower:~# samba stop

root@Tower:~# umount /dev/md2

umount: /dev/md2: not mounted

root@Tower:~# reiserfsck --check /dev/md2

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/md2

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

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.

 

root@Tower:~#

[lionelhutz]

i remember the 1s time i boot it up, parity was in red.

had parity sync, but disk2 stil unformatted and untouched since i boot up.

 

It sounds like you just swapped disk2 and the parity and you've now overwritten your disk2 with new parity information.

 

unRAID will put the proper partition on an unrecognized disk but you have to press the format button. Once the partition is created you can use the disk as part of the array as far as creating parity or rebuilding a disk from parity. You just can't put anything on it until you format it so it has a valid filesystem.

 

Check this out for help with reiserfsck

 

http://linux.about.com/library/cmd/blcmdl8_reiserfsck.htm

 

You can try the --rebuild-sb option and if that works try the plain check again and it might recommend the --fix-fixable or --rebuild-tree options. I think the --rebuild-sb option asks a number of questions and you'll have to search here for the proper responses because the responses have been posted before.

 

However, since I'd bet money that disk2 was really the parity drive I'm also betting by extension that there is no data on disk2 and you will not recover anything.

 

Since you say you had the parity sync and now you say "its building data up, weird thing is unformatted drive "write" increasing while parity and disk1 "reads" keep increasing." It sounds like you are now attempting to rebuild disk2 from parity so you have destroyed both the original disk2 and the original parity data. There is now no way to recover because you have overwritten 2 disks.

 

Peter

 

 

[josywong]

 

Tower login: root

Password:

Linux 2.6.32.9-unRAID.

root@Tower:~# cd

root@Tower:~# samba stop

root@Tower:~# unmount /dev/md2

-bash: unmount: command not found

root@Tower:~# reiserfsck --fix-fixable /dev/md2

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 consistency of the filesystem on /dev/md2

and will fix what can be fixed without --rebuild-tree

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

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.

 

root@Tower:~# reiserfsck --rebuild-sb /dev/md2

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

 

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, ch

oose 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]:

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]: y

 

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

rebuild-sb: no uuid found, a new uuid was generated (3581f43b-3d16-4c03-89f8-2da

0bd718e0b)

 

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 0x902 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: 3581f43b-3d16-4c03-89f8-2da0bd718e0b

LABEL:

Set flags in SB:

Mount count: 1

Maximum mount count: 30

Last fsck run: Wed Apr  6 14:19:49 2011

Check interval in days: 180

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

[josywong]

i remember the 1s time i boot it up, parity was in red.

had parity sync, but disk2 stil unformatted and untouched since i boot up.

 

It sounds like you just swapped disk2 and the parity and you've now overwritten your disk2 with new parity information.

 

unRAID will put the proper partition on an unrecognized disk but you have to press the format button. Once the partition is created you can use the disk as part of the array as far as creating parity or rebuilding a disk from parity. You just can't put anything on it until you format it so it has a valid filesystem.

 

Check this out for help with reiserfsck

 

http://linux.about.com/library/cmd/blcmdl8_reiserfsck.htm

 

You can try the --rebuild-sb option and if that works try the plain check again and it might recommend the --fix-fixable or --rebuild-tree options. I think the --rebuild-sb option asks a number of questions and you'll have to search here for the proper responses because the responses have been posted before.

 

However, since I'd bet money that disk2 was really the parity drive I'm also betting by extension that there is no data on disk2 and you will not recover anything.

 

Peter

 

 

 

i've checked with the reiserfsck. read all posts in this forum.

i always did some research before i start doing things i'm nt really sure.

i am very sure tat its not parity on disk2.

i can stil remember which disk from where, when i bought it, and hw i arrange them physically.

 

i'll do the reiserfsck --rebuild-sb anyway

[lionelhutz]

Ya, you've got to get a superblock on the disk so that the disk has a reiserfs before reiserfsck can attempt to fix or rebuild the disk.

 

Peter

[dgaschk]

This may help recover some files: http://lime-technology.com/forum/index.php?topic=619.msg3972#msg3972