Hi,

 

I knew I was asking for trouble when I decided to change a perfectly stable system!

 

The system is a 20TB array made up of 6 x 4TB WD Red HDs. Its been working fine and stable for months.

 

The HBA was an 8 port Highpoint 2720. For further expansion, I decided to try my 24 port 3ware Inc 9650SE.

 

Unraid recognised the board and listed the discs in its own proprietary way, so Unraid naturally reported the discs as "missing"

 

Having noted the disc ID's, I was able to identify the correct order and use the "New Config" tool to remount the  discs and bring the array online.

 

Two problems;

 

1. It reports one of the array discs as "unmountable" and is offering to format the disc and rebuild. I've held off doing that so far.

 

2. Whilst I can communicate with the array through the docker, I cant access any files on the array through the normal windows file system. However, I can see the files correctly using the folder icon for each disc on the main page.

 

 

Any ideas on why one disc alone has randomly become unmountable?

 

Am I correct in assuming that if I allow the system to format the "unmountable" disc, it should then automatically rebuild the array?

 

Any ideas on the way forward gratefully received please?

 

Regards,

 

Paul

syslog.txt

You probably should have asked before doing anything. If you format a disk, there will be no way to rebuild it.

 

When you did the New Config, did it rebuild parity, or did you tell it to trust parity? If you let it rebuild parity, then perhaps you chose the wrong disk for parity and the unmountable disk is actually the parity disk and you rebuilt parity over a data disk.

 

 

 

Thanks for the reply,

 

No, I told the system to trust the parity, having only recently completed a full parity check.

 

Paul

Since the disks changed ID are you sure you select the correct one as parity?

 

You could do another new config, assign all disks as data disks and start array to confirm.

Since the disks changed ID are you sure you select the correct one as parity?

 

You could do another new config, assign all disks as data disks and start array to confirm.

You should do this immediately. If anything writes to any disk then the disk you currently have assigned as parity will be updated and if it is the wrong disk it will be too late.

Just remembered that starting the array with a data drive as parity, even if "parity is already valid" is checked", will make a few writes to it making it also unmountable, although it should be recoverable using reiserfsck.

Just remembered that starting the array with a data drive as parity, even if "parity is already valid" is checked", will make a few writes to it making it also unmountable, although it should be recoverable using reiserfsck.

In that case, perhaps he should New Config with all drives a data drives, then check filesystems on both unmountable disks. I assume it would fail on the real parity disk and hopefully succeed on the real data disk.

 

That seems safer than just checking filesystem on the single currently unmountable disk, since checking the md device would update the (possibly wrong) parity disk, and checking the sdx1 partition instead would invalidate parity anyway.

 

pm1961, how did you determine what disk to assign as parity? How certain are you that it is correct?

Hi,

 

I've successfully reverted back to my original Highpoint 2720 and all is well again.

 

I suspect that Unraid recognising the card is one one thing.... it working satisfactorily is another.

 

I have 4 cards, and its only the 2720 that works without fuss and properly.....

 

I have a 24 disc case. Anybody with a 24 port card working ok?

 

Looks like two more 2720's will be cheaper and easier, although occupying all the slots because I cant get a card working seems rather untidy.

 

It is pragmatic though...

 

Paul

I know the HighPoint 2760A works, it's used by a member.