Jump to content

GK20

Members
  • Content Count

    351
  • Joined

  • Last visited

Community Reputation

0 Neutral

About GK20

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Hi I purchased a 2nd key back to 2015 during promotion and recently i would like to exercise this order i had sent 3 email with new USB GUID to Lime Tech. How far no response Can anyone in Lime Tech check and reply with my new server key? My email address is in my profile. Thanks Order information: Invoice No.: 12897 Order No.: 260932611 Date: 01/04/2015
  2. GK20

    ONE year warranty?

    Good to know your pencil can help you record bits and bytes generated from CPU. WD at least still provides 2 years although no one knows how soon WD will follow Seagate. >> For Western Digital, warranties for the Caviar Blue, Caviar Green and Scorpio Blue hard drives will be reduced to two years from three years. http://bits.blogs.nytimes.com/2011/12/20/seagate-wd-storage-warranty/
  3. GK20

    ONE year warranty?

    [in a more radical move, Seagate will also be changing its warranty policy from five years to one year for certain desktop and notebook drives, such as the Barracuda and Barracuda Green 3.5-inch drives and the Momentus 2.5-inch (5400 and 7200rpm)] Really? Should we kiss Seagate goodbye? https://www.computerworld.com/s/article/9222760/Hard_drive_manufacturers_slash_warranty_periods
  4. http://www.tomshardware.com/reviews/ssd-reliability-failure-rate,2923.html#xtor=RSS-182
  5. I think once user disable spinup group in Setting, regardless how disks were assigned into groups. unRAID should totally ignore them. otherwise what is the purpose of "disable" spin-up group. i have similar issues, all disks connected to my 8-ports Supermicro controller are assigned to same spin-up group and even i disable spinup group i still see some disks were spun up without reason not even at same share when i was accessing others.
  6. Good point. You can check the MD5 with the windows tool MD5check, found here: http://www.softpedia.com/get/System/File-Management/MD5-Check.shtml MD5 is now known to be "weak" for anti-tampering in message digest, most are moving to SHA1 or SHA2, as this article indicated. http://tools.cisco.com/security/center/viewAlert.x?alertId=17341 Many open source packages distributing online now use either SHA1 or PGP signature.
  7. those high counts in udma_crc_error_count looks to me is not normal. Usually high number in this counter signal you have many link reset/timeout. you might want to check out those cables.
  8. Feb 9 15:32:14 MediaServer kernel: ata8.01: ATA-8: WDC WD20EADS-00S2B0, 01.00A01, max UDMA/133 Feb 9 15:32:14 MediaServer kernel: ata8.01: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) Feb 9 15:32:14 MediaServer kernel: ata8.01: configured for UDMA/100 Feb 9 15:32:14 MediaServer emhttp: pci-0000:02:00.0-scsi-0:0:0:0 host2 (sdi) WDC_WD20EADS-00S2B0_WD-WCAVY1606662 Feb 9 15:32:14 MediaServer emhttp: pci-0000:02:00.0-scsi-0:1:0:0 host2 (sdj) WDC_WD20EADS-00S2B0_WD-WCAVY1937974
  9. Assuming you had two IDE disks at same cable. after you replaced one with SATA, Do you adjust master/slave selection on the only IDE disk in your system right now? http://www.seagate.com/ww/v/index.jsp?vgnextoid=81d0198cdc9ef010VgnVCM100000f5ee0a0aRCRD&locale=en-US&reqPage=Legacy
  10. root@TestTower:~# ls /dev/disk/by-path pci-0000:00:1a.7-usb-0:6:1.0-scsi-0:0:0-lun-0x0000000000000000@ pci-0000:01:00.0-sata-0-part1@ pci-0000:00:1a.7-usb-0:6:1.0-scsi-0:0:0-lun-0x0000000000000000-part1@ pci-0000:01:00.0-sata-1@ pci-0000:00:1f.2-ata-1@ pci-0000:01:00.0-sata-1-part1@ pci-0000:00:1f.2-ata-1-part1@ pci-0000:01:00.1@ pci-0000:01:00.0-sata-0@ pci-0000:01:00.1-part1@ root@TestTower:~# cat /proc/partitions major minor #blocks name 8 0 488386584 sda 8 1 488386552 sda1 8 16 3921919 sdb 8 17 3919841 sdb1 3 0 488386584 hda 3 1 488386552 hda1 3 64 488386584 hdb 3 65 488386552 hdb1 8 32 732574584 sdc 8 33 732574552 sdc1 8 48 488386584 sdd 8 49 488386552 sdd1 root@TestTower:~# ------------------------------------- Update ------------------------------------------------------------------------------------------- reverse back to 5.0Beta2 everything back to normal after reassign back all disks, CPU temperature reading is also back.
  11. yes this test system worked fine at 5.0-beta2. besides, hdb although detected but doesn't show up at inventory table either.
  12. hda is missing. 5 disks in my test system, sda,sdb,sdc, hda and hdb. i guess unRAID mistaken hdb as sdd? from syslog: Feb 1 07:55:51 TestTower emhttp: Device inventory: Feb 1 07:55:51 TestTower emhttp: pci-0000:00:1f.2-ata-1 host1 (sda) ST3500320AS_5QM142BB Feb 1 07:55:51 TestTower emhttp: pci-0000:01:00.0-sata-0 host4 (sdb) ST3750330AS_3QK0601L Feb 1 07:55:51 TestTower emhttp: pci-0000:01:00.0-sata-1 host5 (sdc) WDC_WD5000AAKS-_WD-WCAS82576893 ------------------------------------------------------------------------------------------------------------------------------------------------ root@TestTower:~# ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 9 Feb 1 07:55 pci-0000:00:1a.7-usb-0:6:1.0-scsi-0:0:0-lun-0x0000000000000000 -> ../../sdd lrwxrwxrwx 1 root root 10 Feb 1 07:55 pci-0000:00:1a.7-usb-0:6:1.0-scsi-0:0:0-lun-0x0000000000000000-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Feb 1 07:55 pci-0000:00:1f.2-ata-1 -> ../../sda lrwxrwxrwx 1 root root 10 Feb 1 07:55 pci-0000:00:1f.2-ata-1-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Feb 1 07:55 pci-0000:01:00.0-sata-0 -> ../../sdb lrwxrwxrwx 1 root root 10 Feb 1 07:55 pci-0000:01:00.0-sata-0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Feb 1 07:55 pci-0000:01:00.0-sata-1 -> ../../sdc lrwxrwxrwx 1 root root 10 Feb 1 07:55 pci-0000:01:00.0-sata-1-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Feb 1 07:55 pci-0000:01:00.1 -> ../../hdb lrwxrwxrwx 1 root root 10 Feb 1 07:55 pci-0000:01:00.1-part1 -> ../../hdb1
  13. CPU temperature reading is missing from "CPU info" at unmenu at 5.0-beta3, no problem at 5.0-beta2. Syslog shown following messages, looks like sensor driver has been removed at 5.0beta3? Feb 1 00:09:55 TestTower unmenu[1187]: Try sensors-detect to find out which these are. Feb 1 00:10:02 TestTower unmenu[1187]: No sensors found! Feb 1 00:10:02 TestTower unmenu[1187]: Make sure you loaded all the kernel drivers you need.
  14. upgrade from 5.0-beta2. as following screen captures shown unraid can not detect IDE disks, no issue at 5.0-beta2. Device list from webGui shown no IDE disks however list from unmenu shown all disks. MB : MSI P43 Neo3-F Syslog shown system had successfully detcted both IDE disks, so looks like a presentation issue in webgui? Jan 31 23:53:37 TestTower kernel: scsi6 : usb-storage 1-6:1.0 Jan 31 23:53:37 TestTower kernel: hda: WDC WD5000AAJB-00UHA0, ATA DISK drive Jan 31 23:53:37 TestTower kernel: ata3: SATA link down (SStatus 0 SControl 300) Jan 31 23:53:37 TestTower kernel: ata4: SATA link down (SStatus 0 SControl 300) Jan 31 23:53:37 TestTower kernel: usb 4-2: new full speed USB device using uhci_hcd and address 2 Jan 31 23:53:37 TestTower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 31 23:53:37 TestTower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 31 23:53:37 TestTower kernel: ata5.00: ATA-8: ST3750330AS, SD35, max UDMA/133 Jan 31 23:53:37 TestTower kernel: ata5.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 31/32) Jan 31 23:53:37 TestTower kernel: ata5.00: configured for UDMA/133 Jan 31 23:53:37 TestTower kernel: ata6.00: ATA-8: WDC WD5000AAKS-00YGA0, 12.01C02, max UDMA/133 Jan 31 23:53:37 TestTower kernel: ata6.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Jan 31 23:53:37 TestTower kernel: ata6.00: configured for UDMA/133 Jan 31 23:53:37 TestTower kernel: hdb: MAXTOR STM3500630A, ATA DISK drive
  15. Jan 10 19:00:05 Tower kernel: attempt to access beyond end of device Jan 10 19:00:05 Tower kernel: md15: rw=0, want=27487790696, limit=1953525104 Jan 10 19:00:05 Tower kernel: REISERFS error (device md15): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1294 1301 0x0 SD] Jan 10 19:00:05 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 52428 does not match to the expected one 1 Jan 10 19:00:05 Tower kernel: REISERFS error (device md15): vs-5150 search_by_key: invalid format found in block 176063846. Fsck? Jan 10 19:00:05 Tower kernel: REISERFS error (device md15): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1380 1248 0x0 SD] Jan 10 19:00:08 Tower cache_dirs: killing cache_dirs process 2409 parity checking is at disk block level. You should perform file system check on md15 disk. looks to me, you might have file system corruption. http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems