crazytony

no -- it doesn't appear to work in 5. But it was working in 4.6 (confirmed both by hdparm and physically touching the device to check for vibrations).

The 2805 is not an old controller -- it's still in production/shipping by Adaptec. They just released a firmware update that allows disks larger than 3TB as well. The problem is the SASLP is not available in Australia as far as I could find. Seems there is a huge regional variation in motherboard and SATA/SAS controller availability. Spinup/down was working in 4.6/4.7 and stopped working in 5. I know that the linux driver (aacraid) went through some large updates between the 4.7 kernel and the 5 kernel (I could get no smartctl data in 4.7 no matter what I did). It's not a huge priority because I can monitor the temps by myself.

I know some work was done in 5b5 and 5b6 for this but I'm still seeing a * under temperature on the adaptec. Probably because it requires a device type (-d sat). Get rid of it in one place to bring it back in another - webGui: use smartctl program to enable SMART and get disk temperatures instead of ioctl()'s. - webGui: use hdparm program to query spinning status instead of ioctls()'; now all device type specific code is gone. I did notice the ioctl errors are gone from my syslog.

everything looks good -- parity has been completed.

they all say Partition Format: MBR unaligned (I would expect them to say that -- they're jumpered) I thought the blue icon was for expansion and green was for good. I've pushed start and they're all green except for parity (orange-red) and it says parity sync in progress. I will let it complete.

Hey guys, Upgraded from 5b4 to 5b6 but 5b6 isn't able to start due to it thinking all my drives are expansion drives (they're not). Here is the setup from 5b4: Here's what I see in 5b6: I deleted (renamed) the super.dat file in the config folder. The last disk (sda) is correct despite having a different name -- 5b4 was truncating the last two characters '16' from the name.

is the drive attached to the motherboard or another SATA adapter?

My setup started doing this as well today as well. I moved some disks around to in a case cleanup move but I got a couple of cables wrong. I swapped assignments then started the array then decided to just go ahead and fix the cables. After I shutdown and swapped the cables back, the devices no longer auto-associate. Once I assign the disks the array is valid and can start..

You do need to force it via -d sat. smartctl --all /dev/sda smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Device: WDC WD20EARS-00M Version: 51.0 Serial number: WD-WMAZA0765516 Device type: disk Transport protocol: SAS Local Time is: Sun Feb 13 10:49:49 2011 EST Device supports SMART and is Enabled Temperature Warning Disabled or Not Supported SMART Health Status: OK Error Counter logging not supported Device does not support Self Test logging in addition, I can see the errors in the syslog (which are new to 5b4): Feb 13 10:36:20 mediastorage emhttp: disk_temperature: ioctl (smart_enable): Inappropriate ioctl for device Feb 13 10:36:44 mediastorage last message repeated 2 times

In 4.6 and 4.7 the temperature wasn't displayed for the disks on my adaptec 2805 due to the adaptec driver in the kernel being very old (couldn't even get it in smartctl). I've got 5b4 running but the temperature still isn't showing in the GUI (but I can get it through smartctl). I have a feeling this is due to the -d flag. If it's not too much trouble to fix, could we get access to this in 5.0? Here's the output from running smartctl smartctl -d sat --all /dev/sda smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA0765516 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Feb 13 10:39:53 2011 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (37080) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 164 162 021 Pre-fail Always - 6791 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 38 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1397 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 35 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 33 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1410 194 Temperature_Celsius 0x0022 111 105 000 Old_age Always - 39 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

It looks like it rebuilt just fine. I'm checking md5 sums now. Update: md5sums are all ok between the backup and the restored disk. I keep a warm swap disk: precleared but not added to the array just in case a disk dies. Whenever I need capacity, I buy another disk, preclear it and add the warm swap. I think the reason the mobo is not set to AHCI is that I had problems booting with 6 disks plugged in. I'll have to check -- it's been about 6 months since I built the thing.

ok I punched it because I desperately want the 5.0 kernel. Will let you know in 13 hours.

sorry about the delay. Only had to move over about 500GB but I wasn't paying attention and I used rsync with the -z option. Whoops. lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20101615 -> ../../sdc lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20101615-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20116383 -> ../../sdg lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20116383-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20187386 -> ../../sde lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20187386-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0368817 -> ../../sdf lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0368817-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0371846 -> ../../sdh lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0371846-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1669301 -> ../../sdd lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1669301-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA0765516 -> ../../sda lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA0765516-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA3483417 -> ../../sdb lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA3483417-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20101615 -> ../../sdc lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20101615-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20116383 -> ../../sdg lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20116383-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20187386 -> ../../sde lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20187386-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0368817 -> ../../sdf lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0368817-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0371846 -> ../../sdh lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0371846-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1669301 -> ../../sdd lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1669301-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 usb-SanDisk_Cruzer_Blade_2005173882162BA1275E-0:0 -> ../../sdi lrwxrwxrwx 1 root root 10 Feb 12 19:30 usb-SanDisk_Cruzer_Blade_2005173882162BA1275E-0:0-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee057a1e164 -> ../../sdh lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee057a1e164-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee0acf775ca -> ../../sdf lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee0acf775ca-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee6002f406d -> ../../sdc lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee6002f406d-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee6558480fa -> ../../sde lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee6558480fa-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee655854d3e -> ../../sdg lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee655854d3e-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee6ab379741 -> ../../sdd lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee6ab379741-part1 -> ../../sdd1 thoughts? I have a feeling that if I push that button, I can't go back to 4.6 or 4.7 without pushing that button again....

I'm currently in the process of backing up the data on that disk. Here is what the output for 4.6 looks like: lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20101615 -> ../../sdc lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20101615-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20116383 -> ../../sdg lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20116383-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20187386 -> ../../sde lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20187386-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0368817 -> ../../sdf lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0368817-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0371846 -> ../../sdh lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0371846-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1669301 -> ../../sdd lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1669301-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA0765516 -> ../../sda lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA0765516-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA3483417 -> ../../sdb lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA3483417-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20101615 -> ../../sdc lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20101615-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20116383 -> ../../sdg lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20116383-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20187386 -> ../../sde lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20187386-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0368817 -> ../../sdf lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0368817-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0371846 -> ../../sdh lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0371846-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1669301 -> ../../sdd lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1669301-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 usb-HP_v220w_0000000000002C-0:0 -> ../../sdi once I have the data backed up, I will boot into 5.0b4 and let you know what that looks like.

it has a little data on it -- I was thinking that it would format and rebuild from parity in the worst case scenario. Good to know that it's a tactical nuke. :'( Have already swapped the 4.6 and the 5b4 sticks and the array is back and operational.

4.6 and 4.7 boot just fine but when I boot 5b4 and assign disks I get the following: I'm thinking that this is because that last disk is on the adaptec controller and didn't have a serial number in the array screen but did have one on the devices page. Thoughts on moving forward?

sometimes fact is stranger than fiction. I installed 5.0b4 on a brand new flash drive (formatted, installed the AIO version, copied over the license and away I went). I didn't think anything was wrong because it booted the 5.0 interface. But I left the 4.6 thumbdrive in the machine and upon looking at /boot it was the 4.6 install.

Having some probs booting 5.0b4: when it boots, I see the welcome message (in the browser) then as soon as I click on anything I get the following page (in the browser): unRAID Server version: Log <?=$pg['Title'];?> Here's the syslog (doesn't look suss): http://pastebin.com/r88TirfT This is what the screen looks like: 4.6 boots just fine.... EDIT: Solved the 4.7 flash drive was still installed

I don't think that is true. ... the setting is used only if the disk does not have an existing MBR or valid preclear-signature. (in other words, an empty or foreign disk) If the disk is already partitioned from a prior version of unRAID, it works as it was, and the partition is unchanged. What happened for me was I put 5.0b3 on my second thumbdrive and restarted the machine. Initially when it came up there were no drives listed and I was just about to go to the drive assignment screen before I thought better of it. I tabbed around on the settings a bit and found the 4k-aligned setting was enabled. I switched it to the non-4k aligned, rebooted and the whole array showed up on the device screen. I decided against starting the array and then rebooted with my 4.7 thumbdrive. That was the extent of my 5.0b3 run. I'm happy with the speed of the disks in realworld usage (even if the preclear is 1/2 the speed). Once I summon the courage to run 5.0b3 again I will do a little more testing.

More digging -- 5.0b3 has the kernel Adaptec recommends (2.6.36). I installed 5.0b3 but had a bit of a nightmare (4k aligned is the default setting and I could have lost my array if I had not thought better of manually adding my disks to the array). I'll give it a go again next week when I have more time. I'm starting to think most of this is moot because even though preclear was half the speed, when I added the disks to the array and started testing them they were slightly faster than via the mobo headers. My average write was 23MB/s on the mobo (over samba) vs 26MB/s on the adaptec drive. These were both clean, empty drives using the same exact 20 GB file. Likewise my read speed over samba is about 42MB/s for the mobo and 44MB/s for the adaptec card.

Just getting my Adaptec 2805 up and running and had a couple questions for guys running Adaptec cards and/or the 2-series in general. I've got 6 disks plugged in to the 6 headers on my mobo and when I run preclear through them I get a fairly consistent ~100MB/s write speed. When plugged in via my adaptec card, I'm seeing a consistent 50MB/s write speed. The disks are setup as JBODs so the actual device shouldn't be doing anything. I don't think it's the motherboard an issue with bandwith because I can run 3 preclears at the same time and get the same 50MB/s write speed on each of them. I'm using all WD20EARS disks (staggered purchases, etc...) and if I swap headers I see the normal rate. Doing some digging, it appears that Adaptec is endorsing a newer version of the aacraid module than ships with unraid. My question to Adaptec owners is: what does your preclear speed look like? have you taken their advice and manually upgraded the module? If so, what version? What speed do you see on preclear?