Snap 4000 smart error

[Metal]

Disk Driver : Device 0x10000 SMART warning

would be the secondary (drive 1) on IDE 0 right?

02/24/2008 7:03:33 Command: info devices

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 22472 Private Mounted
Label:Private Contains system files only
Unique Id: 0x07ED0ADD5B64373B Mount: /priv Index: 12 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 245116928 Fixed

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 22232 Private Mounted
Label:Private Contains system files only
Unique Id: 0x2D49C32045A9811A Mount: /pri2 Index: 13 Order: 1
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 245116928 Fixed

Logical Device: 60000 Position: 1 RAID Size (KB): 721171624 Free (KB): 295509008 Public Mounted
Label:RAID5 Large data protection disk
Unique Id: 0x1658213F1BF5AB82 Mount: /0 Index: 0 Order: 2
Partition: 10000 Physical: 10007 R 60000 Size (KB): 243723200 Starting Blk: 174088 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 245116928 Fixed
Partition: 10008 Physical: 1000F R 60000 Size (KB): 243723200 Starting Blk: 174088 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 245116928 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 243723200 Starting Blk: 174088 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 245116928 Fixed
Partition: 10018 Physical: 1001F R 60000 Size (KB): 243723200 Starting Blk: 174088 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 245116928 Fixed

[blue68f100]

10000 is the very first drive, Drive 1, or 0 if you start with 0.

There listed in this order,
Drive 1 10000 (Slot 0),
Drive 2 10008 (Slot 1),
Drive 3 10010 (slot 2),
Drive 4 10018 (slot 3)
with 10000 and 10010 being the pri on the ide controllers.

Did it get you more confused ??????

[Metal]

Originally Posted by blue68f100

Did it get you more confused ??????

I pulled the primary slave and popped it on a HDD tester and sure enough it failed it's smart test, drive 0, 2 and 3 all passed.

[Phoenix32]

Okay, here ya go in an easier than "David confusing you" version;
(sorry David, I couldn't help picking on you, it's in my charachter)

Front bottom = drive 1 = drive slot 0 = 10000 (Primary Master or C/S)

Front top = drive 2 = drive slot 1 = 10008 (Primary Slave or C/S)

Rear bottom = drive 3 = drive slot 2 = 10010 (Secondary Master or C/S)

Rear top = drive 4 = drive slot 3 = 10018 (Secondary Slave or C/S)


Now, with that said, that is how it is SUPPOSED to be. BUT,

Revision 1 and revision 2 use Master/Slave settings rather than C/S like the revision 3 and revision 4. In the revision 1 and 2 units, the bottom drives are supposed to be the Masters and the top drives are supposed to be Slaves. However, sometimes you will find where they have been reversed (Masters on top and Slaves on the bottom), or even where only one pair has been reversed. So keep that in mind.

Everyone clear? Good...

[Phoenix32]

Originally Posted by Metal

I pulled the primary slave and popped it on a HDD tester and sure enough it failed it's smart test, drive 0, 2 and 3 all passed.

Now, I did not read (nor did you show) all the logs, but...

Given that you said smart errors on drive 10000, and then said primary slave, something is amiss here. I am going to assume you have more than one drive going bad on you (which if they are same age and use, could very well be).

Pull that primary master, AFTER THE RAID 5 REBUILD IS COMPLETE from replacing the primary slave, and test it. I got a sneaking suspicion.

[Metal]

Originally Posted by Phoenix32

Now, I did not read (nor did you show) all the logs, but...

Given that you said smart errors on drive 10000, and then said primary slave, something is amiss here. I am going to assume you have more than one drive going bad on you (which if they are same age and use, could very well be).

Pull that primary master, AFTER THE RAID 5 REBUILD IS COMPLETE from replacing the primary slave, and test it. I got a sneaking suspicion.

I agree.
Also the drives on IDE channel 0 were jumperd primary and slave. (the drive on the bottom was the drive jumperd slave)
The drives on IDE channel 2 were set CS (for the master) and the second was jumperd slave.
This is a rev 1 MB

[Phoenix32]

Originally Posted by Metal

the drives on IDE channel 0 were jumperd primary and slave. (the drive on the bottom was the drive jumperd slave)
The drives on IDE channel 2 were set CS (for the master) and the second was jumperd slave.

Yup, someone has been messing with it previously.

Look at the Model Number on the sticker at the back of the unit. The -00X tells you which revision it is.

[Metal]

Originally Posted by Phoenix32

Yup, someone has been messing with it previously.

Look at the Model Number on the sticker at the back of the unit. The -00X tells you which revision it is.

Hi
According to the sticker it's an -002.
I have an -004 I've had sitting around in case this one takes a dump and needed parts but now that I think about it wasn't there a mod you were supposed to do on the older 4000 units?

[Phoenix32]

The mod is just to change the IDE cables from a -001 or -002 revision into C/S cables. I don't remember which message thread it was anymore, but I did post some info to do it a while back. But in your case, it is easy. Just look at the cables from your -004 unit (look for the cut cable lead) and then cut your -002 cables to match them. That's it. Just remember, the drives will need to be C/S then. I have no idea for sure how safe the data will be when doing this. Back the data up first.

[Metal]

Merry Christmas Everybody!
I thought I'd Bring this thread back from the dead.
I dusted off the old dead snap about and hour ago, popped in a 320GB drive, (I didn't have a similar 250GB handy) swapped in the CS cables from the -004 as well as the power supply (due to the -002's power supply having bulged capacitors) set all 4 drives to CS and the old 4000 is rebuilding it's raid as I type. As I recall the 4000 series didn't like drives larger than 250GB so I'll keep and eye on things for a bit. I've long ago backed up all the data on this snap so this whole repair and rebuild was more or less an academic endeavor to kill some time on a lazy holiday evening
On a side note:
I turned off my Dell 745n, my two 4200's and my HP 1500s to keep things quiet around the house today with our company here and I have to say I'm enjoying the peace and quiet of this 4000. I forgot how nice it was to have a relatively quiet NAS