Jump to content

Need some more help with unmountable drives / possible hardware issue again


gshipley

Recommended Posts

syslog attached:

 

If you haven't viewed my other threads, I recently upgraded my system mobo/cpu/ram and hit the virt sata add-on card problems with marvel controllers.

 

I am using a new 8x pcix add on card with the on mobo ports to eliminate the bad cards.

 

Once i got all the new hardware "working" things were fine for a day and then I had a drive failure (red x) with a ton of read errors.  So I replaced the drive.  Once parity rebuilt I had another drive failure so I replaced that one as well.  Now while parity is rebuilding on that drive (I just recently rebooted) three of the drives are showing as unmountable again. 

 

disk7 for example is one that had a million read errors during party rebuilt so I did the following:

 

reiserfsck --check /dev/md7

 

When that finished it wanted me to do it with a rebuild-tree.  So I did that.

 

It finally finished and I rebooted again which is when drive7 as well drive 8 and 10 are showing as unmountable.  Instead of continuing down the road I have been I thought it was probably time to ask for help to see if you guys see anything in the syslog that is pointing to larger problems than just my old sata card corrupting some drives.

 

Any help is appreciated before I throw this thing in the bin and move over to drive pools on windows (I kid, I kid).  All of my non-replaceable items have been backed up at this point to other machines (pictures etc) and I just have media (movies/tv etc) that is replaceable if need be.

 

Screenshot also attached. :)

 

What makes me think its still a hardware (non drive) related issue is I am seeing these in the syslog on the brand new drive4:

Aug  4 22:43:24 Hog kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 18330 does not match to the expected one 3

Aug  4 22:43:24 Hog kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 484016440. Fsck?

Aug  4 22:43:24 Hog kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [21144 22288 0x0 SD]

 

Maybe parity rebuilding is just rebuilding corrupted files or something?

 

hog-syslog-20150804-2232.zip

unraid.png.23826c2200ada766a2d9c4811061f8c7.png

Link to comment

Bumping this.  Am I asking the question wrong or wording it so it confuses people or is it just weird error that most haven't seen and can't help out with?

 

I honestly have searched for answers but if it is a common issue, I am happy reading doc if someone can point me to the right one.

 

Link to comment

Did you preclear any of these drives?

 

Might have been helpful to link to your other threads if you think they are relevant. I could just look at your post history but it wouldn't necessarily be obvious which threads you think are relevant.

 

Also, your wording is a little confusing. You talk about rebuilding parity, but that normally means actually rebuilding the parity drive. I assume what you really mean is you rebuilt a data drive using the parity array.

 

Tools - Diagnostics. Post.

Link to comment

Currently using the following:

 

http://www.newegg.com/Product/Product.aspx?Item=N82E16817139006

 

CORSAIR TX Series CMPSU-750TX 750W ATX12V v2.3 SLI Ready CrossFire Ready 80 PLUS BRONZE Certified Active PFC Compatible with New 4th Gen CPU Certified Haswell Ready

 

I also have a spare (new in box) power supply as well that is not currently being used.

 

Rosewill ATX 12V 750-Watt 80 PLUS BRONZE Certified Power Supply Hive-750

http://www.amazon.com/gp/product/B005ILWYT6?psc=1&redirect=true&ref_=oh_aui_detailpage_o06_s00

 

I really appreciate the help!

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...