aaron330i
-
Posts
40 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by aaron330i
-
-
I would also like to mention that the new 2TB disk was supposed to be used to replace a disk showing signs of impending terminal peril. I'm crossing my fingers on the rebuild. If it's successful, then the old disk 5 may become the new disk10.
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 39
smartctl -a -d ata /dev/sdh (disk10) smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.11 Device Model: ST31000340AS Serial Number: 9QJ1TWGL Firmware Version: SD15 User Capacity: 1,000,204,886,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Wed Oct 5 12:54:00 2011 GMT+6 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: (0x82) Offline data collection activity was completed without error. 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: ( 650) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 233) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103b) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 107 099 006 Pre-fail Always - 42641272 3 Spin_Up_Time 0x0003 091 084 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 097 097 020 Old_age Always - 3192 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 39 7 Seek_Error_Rate 0x000f 077 060 030 Pre-fail Always - 55119825 9 Power_On_Hours 0x0032 070 070 000 Old_age Always - 26835 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 10 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 126 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 087 000 Old_age Always - 137441050657 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 066 057 045 Old_age Always - 34 (Lifetime Min/Max 33/34) 194 Temperature_Celsius 0x0022 034 043 000 Old_age Always - 34 (0 17 0 0) 195 Hardware_ECC_Recovered 0x001a 040 019 000 Old_age Always - 42641272 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 26691 - 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.
-
Question: Since I have that extra unassigned 2TB disk in the system, would it be better to :
1: Remove the current failed disk5 from the array then assign the new 2TB disk to disk5 and let the parity rebuild?
2: Rebuild the current disk5 from parity.
My personal opinion is to go ahead and assign the new disk5 to parity leaving the old disk5 around "just in case" parity should fail to rebuild.
Question: If I assign the new disk to disk5, will the server preclear the disk prior to rebuild or will it rebuild immediately? Minimizing server unavailability is the chief concern.
-
I was running the preclear script on a new 2TB disk when after a while one of my data disks shows up as being disabled with SMART unable to show any kind of information for the disk. The disk log for the disk before I rebooted was this:
cat /var/log/syslog|egrep "(sdi|scsi17 :|scsi 17:0:0:0| ata17:| ata17.00:|disk5[^0-9]| md5:)" (Filtered syslog for disk5) Oct 5 09:32:39 Tower kernel: scsi17 : ahci Oct 5 09:32:39 Tower kernel: ata17: SATA max UDMA/133 abar m2048@0x92100000 port 0x92100100 irq 33 Oct 5 09:32:39 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 5 09:32:39 Tower kernel: ata17.00: ATA-8: ST31500541AS, CC34, max UDMA/133 Oct 5 09:32:39 Tower kernel: ata17.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32) Oct 5 09:32:39 Tower kernel: ata17.00: configured for UDMA/133 Oct 5 09:32:39 Tower kernel: scsi 17:0:0:0: Direct-Access ATA ST31500541AS CC34 PQ: 0 ANSI: 5 Oct 5 09:32:39 Tower kernel: sd 17:0:0:0: [sdi] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) Oct 5 09:32:39 Tower kernel: sd 17:0:0:0: [sdi] Write Protect is off Oct 5 09:32:39 Tower kernel: sd 17:0:0:0: [sdi] Mode Sense: 00 3a 00 00 Oct 5 09:32:39 Tower kernel: sd 17:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 5 09:32:39 Tower kernel: sdi: Oct 5 09:32:39 Tower kernel: sdi1 Oct 5 09:32:39 Tower kernel: sd 17:0:0:0: [sdi] Attached SCSI disk Oct 5 09:32:39 Tower emhttp: pci-0000:06:00.0-scsi-0:0:0:0 host17 (sdi) ST31500541AS_6XW15LJX Oct 5 09:32:39 Tower kernel: md: import disk5: [8,128] (sdi) ST31500541AS 6XW15LJX offset: 63 size: 1465138552 Oct 5 09:32:40 Tower emhttp: shcmd (9): /usr/local/sbin/set_ncq sdi 1 >/dev/null Oct 5 09:32:40 Tower kernel: md5: running, size: 1465138552 blocks Oct 5 09:32:41 Tower emhttp: shcmd (28): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 >/dev/null 2>&1 Oct 5 09:32:43 Tower emhttp: shcmd (63): echo \"/mnt/disk5\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash' '*(rw)' >>/etc/exports Oct 5 10:14:07 Tower emhttp: shcmd (97): umount /mnt/disk5 >/dev/null 2>&1 Oct 5 10:14:07 Tower emhttp: shcmd (98): rmdir /mnt/disk5 >/dev/null 2>&1 Oct 5 10:14:11 Tower kernel: md5: stopping Oct 5 10:14:29 Tower emhttp: shcmd (130): /usr/local/sbin/set_ncq sdi 1 >/dev/null Oct 5 10:14:29 Tower kernel: md5: running, size: 1465138552 blocks Oct 5 10:14:30 Tower emhttp: shcmd (143): mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 >/dev/null 2>&1 Oct 5 10:14:32 Tower emhttp: shcmd (180): echo \"/mnt/disk5\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash' '*(rw)' >>/etc/exports Oct 5 10:57:33 Tower kernel: ata17: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen Oct 5 10:57:33 Tower kernel: ata17: irq_stat 0x80400040, connection status changed Oct 5 10:57:33 Tower kernel: ata17: SError: { PHYRdyChg DevExch } Oct 5 10:57:33 Tower kernel: ata17: hard resetting link Oct 5 10:57:34 Tower kernel: ata17: SATA link down (SStatus 0 SControl 300) Oct 5 10:57:39 Tower kernel: ata17: hard resetting link Oct 5 10:57:39 Tower kernel: ata17: SATA link down (SStatus 0 SControl 300) Oct 5 10:57:39 Tower kernel: ata17: limiting SATA link speed to 1.5 Gbps Oct 5 10:57:44 Tower kernel: ata17: hard resetting link Oct 5 10:57:44 Tower kernel: ata17: SATA link down (SStatus 0 SControl 310) Oct 5 10:57:44 Tower kernel: ata17.00: disabled Oct 5 10:57:44 Tower kernel: ata17: EH complete Oct 5 10:57:44 Tower kernel: ata17.00: detaching (SCSI 17:0:0:0) Oct 5 10:57:44 Tower kernel: sd 17:0:0:0: [sdi] Synchronizing SCSI cache Oct 5 10:57:44 Tower kernel: sd 17:0:0:0: [sdi] Result: hostbyte=0x04 driverbyte=0x00 Oct 5 10:57:44 Tower kernel: sd 17:0:0:0: [sdi] Stopping disk Oct 5 10:57:44 Tower kernel: sd 17:0:0:0: [sdi] START_STOP FAILED Oct 5 10:57:44 Tower kernel: sd 17:0:0:0: [sdi] Result: hostbyte=0x04 driverbyte=0x00 Oct 5 10:58:01 Tower kernel: ata17: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen Oct 5 10:58:01 Tower kernel: ata17: irq_stat 0x80400040, connection status changed Oct 5 10:58:01 Tower kernel: ata17: SError: { PHYRdyChg DevExch } Oct 5 10:58:01 Tower kernel: ata17: hard resetting link Oct 5 10:58:01 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 5 10:58:01 Tower kernel: ata17.00: native sectors (1) is smaller than sectors (2930277168) Oct 5 10:58:01 Tower kernel: ata17.00: ATA-8: ST31500541AS, CC34, max UDMA/133 Oct 5 10:58:01 Tower kernel: ata17.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32) Oct 5 10:58:01 Tower kernel: ata17.00: configured for UDMA/133 Oct 5 10:58:01 Tower kernel: ata17: EH complete Oct 5 10:58:01 Tower kernel: scsi 17:0:0:0: Direct-Access ATA ST31500541AS CC34 PQ: 0 ANSI: 5 Oct 5 10:58:01 Tower kernel: ata17.00: exception Emask 0x10 SAct 0x1 SErr 0x4010000 action 0xe frozen Oct 5 10:58:01 Tower kernel: ata17.00: irq_stat 0x80400040, connection status changed Oct 5 10:58:01 Tower kernel: ata17: SError: { PHYRdyChg DevExch } Oct 5 10:58:01 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Oct 5 10:58:01 Tower kernel: ata17.00: cmd 60/20:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 16384 in Oct 5 10:58:01 Tower kernel: ata17.00: status: { Busy } Oct 5 10:58:01 Tower kernel: ata17: hard resetting link Oct 5 10:58:02 Tower kernel: ata17: SATA link down (SStatus 0 SControl 300) Oct 5 10:58:06 Tower kernel: ata17: hard resetting link Oct 5 10:58:07 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 5 10:58:07 Tower kernel: ata17.00: configured for UDMA/133 Oct 5 10:58:07 Tower kernel: ata17: EH complete Oct 5 10:58:07 Tower kernel: ata17.00: exception Emask 0x10 SAct 0x1 SErr 0x4010000 action 0xe frozen Oct 5 10:58:07 Tower kernel: ata17.00: irq_stat 0x80400040, connection status changed Oct 5 10:58:07 Tower kernel: ata17: SError: { PHYRdyChg DevExch } Oct 5 10:58:07 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Oct 5 10:58:07 Tower kernel: ata17.00: cmd 60/08:00:80:7a:a8/00:00:ae:00:00/40 tag 0 ncq 4096 in Oct 5 10:58:07 Tower kernel: ata17.00: status: { Busy } Oct 5 10:58:07 Tower kernel: ata17: hard resetting link Oct 5 10:58:07 Tower kernel: ata17: SATA link down (SStatus 0 SControl 300) Oct 5 10:58:12 Tower kernel: ata17: hard resetting link Oct 5 10:58:13 Tower kernel: ata17: SATA link down (SStatus 0 SControl 300) Oct 5 10:58:13 Tower kernel: ata17: limiting SATA link speed to 1.5 Gbps Oct 5 10:58:18 Tower kernel: ata17: hard resetting link Oct 5 10:58:18 Tower kernel: ata17: SATA link down (SStatus 0 SControl 310) Oct 5 10:58:18 Tower kernel: ata17.00: disabled Oct 5 10:58:18 Tower kernel: ata17: EH complete Oct 5 10:58:18 Tower kernel: ata17.00: detaching (SCSI 17:0:0:0) Oct 5 11:00:54 Tower kernel: ata17: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen Oct 5 11:00:54 Tower kernel: ata17: irq_stat 0x80400040, connection status changed Oct 5 11:00:54 Tower kernel: ata17: SError: { PHYRdyChg DevExch } Oct 5 11:00:54 Tower kernel: ata17: hard resetting link Oct 5 11:00:55 Tower kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 5 11:00:55 Tower kernel: ata17.00: native sectors (1) is smaller than sectors (2930277168) Oct 5 11:00:55 Tower kernel: ata17.00: ATA-8: ST31500541AS, CC34, max UDMA/133 Oct 5 11:00:55 Tower kernel: ata17.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32) Oct 5 11:00:55 Tower kernel: ata17.00: configured for UDMA/133 Oct 5 11:00:55 Tower kernel: ata17: EH complete Oct 5 11:00:55 Tower kernel: scsi 17:0:0:0: Direct-Access ATA ST31500541AS CC34 PQ: 0 ANSI: 5 Oct 5 11:40:07 Tower kernel: md: disk5 read error Oct 5 11:40:07 Tower kernel: md: disk5 write error Oct 5 11:40:07 Tower kernel: md: disk5 read error Oct 5 11:40:15 Tower kernel: md: disk5 write error Oct 5 11:43:13 Tower kernel: md: disk5: open_by_devnum error: -6 Oct 5 11:43:17 Tower emhttp: shcmd (214): umount /mnt/disk5 >/dev/null 2>&1 Oct 5 11:43:18 Tower emhttp: shcmd (215): rmdir /mnt/disk5 >/dev/null 2>&1 Oct 5 11:43:21 Tower kernel: md5: stopping DoneAfter rebooting, I was able to run smartctl to get information about the disk and for the life of me, I can't really see anything wrong with it.:
smartctl -a -d ata /dev/sdi (disk5) smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500541AS Serial Number: 6XW15LJX Firmware Version: CC34 User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Wed Oct 5 12:13:44 2011 GMT+6 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 653) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 195402452 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1963 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 5610545 9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 11923 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 97 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 099 000 Old_age Always - 4295032833 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 070 063 045 Old_age Always - 30 (Lifetime Min/Max 29/30) 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 17 0 0) 195 Hardware_ECC_Recovered 0x001a 061 049 000 Old_age Always - 195402452 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 226306121796863 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1779109296 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 829014263 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 11781 - 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.
I'm sorta lost as to whether or not the disk is truly bad, or if preclearing the new disk may have caused some sort of controller error, or something else entirely. I don't really know what to do to get my server into a protected state asap.
-
One last interesting item of note: I can't seem to figure out the /dev/disk of the cache drive. I know it's sdg/sdg1, but I can't figure out what dev it maps to to run reiserfsck. Is this an RTFM I missed somewhere?
-
Doing this won't interrupt the new drive being rebuilt from parity?
-
...with the actual cache drive becoming unallocated. I then removed the new and incorrectly assigned cache drive and readded the old cache drive. Problem is I get a syslog full of:
Feb 9 08:25:50 Tower kernel: REISERFS error (device sdg1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 2787 0x0 SD] Feb 9 08:25:50 Tower kernel: REISERFS error (device sdg1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 2904 0x0 SD] Feb 9 08:25:50 Tower kernel: REISERFS error (device sdg1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 2901 0x0 SD]
messages. I assume I need to run reiserfsk, but since the new drive replaced an older drive, it is being rebuilt from parity and I don't want to stop the process...it's going very, very slow due to the number of older IDE PATA drives in the box.
The downside is I cannot seem to access most of my user shares, only the direct disk1-xx shares. Oh well, in another 18 hours the new drive should be rebuilt from parity and I'll be on my merry reiserfscking way.
Unless samba can be stopped without causing the drive rebuilding to stop as well?
-
I had that problem initially when I replaced my motherboard. It turned out the bios wasn't properly detecting the RAM timings (cheap RAM). Once I manually set the timings the problem went away. To reduce heat even more, I underclocked both the ram and the processor. There was no noticable difference in performance when I did this, but temps went down a few degrees.
-
This worked great for me with my new Intel DP35DP motherboard. I only ran the USB-ZIP version, but it worked and unRAID booted up first try.
-
I had a motherboard die on me. A 6 year old Athlon board that had been on its legs for a long time but since it was serving up my 11 unRAID array, I didn't want to mess with it unless I really had to.
And I finally had to. It died.
Hi ho hi it it's off to Fry's I go, and came back with an Intel DP35DP (open box) with the cheapest Core 2 (also open box) I could buy.
After figuring how to get my 8xIDE + 3xSATA drives working on a mobo that only has 1 non-operational IDE connector (fortunatly, I had an old SiiS IDE card around), I booted up, set the proper drive order in the devices page, and the array started without even needing a parity check (though I did one anyway).
After all this time, the simplicity, reliability, and convenience of unRAID still astounds me. The fact I could go from a 6 year old motherboard to a brand new one, totally change which drives were on what connector or expansion car, and then just have it "work" makes this a great product.
Since I now have a couple spare SATA connecters, I also bought two 1TB Seagate drives and am in the process of adding them to the array. One drive will replace a 400GB IDE, and the other will be an addition. This will then give me 7.4TB in 12 drives. I hope by reducing the number of IDE drives the parity check will speed up a bit.
When first adding in the 1TB drive so it became parity, my parity calc speeds are:
0-400GB 15MB/sec
400-500GB 18MB/sec
500-750GB 55MB/sec
750-1TB 65MB/sec (just the parity drive by itself)
-
Grats on beta6. Installed it on 4/2 with a 250GB cache disk and it has been up and running with zero downtime since then. What a huge difference the cache disk makes in the performance of the system. I love it.
-
I thought User Share data was cached by unRAID so that shares could be browsed by clients without having to spin up the drives until files actually needed to be read?
Or does Vista, when exploring, read properties not handled by unRAID?
-
My server with 6 year old motherboard upgraded to beta 6 no problem. It now has 11 disk including the cache disk which was an old 250MB disk I had in an external enclosure. The gigE card (Realtek based) worked flawlessly as well.
The write times when using the cache were about 2 1/2 (a whopping 16MB/s) times faster than writing to a non-cache disk
The mover service must have executed just fine since the cache disk was empty sans directories.
Writing files into a pre-existing directory not on the cache disk resulted in a direct write to the share, not having the file get written to the cache. In these cases I had to explicitly create the path on the cache disk first.
One hard thine for me to do is to give up control where files are being placed. I have always been very organized as to what goes on what disk...but I think that is from using unRAID 3.x for over two years without bothering to upgrade. The thought of taking down my zero downtime server and possibly messing it up scared me. hehe. After getting a new case and power supply and a few new disks necessitated getting current. And I'm glad I did.
Keep up the good work!
-
I disabled user security, deleted user accounts, but still getting login and access denied messages. i'll delete those files and reboot the server and see what happens.
-
is there a way to delete or reset the files that control security?
-
I noticed my Fry's has a boatload of refurbished AB9 Pro's for $40 each. I was sorely tempted to roll the dice and try one, but they were out of stock on the $50 core 2's and I didn't want to have to jump up to the $120 one.
-
I'm up and running and have found that the old PCI sata controller card I have isn't being picked up (and so the Disk on it isn't).
My old Mobo has only 4 SATA ports and theyre full.
A new Mobo may be cheaper than a new SATA controller card (plus I'll get on board video etc, etc).
So how easy is it to do open heart bypass surgery on your unRAID server?
If you swap out the mobo, CPU, and memory for new components, how do you bring your disks back into play without lossing data?
Thanks in advance....
Lol, whack me up side the head...I never did the math on buying a new mobo vs. new SATA card. My mobo is very old. probably a good 5 years old. Wish I didn't buy that SATA card a few weeks ago...won't make that mistake again.
-
It helps to know a bit about how SMART drives work, and what unRAID does, with physical read errors.
...
(snip)
...
-Brian
Thanks for the lengthy explanation Brian, it explains a lot!
So far, so good with the drive. I think that part of the problem also may have been a heat buildup problem. After removing the front of the case, the vent opening in front of that drive was completely blocked with dust. After thoroughly cleaning the entire case of dust buildup the average temps of all drives went down between 5-10 degrees. The parity drive being one drive that went down 10 degrees.
-
Upgraded to 4.2.1, rebuilt parity, and haven't had any errors since. Going on almost a couple weeks now.
-
I recently upgraded the parity drive in my unRAID system from a 500GB IDE to 750GB Barracuda 7200.10 SATA (was pretty easy).
About five days ago, I noticed the error count on the parity drive wasn't the zero I was expecting. It was a 1. Two nights ago, I added an additional 750GB Barracuda to my server and after it finally became available to the array, I started moving content between the drives in a small attempt at better organization.
Today I woke up and the error count on the parity drive was "1" so I looked in the syslog and this was in it:
Feb 16 08:01:26 Tower kernel: ata2: status=0x50 { DriveReady SeekComplete } Feb 16 08:01:26 Tower kernel: SCSI disk error : host 2 channel 0 id 0 lun 0 return code = 8000002 Feb 16 08:01:26 Tower kernel: Current sd08:11: sns = 70 0 Feb 16 08:01:26 Tower kernel: Raw sense data:0x70 0x00 0x00 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Feb 16 08:01:26 Tower kernel: I/O error: dev 08:11, sector 28764376 Feb 16 08:01:26 Tower kernel: md0: read error! Feb 16 08:01:26 Tower kernel: end_read_request 28764376/0, count: 1, uptodate 0. Feb 16 08:07:38 Tower smbd[2336]: [2008/02/16 08:07:38, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(993) Feb 16 08:07:38 Tower smbd[2336]: api_pipe_bind_req: unknown auth type 1 requested.Question: Is the occasional error on the parity drive itself cause for alarm? Or do I just monitor it more closely for a while and see what happens? I don't know if the earlier error was the same sector or not.
I'm running unRAID 3.1 beta 2
My motherboard is older and doesn't have any SATA ports so I'm using a Promise SATA300 PCI adapter.
Thanks.
Aaron
-
I boot from a "kicker disk" floppy since my motherboard doesn't support booting from USB. It's been working for me for a long time.
So long, in fact, that I've been hesitant in upgrading my 3.1 beta-2 unRAID box.
-
For Promise, there's a 2-card-of-the-same-type limit - this is a Promise bios limitation. You should be able to install a third card of a different type (try a SIIG card, though we haven't tested that, it should work with 4.0). You could also plug a SATA card in there.
at least as of the 3.x beta, I was unable to get the SIIG PATA controller to work with unRaid.
-
Right, no floppy support was built into the kernel.... If you can find 3 people who want that feature, I'll add it
Time to register two more accounts.
-
I also have no problem with this scheme.
I have (personally) never had any flash memory ever go bad on me, not my MP3 player i've had for years and gets written to daily, nor the 32MB memory card for the digital camera i've had for 6 years that I let my kid play with.
I would think the main danger would be to accidental breakage because its poking out the front or back of the computer and it gets broken off at the connector...also easily solved by using a small USB extension cord then taping the flash drive flat or moving it inside the case.
-
I backup my digital photos and computers to disk1 of my unRaid server using NT Backup and some some RoboCopy scripts. I feel good about having my most important data backed up and secure, but in the case of fire or theft, i'm still screwed.
What I would like to be able to do is have three disks identical to disk1, and on a periodic basis, pull disk1 out and move it offsite then stick in one of the other two disks and rebuild it from parity, then rinse and repeat.
my main question revolves around what happens when the first dist that got pulled comes back around and gets re-inserted into the array. Does the old data on that drive get overwritten with the current parity information or does the parity get recalculated because a valid unRaid disk was placed in disk1 location. Also, if I did need to replace the disk with the offsite version, what would be the best procedure to do that? Stop the array, select Rebuild option, shutsown, swap drive, boot, and then start the array to calculate new parity?
Much thanks.
[UNSOLVED BUT REBUILDING] HELP! What would cause this disk to disable? (v 4.5.3)
in General Support (V5 and Older)
Posted
I've decided to rebuild using the new disk. My 16 disk array will take almost 20 hours to rebuild. When it gets past the 1TB mark of (the size of disk10), I'll breath a bit easier. Then it'll be time to preclear the old disk on a different SATA channel to verify the disk is truely good before using it as a replacement for disk10. Sigh, I hate babysitting. Heh.