burtjr

I will add that in your signature you have 5 2TB drives and in your current screen shot there are 5 2TB drives. I think the question garycase is getting at is are you sure this is a 1TB drive vise a 2TB drive as indicated? Although this doesn't answer your question of the reported negative space. Attach a copy of your system log to help isolate problem if the drive is actually reporting incorrectly.

Please read thread title and stay on topic please. Thank you. "Posted from ASUS laptop computer via google chrome"

It now says sold out on product page.

Disable simplefeatures and see if the problem goes away. If it does then you will need to decide how important it is to you.

The first question to answer is what did you install with unraid? No one can truly help you unless you give the details. A syslog would help the assistance also.

We are making a lot of assumptions based on a system that he will be selling in the future. Tom has never mentioned adding in any of these into 5 final. We are bitching just to bitch. If you don't like the product move to something else. As soon as 5 final is out we will be bitching about 5.1 and 6. It will never stop. Be happy with what you have or move on to something that will work for you.

Your parity drive is reporting HPA Apr 13 20:11:27 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 13 20:11:27 NAS kernel: ata4.00: HPA detected: current 5860531055, native 5860533168 Apr 13 20:11:27 NAS kernel: ata4.00: ATA-9: WDC WD30EZRX-00DC0B0, 80.00A80, max UDMA/133 Apr 13 20:11:27 NAS kernel: ata4.00: 5860531055 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Apr 13 20:11:27 NAS kernel: ata4.00: configured for UDMA/133 Apr 13 20:11:27 NAS kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD30EZRX-00D 80.0 PQ: 0 ANSI: 5 Apr 13 20:11:27 NAS kernel: sd 3:0:0:0: [sde] 5860531055 512-byte logical blocks: (3.00 TB/2.72 TiB) Apr 13 20:11:27 NAS kernel: sd 3:0:0:0: Attached scsi generic sg4 type 0 Apr 13 20:11:27 NAS kernel: sd 3:0:0:0: [sde] 4096-byte physical blocks Apr 13 20:11:27 NAS kernel: sd 3:0:0:0: [sde] Write Protect is off Apr 13 20:11:27 NAS kernel: sd 3:0:0:0: [sde] Mode Sense: 00 3a 00 00 Apr 13 20:11:27 NAS kernel: sd 3:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 13 20:11:27 NAS kernel: sde: sde1

I haven't looked at the smart report yet, but with those numbers on those attributes I'm guessing it's a Seagate drive. If it is those numbers don't mean anything. I have a couple Seagate drives and those are extremely high compared to my others. From what I have read companies have different ways and tolerances on when these log the errors. Edit - Just looked at the smart report and is indeed a Seagate drive. When I get a chance I'll look at my Seagate smart reports and see if they follow. I know the two you posted follow mine, but I am unsure of this one (195 Hardware_ECC_Recovered 0x001a 080 069 000 Old_age Always - 242506871). Perhaps somone will chime in to verify that this is also ok before I get time to look at mine.

Dead horse dead horse.

I was wondering how long this would take to turn into a bitch session. It was longer than I anticipated. Way to hold the constructive criticism in.

I will add that this (May 4 22:13:12 storageserver kernel: sas: ata7: end_device-0:0: dev error handler (Errors)) is just information of which error handler is being used an no cause for concern.

You may need to clear the cache, but normally if you installed it correctly it should show up instead of the default unraid web gui.

May 1 23:07:10 Hal-1 kernel: sde: sde1 May 1 23:07:10 Hal-1 kernel: sd 5:0:0:0: [sde] Attached SCSI disk May 1 23:07:10 Hal-1 kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) May 1 23:07:10 Hal-1 kernel: ata7.00: ATA-8: , 50.0AB50, max UDMA/133 May 1 23:07:10 Hal-1 kernel: ata7.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA May 1 23:07:10 Hal-1 kernel: ata7.00: configured for UDMA/133 May 1 23:07:10 Hal-1 kernel: scsi 6:0:0:0: Direct-Access ATA 50.0 PQ: 0 ANSI: 5 May 1 23:07:10 Hal-1 kernel: sd 6:0:0:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) May 1 23:07:10 Hal-1 kernel: sd 6:0:0:0: [sdf] Write Protect is off May 1 23:07:10 Hal-1 kernel: sd 6:0:0:0: [sdf] Mode Sense: 00 3a 00 00 May 1 23:07:10 Hal-1 kernel: sd 6:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Add a syslog also, so we can help you figure out why your having probems.

Post a smart report for the drive

Post a smart report of sdg

This is the main reason I went with the Kingston Flash Card Reader MobileLite G2 USB 2.0 Multi-card Reader, when the card goes I throw in my backup SD card and I have minimal down time. The GUID is with the reader and not the card.

Check for hidden files

I didn't see the 180 degree rotation you were talking about in the article, but by the looks of the cage that would put the sata and power connectors on the bottom and make installation a bit easier, also the cables would not block the air flow from the bays in anyway. Just my thoughts.

I believe these are 7200 rpm drives. Good deal for today's prices as they normally go for $199 usd.

OpenIndiana FTW. Unfortunately I tried OpenIndiana and I get a blue screen when it starts the install gui. Have not figured out how to get past this and from the looks of they're install instructions they haven't either. I have tried both and Intel based and amd based build with on board and Ati graphics. My guess is it just doesn't like my choice of motherboard vendor which are both Gigabyte. Appreciate the recommendation though

ATA:7 = sde sas: DOING DISCOVERY on port 0, pid:841 Apr 13 10:12:58 tower kernel: drivers/scsi/mvsas/mv_sas.c 1388:found dev[0:5] is gone. Apr 13 10:12:58 tower kernel: sas: sas_ata_phy_reset: Found ATA device. Apr 13 10:12:58 tower kernel: ata7.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 Apr 13 10:12:58 tower kernel: ata7.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) Apr 13 10:12:58 tower kernel: ata7.00: configured for UDMA/133 Apr 13 10:12:58 tower kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5 Apr 13 10:12:58 tower kernel: sas: DONE DISCOVERY on port 0, pid:841, result:0 Apr 13 10:12:58 tower kernel: sd 0:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Apr 13 10:12:58 tower kernel: sd 0:0:0:0: [sde] Write Protect is off Apr 13 10:12:58 tower kernel: sd 0:0:0:0: [sde] Mode Sense: 00 3a 00 00 Apr 13 10:12:58 tower kernel: sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata:8 = sdf sas: DOING DISCOVERY on port 1, pid:841 Apr 13 10:12:58 tower kernel: drivers/scsi/mvsas/mv_sas.c 1388:found dev[1:5] is gone. Apr 13 10:12:58 tower kernel: sas: sas_ata_phy_reset: Found ATA device. Apr 13 10:12:58 tower kernel: ata8.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 Apr 13 10:12:58 tower kernel: ata8.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) Apr 13 10:12:58 tower kernel: ata8.00: configured for UDMA/133 Apr 13 10:12:58 tower kernel: scsi 0:0:1:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5 Apr 13 10:12:58 tower kernel: sas: DONE DISCOVERY on port 1, pid:841, result:0 Apr 13 10:12:58 tower kernel: sd 0:0:1:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Apr 13 10:12:58 tower kernel: sd 0:0:1:0: [sdf] Write Protect is off Apr 13 10:12:58 tower kernel: sd 0:0:1:0: [sdf] Mode Sense: 00 3a 00 00 Apr 13 10:12:58 tower kernel: sd 0:0:1:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA I changed the font color to red on the parts that identify the ata and drive id. Did you move your troubled drives to a MB port? Post your smart report the more data you provide the better the support.

Although I do not know if it's an actual mode it should have read "simulated", although thinking about what I wrote now doesn't seem correct as the disks in question are still part of the array.

I put them in a test setup and currently playing with freebsd booting in ZFS root. Once I get done playing with that I will install Solaris and play with that. The only issue right now with Solaris 11 is that I can't get it to install or boot with more than one processor core.

Looks to me like your having problems with ata:7 and ata:8 on the sas card. You could try power down set sata cables. Move cables to on board sata ports to see if problem clears. A smart test is in order to see if those drives have issues. I would do that after one and 2 were complete. I could be wrong, but it looks to me like you are in translation mode where the parity drive is translating those two drives and is the reason for your slow performance.