abeta

Members
  • Posts

    270
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

abeta's Achievements

Contributor

Contributor (5/14)

0

Reputation

  1. I'm reading the instructions here: http://lime-technology.com/wiki/index.php/Upgrading_to_UnRAID_v6#Upgrade_or_Clean_Install.3F I'm trying to understand the part about preparing the drive. I'm on unRaid 5.06 and everything is running. Do I actually need to physically pull my flash drive and put it into my Windows machine and run the format, make-bootable, etc? I'm pretty sure I did that a long time time ago and I've just been copying the bzimage/bzroot files to upgrade in the past to \\serenity\flash (serenity is the name of my server).
  2. I have a CleverBox 16 as a ESXi server that is running unRAID as a VM. Very prompt and courteous service before, during and after the delivery of my CleverBox16. I can't say it is stone silent but its much better than most and I'd buy another system from them when it comes time for me upgrade or buy another unit.
  3. FYI, I turned off the spinup/spindown on 9/27. No errors of any sort since then. I've emailed Lime Technology a link to this thread a few days ago, hopefully he'll look in or at respond to my email. No response yet.
  4. I've emailed Tom this thread link and asked him if he wanted to test something, etc. I'll set the timeouts to a very large value when I get home tonight. Spindown is a feature I really like so hopefully it'll get fixed/resolved to my liking . Thanks everyone. If there's other things you want me to show/display feel free to let me know. Appreciate all of the help!
  5. Ack. I'm not really concerned at the moment as long as no one here was screaming OMG everything is about to blow up I think its probably normal or as close to normal. I'm currently migrating my old unRAID machine to this so I've got a backup if things start acting up.
  6. I dont have much experience with unRAID and SAS drives either . The one time I tried SCSI drives with a 3Ware controller I recalled it was a very similar experience. No drive temps and a variety of errors similar to this. I didn't get much help from Lime Technology back then as I don't think it was really supported and I was just playing around with it so I never pursued it. Precleared and burned in. The system is actually running ESXi with unRAID and the LSI as a pass-through. A good friend of mine is the GM of a reseller/VAR that my company deals with. I got it at a huge discount for services rendered and I his guarantee of service in the event of drive failure. I hate doing RMAs for drives in general so that was the real benefit to me. I think it cost me just a little more than SATA drives would have run me with no hassles so I didn't really care what brand/make/etc it was as long as he didn't care.
  7. They supplied the Norco cages and tested one of the SAS drives. I put in the SAS drives when I got it there. Everything was trayless to the Norco cages as they support SAS/SATA. I could probably use some ventilation in that corner of the office .
  8. It's a Greenleaf Technology Cleverbox 16. I'll shoot them a note and they can comment on all of the inner workings I'm sure. The rest of the info that you requested is posted below. ETA: http://greenleaf-technology.com/types-of-servers/silent-servers/ That might be pictures of my 16 . ABSOLUTELY PLEASED WITH GREENLEAF. Just wanted to get it down on the thread and then ask Lime Tech about it Alpha login: root Linux 3.9.6p-unRAID. root@Alpha:~# hdparm -I /dev/sdd /dev/sdd: SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 HDIO_DRIVE_CMD(identify) failed: Input/output error root@Alpha:~# hdparm -H /dev/sdd /dev/sdd: SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 HDIO_DRIVE_CMD(hitachisensecondition) failed: Input/output error root@Alpha:~# smartctl --all /dev/sdd smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Device: SEAGATE ST33000650SS Version: 0003 Serial number: Z292AZWL000092350KUC Device type: disk Transport protocol: SAS Local Time is: Wed Sep 25 17:32:18 2013 EDT Device supports SMART and is Enabled Temperature Warning Enabled SMART Health Status: OK Current Drive Temperature: 48 C Drive Trip Temperature: 68 C Manufactured in week 13 of year 2012 Specified cycle count over device lifetime: 10000 Accumulated start-stop cycles: 287 Specified load-unload count over device lifetime: 300000 Accumulated load-unload cycles: 287 Elements in grown defect list: 0 Vendor (Seagate) cache information Blocks sent to initiator = 730488606 Blocks received from initiator = 778098224 Blocks read from cache and sent to initiator = 76648815 Number of read and write commands whose size <= segment size = 3341096 Number of read and write commands whose size > segment size = 19769 Vendor (Seagate/Hitachi) factory information number of hours powered up = 2832.42 number of minutes until next internal SMART test = 2 Error counter log: Errors Corrected by Total Correction Gigabytes Total ECC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 3761518176 0 0 3761518176 0 4157.876 0 write: 0 0 0 0 0 398.608 0 Non-medium error count: 168 [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on'] No self-tests have been logged Long (extended) Self Test duration: 27600 seconds [460.0 minutes] root@Alpha:~#
  9. Alpha login: root Linux 3.9.6p-unRAID. root@Alpha:~# cd /boot root@Alpha:/boot# installpkg hdparm-9.43-i486-1_pourko.txz Verifying package hdparm-9.43-i486-1_pourko.txz. Installing package hdparm-9.43-i486-1_pourko.txz: PACKAGE DESCRIPTION: # hdparm (read/set hard drive parameters) # # hdparm provides a command line interface to various hard disk ioctls # supported by the Linux ATA/IDE device driver subsystem. This may be # required to enable higher-performing disk modes. # # hdparm was written by Mark Lord. # Executing install script for hdparm-9.43-i486-1_pourko.txz. Package hdparm-9.43-i486-1_pourko.txz installed. root@Alpha:/boot# hdparm -y /dev/sdd /dev/sdd: issuing standby command SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 HDIO_DRIVE_CMD(standby) failed: Input/output error root@Alpha:/boot#
  10. root@Alpha:/boot# ls hdparm-9.43-i486-1_pourko.txz hdparm-9.43-i486-1_pourko.txz* root@Alpha:/boot# upgradepkg -install-new hdparm-9.43-i486-1_pourko.txz Cannot install -install-new: file not found Error: there is no installed package named hdparm-9.43-i486-1_pourko. (looking for /var/log/packages/hdparm-9.43-i486-1_pourko) root@Alpha:/boot# No temperature readings but I thought that might be normal as I've tried SCSI drives before along time ago and I don't remember temps. Looks like the file is there? ETA: If I'm reading it correctly from Pourko...it's expected? .
  11. root@Alpha:~# hdparm -V hdparm v9.37 root@Alpha:~# Looks like -Y is to try to put it to sleep. Lemme try now. Console output: /dev/sdd: issuing sleep command SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 HDIO_DRIVE_CMD(sleep) failed: Input/output error root@Alpha:~# Nothing in the syslog to match.
  12. /dev/sdd: issuing standby command SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 HDIO_DRIVE_CMD(standby) failed: Input/output error This is the error on the terminal console. I don't see it in the syslog. Syslog attached. I'm aware that I need to remove Simple Features as it isn't fully supported but I'm in the midst of a very long copy and haven't gotten to it yet . syslog-2013-09-24.zip
  13. I'm seeing a lot of these "errors". A quick search through the forums seeems to be mixed as to whether it is a problem or not. I'm running on unRaid 5.0 with SAS drives and the "errors" seem to occur when it is spinning down. Is this normal since they're SAS drives and basically a false positive or is there something else going on? Sep 24 01:29:31 Alpha kernel: mdcmd (81): spindown 3 (Routine) Sep 24 01:29:31 Alpha kernel: md: disk3: ATA_OP e0 ioctl error: -5 (Errors) Sep 24 02:27:12 Alpha emhttp: mdcmd: write: Input/output error (Errors) Sep 24 02:27:12 Alpha kernel: mdcmd (82): spindown 6 (Routine) Sep 24 02:27:12 Alpha kernel: md: disk6: ATA_OP e0 ioctl error: -5 (Errors) Sep 24 03:30:42 Alpha emhttp: mdcmd: write: Input/output error (Errors) Sep 24 03:30:42 Alpha kernel: mdcmd (83): spindown 3 (Routine) Sep 24 03:30:42 Alpha kernel: md: disk3: ATA_OP e0 ioctl error: -5 (Errors) Sep 24 04:51:52 Alpha emhttp: mdcmd: write: Input/output error (Errors) Sep 24 04:51:52 Alpha kernel: mdcmd (84): spindown 3 (Routine) Sep 24 04:51:52 Alpha kernel: md: disk3: ATA_OP e0 ioctl error: -5 (Errors) Sep 24 04:52:02 Alpha emhttp: mdcmd: write: Input/output error (Errors) Sep 24 04:52:02 Alpha kernel: mdcmd (85): spindown 4 (Routine) Sep 24 04:52:02 Alpha kernel: md: disk4: ATA_OP e0 ioctl error: -5 (Errors) Sep 24 04:52:22 Alpha emhttp: mdcmd: write: Input/output error (Errors) Sep 24 04:52:22 Alpha kernel: mdcmd (86): spindown 6 (Routine) Sep 24 04:52:22 Alpha kernel: md: disk6: ATA_OP e0 ioctl error: -5 (Errors) Sep 24 10:02:14 Alpha emhttp: mdcmd: write: Input/output error (Errors) Sep 24 10:02:14 Alpha kernel: mdcmd (87): spindown 4 (Routine) Sep 24 10:02:14 Alpha kernel: md: disk4: ATA_OP e0 ioctl error: -5 (Errors) Sep 24 10:19:14 Alpha emhttp: mdcmd: write: Input/output error (Errors) Sep 24 10:19:14 Alpha kernel: mdcmd (88): spindown 1 (Routine) Sep 24 10:19:14 Alpha kernel: md: disk1: ATA_OP e0 ioctl error: -5 (Errors)
  14. Hello, I apologize for posting this in the forum but I haven't received an email response on a specific feature and was wondering if anyone had this unit and could comment on the following questions: 1-Noise level. It says quiet, is it relatively silent? 2-It says it supports "10 trayless 3.5" SAS/SATA drive bays". What doesn't this mean? Can I plug in SAS AND SATA in the different bays at the same time? Can I plug in a SAS drive with this connector (http://en.wikipedia.org/wiki/Serial_attached_SCSI) into the unit without a problem? Thank you very much.
  15. Python in the PKG Manager for unmenu doesn't seem to "stick" for me. I download it, install it then enable it for reboot, but upon reboot it shows as uninstalled? Is there a way to get the 2.7.5 version as well in the pkg manager? Thoughts on what I'm missing?