So, today I finished preclearing another drive so I can remove the Samsung F4 out of my array.  I followed the instructions to stop the array, remove the F4 from the array, re-started the array to remove the F4.  I then stopped the array and took my server apart.

 

I then decided to have all of my seagates together in one of the 3x4 cages.  However, I forgot that my 4th data drive was set to a WD drive, and when I went ahead and assigned the array according to the order I wanted it to be it gave stated that two of my drives were unformatted.

 

Right now, I am taking my server apart and setting the WD drive in the 4th spot of the 3x4 drive cages and re-starting the array and see if this fixes the issue.

 

If not what do I need to do to restart the array without reformatting any of my drives since they've got data in them already.

syslog-2012-04-06.txt

So, today I finished preclearing another drive so I can remove the Samsung F4 out of my array.  I followed the instructions to stop the array, remove the F4 from the array, re-started the array to remove the F4.  I then stopped the array and took my server apart.

 

I then decided to have all of my seagates together in one of the 3x4 cages.  However, I forgot that my 4th data drive was set to a WD drive, and when I went ahead and assigned the array according to the order I wanted it to be it gave stated that two of my drives were unformatted.

 

Right now, I am taking my server apart and setting the WD drive in the 4th spot of the 3x4 drive cages and re-starting the array and see if this fixes the issue.

 

If not what do I need to do to restart the array without reformatting any of my drives since they've got data in them already.

Don't panic, and DO NOT press any format buttons.

 

4.7 unRAID has been know to incorrectly reset the MBR of disks.  It is easy to fix, but you can make things a lot worse if you attempt to re-format.

 

Step 1.  As with ALL requests for help, post a system log.  (oh yes, put the disks back as they were first)  Do not worry about un-formatted just yet.  Not until somebody can help you diagnose what is keeping the disks from being mounted. (unRAID thinks any disk it cannot mount is un-formatted)

So, today I finished preclearing another drive so I can remove the Samsung F4 out of my array.  I followed the instructions to stop the array, remove the F4 from the array, re-started the array to remove the F4.  I then stopped the array and took my server apart.

 

I then decided to have all of my seagates together in one of the 3x4 cages.  However, I forgot that my 4th data drive was set to a WD drive, and when I went ahead and assigned the array according to the order I wanted it to be it gave stated that two of my drives were unformatted.

 

Right now, I am taking my server apart and setting the WD drive in the 4th spot of the 3x4 drive cages and re-starting the array and see if this fixes the issue.

 

If not what do I need to do to restart the array without reformatting any of my drives since they've got data in them already.

Don't panic, and DO NOT press any format buttons.

 

4.7 unRAID has been know to incorrectly reset the MBR of disks.  It is easy to fix, but you can make things a lot worse if you attempt to re-format.

 

Step 1.  As with ALL requests for help, post a system log.  (oh yes, put the disks back as they were first)  Do not worry about un-formatted just yet.  Not until somebody can help you diagnose what is keeping the disks from being mounted. (unRAID thinks any disk it cannot mount is un-formatted)

 

Just posted it!

I was able to bring it back up, and now it's conducting a parity check, which I've been looking at system log on the web gui, and it's coming up with a lot of errors.

 

I checked my Media folder, and it is missing about 45 HD movies.  We'll see what happens after the parity check is finalized.  I hope the errors won't damage or corrupt the rest of my media.  It's taken me over 3 months to finish ripping all of my blu-rays, DVD's and TV Shows.

I am wondering if I can re-install the Samsung F4 in the parity, and may be that drive has more of my media in it, and I might be able to include it?

 

Is this possible?

Any drive installed as parity will be overwritten with parity bits. The parity drive contains no data.

I am wondering if I can re-install the Samsung F4 in the parity, and may be that drive has more of my media in it, and I might be able to include it?

 

Is this possible?

 

Im sorry.  The F4 was a data drive not a parity drive.  I was wondering if any of the F4 data could be added back.

System log after parity check.  I see a lot of error, but it says parity is valid.  What should I do?

It won't let me attach anything.

After Googling how to find the manufacturing date for my Samsung F4, I found out THAT I DIDN'T NEED TO DO THE FW UPDATE.  So, I lost 41 movies for nothing.

 

I'M SO FREAKING PISSED! AND LAUGHING AT THE SAME TIME!!!!

 

Time to go buy some Norco SS500 or Supermicro.  It was a PIA to take off the drive 4 times in a row.

If you did not move the data off of it, wipe, format, preclear or make it a parity drive... the the F4 should still have your data on it. simply removing it from an array does not make it loose the data on its own.

 

you should be able to pop that drive into the server as a drive OUTSIDE the arrray and see whats on it.

Again,  do not try to add it to the array with the webgui. using the command line or SNAP, you should be able to see the data. I belive midnight commander should work too.

 

another option that "should work" is to put that drive into another "virgin" unconfigured unraid box (with a new flash drive, the free version is ok) and make it a data disk. DO NOT format if it asks you to! just stop and seek help. it should just have the data on it. that you can copy to your main server.

I completed the parity check, and at the home screen it said 0 parity error, but after looking at the system log is has numerous error, and I was wondering if any of you know what they mean? and how do I fix them?  Thank you.

 

I replaced all he SATA cables, with monoprice SATA locking cables a couple of days ago.  Would this have anything to do with it?

Can't tell without a new syslog. I wish my telepathic powers were better.

Can't tell without a new syslog. I wish my telepathic powers were better.

 

I tried attaching a system log but it said the file is too large.  I didnt have time to try to host it.

Here is the link for my system log.  It is bigger than 192kb so I had to host it.  I am very concern with the errors even though I don't know what they mean.  I hope someone can help me with this.

 

http://www.freefilehosting.net/syslog-2012-04-07

Here is the link for my system log.  It is bigger than 192kb so I had to host it.  I am very concern with the errors even though I don't know what they mean.  I hope someone can help me with this.

 

http://www.freefilehosting.net/syslog-2012-04-07

 

You could have zipped the file file if it is too large.

Please zip the file next time.

 

 

At least disk3 has a file system error.

See here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

These errors are all the result of file-system-corruption on disk3.

 

In fact, to prevent further corruption, the operating system has made the disk read-only.

 

The fix is not difficult, and the instructions are in the wiki here:

http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems

 

Apr  7 10:50:15 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 3

Apr  7 10:50:15 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 436755960. Fsck?

Apr  7 10:50:15 Tower kernel: REISERFS (device md3): Remounting filesystem read-only

Apr  7 10:50:15 Tower kernel: REISERFS error (device md3): vs-2140 finish_unfinished: search_by_key returned -2

Apr  7 10:50:16 Tower emhttp: shcmd (18): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Apr  7 10:50:16 Tower emhttp: _shcmd: shcmd (18): exit status: 1

Apr  7 10:50:16 Tower emhttp: shcmd (19): cp /etc/exports- /etc/exports

Apr  7 10:50:16 Tower emhttp: shcmd (20): mkdir /mnt/user

Apr  7 10:50:16 Tower emhttp: shcmd (21): /usr/local/sbin/shfs /mnt/user  -o noatime,big_writes,allow_other,default_permissions

Apr  7 10:50:16 Tower emhttp: shcmd (22): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root

Apr  7 10:50:16 Tower emhttp: shcmd (23): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root

Apr  7 10:50:16 Tower emhttp: shcmd (24): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root

Apr  7 10:50:16 Tower emhttp: shcmd (25): crontab /var/spool/cron/crontabs/root

Apr  7 10:50:17 Tower emhttp: shcmd (26): echo \"/mnt/user/Media\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=100' '*(rw)' >>/etc/exports

Apr  7 10:50:17 Tower emhttp: shcmd (27): killall -HUP smbd

Apr  7 10:50:17 Tower emhttp: shcmd (28): /etc/rc.d/rc.nfsd restart | logger

Apr  7 10:50:19 Tower logger: Starting NFS server daemons:

Apr  7 10:50:19 Tower logger:  /usr/sbin/exportfs -r

Apr  7 10:50:19 Tower logger:  /usr/sbin/rpc.nfsd 8

Apr  7 10:50:19 Tower logger:  /usr/sbin/rpc.mountd

Apr  7 10:51:46 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2

Apr  7 10:51:46 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 33454. Fsck?

Apr  7 10:51:46 Tower kernel: REISERFS error (device md3): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4 143 0x0 SD]

Apr  7 10:51:46 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2

Apr  7 10:51:46 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 33454. Fsck?

Apr  7 10:51:46 Tower kernel: REISERFS error (device md3): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4 143 0x0 SD]

Apr  7 10:51:46 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2

Apr  7 10:51:46 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 33454. Fsck?

Apr  7 10:51:46 Tower kernel: REISERFS error (device md3): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4 143 0x0 SD]

Apr  7 10:51:48 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2

Apr  7 10:51:48 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 326703116. Fsck?

Apr  7 10:51:48 Tower kernel: REISERFS error (device md3): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [5 18 0x0 SD]

Apr  7 10:51:48 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2

JOE L.

 

Thanks.  You know drive 3 used to be my Samsung F4, which I took out from the array.  It is now back in the array in drive 5 spot, and it has the missing media.  I am not at home right now but when i get home Ill run the directions from the wiki.  Thanks for your help.

I follow the wiki for the reiserfsck disk 3, and it at the end it states: "3 found corruptions can be fixed only when running with --rebuild-tree"

 

However, it states on the wiki to only run this as last resort.  So, I am posting here to ask you if I should do this or not?  I've manually checked disk 3, and there is only 1 movie in there, which I don't care about since I've got an extra copy in disk 5.  I was trying to transfer the movies from disk 5 to my main Media Shares, but it says that I need permission from tower/root.  I believe this is due to the drive or drives being set to read only due to the errors.

 

All the other drives have the movies that I need.  Drive 3 was a new drive that was supposed to replace the Samsung F4 drive, which is now assign to drive 5.  So, can I just delete everything from the current drive 3, make it read/write, transfer the files from drive 5 to the main Media share folder, re-run parity and be done with it?  Thanks for all your help.

I follow the wiki for the reiserfsck disk 3, and it at the end it states: "3 found corruptions can be fixed only when running with --rebuild-tree"

 

However, it states on the wiki to only run this as last resort.  So, I am posting here to ask you if I should do this or not?  I've manually checked disk 3, and there is only 1 movie in there, which I don't care about since I've got an extra copy in disk 5.  I was trying to transfer the movies from disk 5 to my main Media Shares, but it says that I need permission from tower/root.  I believe this is due to the drive or drives being set to read only due to the errors.

 

All the other drives have the movies that I need.  Drive 3 was a new drive that was supposed to replace the Samsung F4 drive, which is now assign to drive 5.  So, can I just delete everything from the current drive 3, make it read/write, transfer the files from drive 5 to the main Media share folder, re-run parity and be done with it?  Thanks for all your help.

you must either fix the file system, or completely reformat the disk.

 

Give the --rebuild-tree a chance.  You have nothing to lose if there are no files on the disk you need.

Ok ill run that script when i get home im the morning.  I just wanted to double check with you befote i proceed.

 

Couple more questions

1. If rebult-tree work, will i be able to start transferring files?  In other words will this make my array read/write?

 

2. If rebuit-doesnt work, if i preclear the drive and added the drive back to my array again will this fix the read/write issue?

 

3. Should i move drive 5 to drive 3 spot since drive 5 used to be drive 3? Will this accomplish anything or it doesn't matter?

 

4. After the --rebuilt-tree is complete, do I just mount the drives again and run a parity check? or should I run reiserfsck on disk 3 again?

 

Sorry for all these questions, but my wife and my kids wanted to see a couple of movies last night, and I forgot to tell them that the server isn't working yet.  So, they keep asking me when is the server going to be working again since they miss the Zappiti Jukebox.

I just got home from work.  Freaking tired.  I am running the --rebuild-tree right now.  I am hoping this fixes the drive, and I am able to get my read/write set up back again.  It's weird, for some reason or another, I was able to transfer about 30% of the movies from drive 5 to the Media share folder, but once it got to "The Incredible Hulk," it said that I needed permission from tower/root to proceed.

--rebuilt-tree was complete after almost 7 hours.  I don't know how to copy the screen information, but this is what it says:

Flushing..finished

Files found: 1

Directories found: 6

Names pointing to nowhere (removed): 40

Pass 3a (looking for lost dir/files):

###### Pass 3a (lost+found pass) ######

Looking for lost directories:

Flushing..finishede 0, 0 /sec

Pass 4 - finished          done 0, 0 /sec

Flushing..finished

Syncing..finished

#######

reiserfsck finished at Tue Apr 10 14:00:31 2012

#######

root@tower:~#

 

Is this good or bad?

Run with --check again.