No, the disks are formatted ReiserFS, so you will need some drivers and/or a Linux distro to be able to read them.  Do some google searching for ReiserFS on Windows and see what you can come up with.

No, the disks are formatted ReiserFS, so you will need some drivers and/or a Linux distro to be able to read them.  Do some google searching for ReiserFS on Windows and see what you can come up with.

 

I found a program for it, most are pretty old, yareg, it shows you the file structure then you have to copy over what you want, unfortunately you can't actually use the files until you copy them over.  It seems like that file system is pretty old.  so i can manage with that for a while though, i don't want to copy everything over, just some core stuff, i'd like everything but too much of a pita.

 

I have a question though, with getting a new mobo, is that going to be a problem for keeping this array intact?  i had accidentally switched two of the sata ports on this mobo once, doing something, and it wouldn't start up, there was some error message, can't remember now what, but it made me think that it could be an issue.

 

thanks,

rlr

As long as you know which drive is the parity drive there should not be a problem with getting the array back up and running on a new motherboard

As long as you know which drive is the parity drive there should not be a problem with getting the array back up and running on a new motherboard

 

Hey,

 

so it doesn't matter what ports the drives are plugged into?

 

the prob with this mobo is it could just as well be the cpu, it's an amd so mem controller is on chip.  however those cpu's are not cheap right now, i saw one of the x2's, can't remember which one, but it was 200 on ebay, i could buy a way better new cpu for the same money, or much less actually, then if i find it's the mobo, i'm stuck buying one of those too, which is socket 939, not sure on the availability of those but i think it's limited, so i figured i'd just wait and do a nice, new, simple rebuild, i want something i can count on more.  for now i'm moving everything back to windows, i lost one whole disk, pretty bummed about that, but it's replaceable without too much hassle.

 

so, thanks though man,

and thanks Joe and everybody,

i'll catch up with you in a while,

rlr

As long as you know which drive is the parity drive there should not be a problem with getting the array back up and running on a new motherboard

 

Hey,

 

so it doesn't matter what ports the drives are plugged into?

 

the prob with this mobo is it could just as well be the cpu, it's an amd so mem controller is on chip.  however those cpu's are not cheap right now, i saw one of the x2's, can't remember which one, but it was 200 on ebay, i could buy a way better new cpu for the same money, or much less actually, then if i find it's the mobo, i'm stuck buying one of those too, which is socket 939, not sure on the availability of those but i think it's limited, so i figured i'd just wait and do a nice, new, simple rebuild, i want something i can count on more.  for now i'm moving everything back to windows, i lost one whole disk, pretty bummed about that, but it's replaceable without too much hassle.

 

so, thanks though man,

and thanks Joe and everybody,

i'll catch up with you in a while,

rlr

 

sorry to hear about your luck.

 

Yup, the ports that the drives are plugged into does not matter to unRAID.  The only thing that really does is that you get the parity drive assigned back to the right slot in the devices page.  All other data disks can be assigned anywhere and the array will be fine.  Once you get it all set back up it would probably not hurt to hit the restore button, especially if you know the data disks are not in there original spots.  Parity will be calculated based on the new drive positions so you will be without parity protection until that is complete.

Once you get it all set back up it would probably not hurt to hit the restore button, especially if you know the data disks are not in there original spots.  Parity will be calculated based on the new drive positions so you will be without parity protection until that is complete.

The user already stated he has not calculated parity ever... because of the lock-ups.

 

There is absolutely NO need to press "restore" unless the array complains about too many wrong or missing disks when attempting to start.

 

Just assign your disks to the correct slots in the array, making sure the parity disk is in the correct assignment and press "Start".

 

Parity will be initially calculated and stored on the parity disk.

 

Then... to be certain it can be read back properly, once the initial parity calc is completed and the indicator next to the parity disk is "green" press the "Parity Chack" button for a full verification.  Only then will you know a disk can be re-constructed if a failure occurs.

 

Thereafter, a monthly press of the "Check" button will ensure your hardware is all still working.

 

Joe L.

Once you get it all set back up it would probably not hurt to hit the restore button, especially if you know the data disks are not in there original spots.  Parity will be calculated based on the new drive positions so you will be without parity protection until that is complete.

The user already stated he has not calculated parity ever... because of the lock-ups.

 

There is absolutely NO need to press "restore" unless the array complains about too many wrong or missing disks when attempting to start.

 

Just assign your disks to the correct slots in the array, making sure the parity disk is in the correct assignment and press "Start".

 

Parity will be initially calculated and stored on the parity disk.

 

Then... to be certain it can be read back properly, once the initial parity calc is completed and the indicator next to the parity disk is "green" press the "Parity Chack" button for a full verification.   Only then will you know a disk can be re-constructed if a failure occurs.

 

Thereafter, a monthly press of the "Check" button will ensure your hardware is all still working.

 

Joe L.

 

I missed the part about never having calculated parity ever.

kyle has not had enough cups of coffee yet this morning

Just for completeness, your syslog showed that your parity drive rather suddenly lost contact, about 3 hours and 20 minutes into the parity sync, and within a minute, the kernel gave up trying to recover it, and disabled it.  All of the errors you see following that are because the drive had been disabled.  Unfortunately, there are no clues I can see as to WHY the drive abruptly stopped communicating.  I don't think there is any connection to your memory problems.  The fact that there are 1295 potentially bad sectors seems to rule out something as simple as a cable having vibrated loose.  Discovering and testing bad sectors does take some time, and perhaps the drive was hanging while working on them, but it really should have responded in some fashion.  The kernel got no response at all for the 60 seconds that it tried to contact it.  Almost an hour later, it does appear to regain contact with it, but that is way too late.