dlmh Posted August 12, 2011 Share Posted August 12, 2011 I would be extremely surprised if anyone would be running them 24/7 given even my lowest power attempts draws at least 40W with my drives shut down, and I don't have additional cards! S3 Sleep working perfectly here. My server is on 24/7 along with my desktop since the torrent client is on my PC. If the torrent client isn't running everything is sleeping. You do know that you can install a Torrent client on unRAID, right? Quote Link to comment
Interstellar Posted August 12, 2011 Share Posted August 12, 2011 I would be extremely surprised if anyone would be running them 24/7 given even my lowest power attempts draws at least 40W with my drives shut down, and I don't have additional cards! S3 Sleep working perfectly here. My server is on 24/7 along with my desktop since the torrent client is on my PC. If the torrent client isn't running everything is sleeping. You do know that you can install a Torrent client on unRAID, right? Well count me surprised then. Although, if we are being specific, you are all running software on top of UnRAID. If you were running virgin systems (i.e. as supplied by Limetech) that are only required when your awake/a machine is running other than UnRAID then you'd sleep them, surely? And yes I'm well aware that Torrenting is possible, however I don't torrent. I run a few things from my server too, however given that they are only accessed when I'm awake or the PS3/Mac Pro is on then absolutely no point in it running at all other times I might start a poll to see what usage is! Interested now given power usage is fairly important. Edit: @Prostuff, crashplan is rather high-end and rare usage for the UnRAID market, no? Quote Link to comment
prostuff1 Posted August 12, 2011 Share Posted August 12, 2011 Edit: @Prostuff, crashplan is rather high-end and rare usage for the UnRAID market, no? Probably, but there is a fairly large thread about getting it set up and running on the unRAID server. Quote Link to comment
aiden Posted August 12, 2011 Share Posted August 12, 2011 Edit: @Prostuff, crashplan is rather high-end and rare usage for the UnRAID market, no? You might be surprised how many of us are using Crashplan with unRAID. It's popular enough to have a wiki entry, a large active thread, and a 5.x plug-in. Quote Link to comment
abeta Posted August 12, 2011 Share Posted August 12, 2011 Any assistance the unRaid screen problem from a few pages back? It doesn't look like I have php doing anything? Thx. Quote Link to comment
Joe L. Posted August 12, 2011 Share Posted August 12, 2011 Any assistance the unRaid screen problem from a few pages back? It doesn't look like I have php doing anything? Thx. Yes perhaps... I updated the unMENU packages to edit their respective php.ini files. Basically, if you only installed "php" it would probably install its .ini file under /etc/httpd The same edit would apply to it. You can check for updates in unMENU, then, after you have downloaded the updated package and logged in via telnet, type rm /boot/packages/php-5.2.8-i486-1.tgz.manual_install rm /boot/packages/php-5.2.8-i486-1.tgz.auto_install rm /boot/packages/php-5.2.8-i486-1.tgz Then, re-install php via the package manager. Or, you can just run this command: sed -i "s/^short_open_tag = Off/short_open_tag = On/" /etc/httpd/php.ini Quote Link to comment
Superorb Posted August 12, 2011 Share Posted August 12, 2011 I know unRAID can run a Torrent client, I just haven't gotten around to it yet. Quote Link to comment
mfort312 Posted August 12, 2011 Share Posted August 12, 2011 I've been having some funny problems with this release... I keep getting 'simple features' email notifications that I have an array fault (missing or invalid disk). The array and AFP/SMB shares seem to be running ok at the moment, but the drive mappings in the email don't match my actual setup (screenshot attached). The email erroneously lists disk1 as my parity drive, and the rest of the drives are also mismatched in sequence. I don't actually have a parity drive assigned yet; I'm still in the process of adding data before activating one. The problems started after a automated backup to a Time Machine Share initiated at the same time as a large file copy to the same drive (but different share) and AFP crashed and unmounted all the shares. It took a restart of both server and client and several minutes of waiting to reconnect to my AFP shares. I've been receiving the emails since, even after repeated restarts and file system checks. The Time Machine backups are still pretty flaky; every few hours it fails to mount the drive but eventually succeeds. It usually takes several minutes to reconnect my Time Machine share after the backup fails. Any advice on troubleshooting? I've attached my recent syslog and my console messages from yesterday when the AFP crash happened. I'm running the 5beta10 version and accessing from a Snow Leopard client. Array Fault email: This message is a status update for unRAID Tower ----------------------------------------------------------------- Server Name: Tower Status: unRaid array not started. Status: The unRaid array needs attention. One or more disks are disabled or invalid. Date: Fri Aug 12 14:18:05 CDT 2011 Disk Temperature Status ----------------------------------------------------------------- Parity Disk [sdc]: 35°C (DiskId: Hitachi_HDS5C3020ALA632_ML0220F313L5PD) Disk 1 [sdd]: 34°C (DiskId: Hitachi_HDS5C3020ALA632_ML0220F313NV0D) Disk 2 [sde]: 33°C (DiskId: Hitachi_HDS5C3020ALA632_ML0220F313S42D) Disk SMART Health Status ----------------------------------------------------------------- Parity Disk PASSED (DiskId: Hitachi_HDS5C3020ALA632_ML0220F313L5PD) Disk 1 PASSED (DiskId: Hitachi_HDS5C3020ALA632_ML0220F313NV0D) Disk 2 PASSED (DiskId: Hitachi_HDS5C3020ALA632_ML0220F313S42D) Output of /proc/mdcmd: ----------------------------------------------------------------- sbName=/boot/config/super.dat sbVersion=2.1.2 sbCreated=1311308833 sbUpdated=1313175533 sbEvents=31 sbState=1 sbNumDisks=4 sbSynced=0 sbSyncErrs=0 mdVersion=2.1.2 mdState=STOPPED mdNumProtected=4 mdNumDisabled=1 mdDisabledDisk=0 mdNumInvalid=1 mdInvalidDisk=0 mdNumMissing=0 mdMissingDisk=0 mdNumNew=0 mdResync=0 mdResyncCorr=0 mdResyncPos=0 mdResyncDt=0 mdResyncDb=0 diskNumber.0=0 diskName.0= diskSize.0=0 diskState.0=4 diskId.0= rdevNumber.0=0 rdevStatus.0=DISK_DSBL_NP rdevName.0= rdevSize.0=0 rdevId.0= rdevNumErrors.0=0 rdevLastIO.0=0 rdevSpinupGroup.0=0 diskNumber.1=1 diskName.1=md1 diskSize.1=1953514552 diskState.1=7 diskId.1=Hitachi_HDS5C3020ALA632_ML0220F313L5PD rdevNumber.1=1 rdevStatus.1=DISK_OK rdevName.1=sdc rdevSize.1=1953514552 rdevId.1=Hitachi_HDS5C3020ALA632_ML0220F313L5PD rdevNumErrors.1=0 rdevLastIO.1=1313175588 rdevSpinupGroup.1=0 diskNumber.2=2 diskName.2=md2 diskSize.2=1953514552 diskState.2=7 diskId.2=Hitachi_HDS5C3020ALA632_ML0220F313NV0D rdevNumber.2=2 rdevStatus.2=DISK_OK rdevName.2=sdd rdevSize.2=1953514552 rdevId.2=Hitachi_HDS5C3020ALA632_ML0220F313NV0D rdevNumErrors.2=0 rdevLastIO.2=1313175588 rdevSpinupGroup.2=0 diskNumber.3=3 diskName.3=md3 diskSize.3=1953514552 diskState.3=7 diskId.3=Hitachi_HDS5C3020ALA632_ML0220F313S42D rdevNumber.3=3 rdevStatus.3=DISK_OK rdevName.3=sde rdevSize.3=1953514552 rdevId.3=Hitachi_HDS5C3020ALA632_ML0220F313S42D rdevNumErrors.3=0 rdevLastIO.3=1313175588 rdevSpinupGroup.3=0 diskNumber.4=4 diskName.4= diskSize.4=0 diskState.4=0 diskId.4= rdevNumber.4=4 rdevStatus.4=DISK_NP rdevName.4= rdevSize.4=0 rdevId.4= rdevNumErrors.4=0 rdevLastIO.4=0 rdevSpinupGroup.4=0 diskNumber.5=5 diskName.5= diskSize.5=0 diskState.5=0 diskId.5= rdevNumber.5=5 rdevStatus.5=DISK_NP rdevName.5= rdevSize.5=0 rdevId.5= rdevNumErrors.5=0 rdevLastIO.5=0 rdevSpinupGroup.5=0 UPDATE: Once I built my parity disk, the hourly emailed errors went away. console.txt syslog-2011-08-12.txt.zip Quote Link to comment
dimaestro Posted August 12, 2011 Share Posted August 12, 2011 And a dead server again today. Gonna drop back to 4.7. I just hope the file copies I initiated over lunch completed correctly. Just a quick update: Since I downgraded to 4.7 I haven't had a lockup/non responsive server since. Quote Link to comment
abeta Posted August 13, 2011 Share Posted August 13, 2011 Any assistance the unRaid screen problem from a few pages back? It doesn't look like I have php doing anything? Thx. Yes perhaps... I updated the unMENU packages to edit their respective php.ini files. Basically, if you only installed "php" it would probably install its .ini file under /etc/httpd The same edit would apply to it. You can check for updates in unMENU, then, after you have downloaded the updated package and logged in via telnet, type rm /boot/packages/php-5.2.8-i486-1.tgz.manual_install rm /boot/packages/php-5.2.8-i486-1.tgz.auto_install rm /boot/packages/php-5.2.8-i486-1.tgz Then, re-install php via the package manager. Or, you can just run this command: sed -i "s/^short_open_tag = Off/short_open_tag = On/" /etc/httpd/php.ini I did both (updated unmenu, reinstalled package and ran the command line), I can't get it to boot with 5.0 Beta 10. It doesn't respond to anything now. I can't connect to it at it either through telnet, webpage, or anything. I restored back to 4.7. I'm going to give up on this beta, it doesn't seem to like me. Quote Link to comment
squirrellydw Posted August 13, 2011 Share Posted August 13, 2011 So, does anyone know why my drives won't spin down? Anything I can try? Quote Link to comment
Nezil Posted August 13, 2011 Share Posted August 13, 2011 I know this isn't the right place to make a full post, so I'm just linking to a thread I've created in the General section with a solution to the 'OS X Lion Finder Sidebar SMB' issue. Thread is here: http://lime-technology.com/forum/index.php?topic=14623.msg137872 Hopefully Tom might be able to put this fix into the next build for the Mac users among us. Quote Link to comment
Whaler_99 Posted August 13, 2011 Share Posted August 13, 2011 So, does anyone know why my drives won't spin down? Anything I can try? Have you tried going into the settings for each disk, setting a value other then default, hit apply, and see of that works? Shawn Quote Link to comment
mikejp Posted August 13, 2011 Share Posted August 13, 2011 So, does anyone know why my drives won't spin down? Anything I can try? Have you tried going into the settings for each disk, setting a value other then default, hit apply, and see of that works? Shawn I went into the settings for each disk, didn't change anything, hit apply, hit done... drives spin down as they should. Mike Quote Link to comment
PeterB Posted August 13, 2011 Share Posted August 13, 2011 I don't think there are many people in general that use S3 Sleep, S2ram, etc. They are either running 24/7 (like mine) or people just turn them off. I would be extremely surprised if anyone would be running them 24/7 given even my lowest power attempts draws at least 40W with my drives shut down, and I don't have additional cards! I'm sure that a lot of us have our unRAID servers running 24/7 - I certainly do. S3 Sleep working perfectly here. Yes, I can get S3 Sleep working, and while my music players will wake it up automatically, the video players require manual intervention - this is more than I can expect the kids to cope with when they want to watch a video. In any case, I've not yet implemented a way to wake the machine up in the case of a power cut, so that it can shut itself down before the UPS cuts out. Quote Link to comment
Joe L. Posted August 13, 2011 Share Posted August 13, 2011 I don't think there are many people in general that use S3 Sleep, S2ram, etc. They are either running 24/7 (like mine) or people just turn them off. I would be extremely surprised if anyone would be running them 24/7 given even my lowest power attempts draws at least 40W with my drives shut down, and I don't have additional cards! I'm sure that a lot of us have our unRAID servers running 24/7 - I certainly do. S3 Sleep working perfectly here. Yes, I can get S3 Sleep working, and while my music players will wake it up automatically, the video players require manual intervention - this is more than I can expect the kids to cope with when they want to watch a video. In any case, I've not yet implemented a way to wake the machine up in the case of a power cut, so that it can shut itself down before the UPS cuts out. Many boards also support wake-on-ring. (for the serial port) Perhaps, if your MB has such a feature, you can rig a relay to trip the RI lead on the serial port, and feed the coil on the relay with un-protected power from a wall-wart. You lose power, it simulates a ringing phone, and wakes up the server. Would take a bit of experimenting, but a cliplead or two and you would know if the RI lead on the serial port can be used when sleeping to wake the server. Joe L. Quote Link to comment
squirrellydw Posted August 13, 2011 Share Posted August 13, 2011 So, does anyone know why my drives won't spin down? Anything I can try? Have you tried going into the settings for each disk, setting a value other then default, hit apply, and see of that works? Shawn Yeah, tried that and still don't spin down Quote Link to comment
WingmanNZ Posted August 14, 2011 Share Posted August 14, 2011 Just upgraded to 5b10 and now im getting these errors when the mover script is moving the data off the cache disk. the disk doesnt have and SMART status errors... anyone have any pointers? Aug 14 18:21:57 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:21:57 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:21:57 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:21:57 Aurora-NAS01 kernel: ata1: EH complete Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr0x0 action 0x0 Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: irq_stat 0x40000001 Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: failed command: READ DMA EXT Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: cmd 25/00:f0:e8:eb:b1/00:03:e7:00:00/e0 tag 0 dma 516096 in Aug 14 18:22:08 Aurora-NAS01 kernel: res 51/40:5f:70:ee:b1/00:01:e7:00:00/e0 Emask 0x9 (media error) Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:22:08 Aurora-NAS01 kernel: ata1: EH complete Aug 14 18:22:16 Aurora-NAS01 kernel: mdcmd (106): spindown 4 Aug 14 18:22:17 Aurora-NAS01 emhttp: shcmd (694): /usr/sbin/hdparm -y /dev/sdc &> /dev/null Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr0x0 action 0x0 Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: irq_stat 0x40000001 Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: failed command: READ DMA EXT Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: cmd 25/00:00:d8:ff:b1/00:04:e7:00:00/e0 tag 0 dma 524288 in Aug 14 18:22:23 Aurora-NAS01 kernel: res 51/40:2f:a2:01:b2/00:02:e7:00:00/e0 Emask 0x9 (media error) Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:22:23 Aurora-NAS01 kernel: ata1: EH complete Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr0x0 action 0x0 Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: irq_stat 0x40000001 Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: failed command: READ DMA EXT Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: cmd 25/00:98:e8:5d:c3/00:01:e7:00:00/e0 tag 0 dma 208896 in Aug 14 18:23:14 Aurora-NAS01 kernel: res 51/40:37:47:5e:c3/00:01:e7:00:00/e0 Emask 0x9 (media error) Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:23:14 Aurora-NAS01 kernel: ata1: EH complete Quote Link to comment
Joe L. Posted August 14, 2011 Share Posted August 14, 2011 Just upgraded to 5b10 and now im getting these errors when the mover script is moving the data off the cache disk. the disk doesnt have and SMART status errors... anyone have any pointers? Aug 14 18:21:57 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:21:57 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:21:57 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:21:57 Aurora-NAS01 kernel: ata1: EH complete Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr0x0 action 0x0 Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: irq_stat 0x40000001 Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: failed command: READ DMA EXT Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: cmd 25/00:f0:e8:eb:b1/00:03:e7:00:00/e0 tag 0 dma 516096 in Aug 14 18:22:08 Aurora-NAS01 kernel: res 51/40:5f:70:ee:b1/00:01:e7:00:00/e0 Emask 0x9 (media error) Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:22:08 Aurora-NAS01 kernel: ata1: EH complete Aug 14 18:22:16 Aurora-NAS01 kernel: mdcmd (106): spindown 4 Aug 14 18:22:17 Aurora-NAS01 emhttp: shcmd (694): /usr/sbin/hdparm -y /dev/sdc &> /dev/null Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr0x0 action 0x0 Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: irq_stat 0x40000001 Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: failed command: READ DMA EXT Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: cmd 25/00:00:d8:ff:b1/00:04:e7:00:00/e0 tag 0 dma 524288 in Aug 14 18:22:23 Aurora-NAS01 kernel: res 51/40:2f:a2:01:b2/00:02:e7:00:00/e0 Emask 0x9 (media error) Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:22:23 Aurora-NAS01 kernel: ata1: EH complete Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr0x0 action 0x0 Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: irq_stat 0x40000001 Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: failed command: READ DMA EXT Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: cmd 25/00:98:e8:5d:c3/00:01:e7:00:00/e0 tag 0 dma 208896 in Aug 14 18:23:14 Aurora-NAS01 kernel: res 51/40:37:47:5e:c3/00:01:e7:00:00/e0 Emask 0x9 (media error) Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:23:14 Aurora-NAS01 kernel: ata1: EH complete media errors are un-readable sectors on a disk. Post the output of the smartctl report for the disks involved. (parity disk, and both the cache disk and destination data disk) Quote Link to comment
WingmanNZ Posted August 14, 2011 Share Posted August 14, 2011 Just upgraded to 5b10 and now im getting these errors when the mover script is moving the data off the cache disk. the disk doesnt have and SMART status errors... anyone have any pointers? Aug 14 18:21:57 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:21:57 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:21:57 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:21:57 Aurora-NAS01 kernel: ata1: EH complete Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr0x0 action 0x0 Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: irq_stat 0x40000001 Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: failed command: READ DMA EXT Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: cmd 25/00:f0:e8:eb:b1/00:03:e7:00:00/e0 tag 0 dma 516096 in Aug 14 18:22:08 Aurora-NAS01 kernel: res 51/40:5f:70:ee:b1/00:01:e7:00:00/e0 Emask 0x9 (media error) Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:22:08 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:22:08 Aurora-NAS01 kernel: ata1: EH complete Aug 14 18:22:16 Aurora-NAS01 kernel: mdcmd (106): spindown 4 Aug 14 18:22:17 Aurora-NAS01 emhttp: shcmd (694): /usr/sbin/hdparm -y /dev/sdc &> /dev/null Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr0x0 action 0x0 Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: irq_stat 0x40000001 Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: failed command: READ DMA EXT Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: cmd 25/00:00:d8:ff:b1/00:04:e7:00:00/e0 tag 0 dma 524288 in Aug 14 18:22:23 Aurora-NAS01 kernel: res 51/40:2f:a2:01:b2/00:02:e7:00:00/e0 Emask 0x9 (media error) Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:22:23 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:22:23 Aurora-NAS01 kernel: ata1: EH complete Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr0x0 action 0x0 Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: irq_stat 0x40000001 Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: failed command: READ DMA EXT Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: cmd 25/00:98:e8:5d:c3/00:01:e7:00:00/e0 tag 0 dma 208896 in Aug 14 18:23:14 Aurora-NAS01 kernel: res 51/40:37:47:5e:c3/00:01:e7:00:00/e0 Emask 0x9 (media error) Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: status: { DRDY ERR } Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: error: { UNC } Aug 14 18:23:14 Aurora-NAS01 kernel: ata1.00: configured for UDMA/133 Aug 14 18:23:14 Aurora-NAS01 kernel: ata1: EH complete media errors are un-readable sectors on a disk. Post the output of the smartctl report for the disks involved. (parity disk, and both the cache disk and destination data disk) It looks like it might be my Parity disk or a cable. I do have both the Parity and Cache disk on 0.5m SATA cables. not sure if that would cause the issue. Here is a Pastebin of the SMART info form the parity disk. http://pastebin.com/SEtXz41A below is the SMART info for the Parity disk and the images below for disk info. Note the errors on the Parity. Screenshot (part1) Screenshot (part2) Quote Link to comment
Joe L. Posted August 14, 2011 Share Posted August 14, 2011 Those on the mgmt console are "read" errors. The smart report shows 190 sectors have been re-allocated. That disk is starting to fail. Granted, there are usually several thousand spare sectors, but once it starts getting up there, it is just a matter of time: Reallocated_Sector_Ct 0x0033 176 176 140 Pre-fail Always - 190 Current normalized value is 176. Failure threshold = 140. The normal initialized starting point is typically 200. You are half way there before the SMART report shows a failed drive. Quote Link to comment
WingmanNZ Posted August 14, 2011 Share Posted August 14, 2011 Those on the mgmt console are "read" errors. The smart report shows 190 sectors have been re-allocated. That disk is starting to fail. Granted, there are usually several thousand spare sectors, but once it starts getting up there, it is just a matter of time: Reallocated_Sector_Ct 0x0033 176 176 140 Pre-fail Always - 190 Current normalized value is 176. Failure threshold = 140. The normal initialized starting point is typically 200. You are half way there before the SMART report shows a failed drive. thanks for the heads up. on those "read" errors, are they from the reallocated sectors? Looks like i might get the drive replaced as its not that old (bought it about 3 1/2 months ago) what would be the cause of the high "read" errors? any further info you might need from me? thanks so much for your help Joe much appreciated. Quote Link to comment
dgaschk Posted August 14, 2011 Share Posted August 14, 2011 Yes. This drive is probably is the source of your problems. RMA it. Quote Link to comment
WingmanNZ Posted August 14, 2011 Share Posted August 14, 2011 Yes. This drive is probably is the source of your problems. RMA it. thanks to both yourself and Joe! will RMA tomorrow at least its only the parity drive Quote Link to comment
Nezil Posted August 15, 2011 Share Posted August 15, 2011 I foolishly messed up on my first fix for Lion Sidebar SMB Shares. I've gone through it again and updated the thread with a fix that does actually work this time. Just posting here again for Tom and others to see, and in the hope that the fix can be integrated into future builds for the Lion users among us. Fix can be found here: http://lime-technology.com/forum/index.php?topic=14623.msg138068#msg138068 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.