July 5, 201016 yr I have just finished creating my unraid server, here is my Hardware - Asus P5Q Premium board 4 GB Ram 2x Supermicro AOC-SASLP-MV8 12x Samsung 1.5tb Ecogreen Spinpoint drives 1x Seagate 7200.11 1.5tb Drive - Cache Drive Everything is working great, but this error is filling my syslogs... Jul 5 10:38:48 Tower ata_id[22977]: HDIO_GET_IDENTITY failed for '/dev/block/8:32' Jul 5 10:38:48 Tower ata_id[22989]: HDIO_GET_IDENTITY failed for '/dev/block/8:48' Jul 5 10:38:48 Tower ata_id[23001]: HDIO_GET_IDENTITY failed for '/dev/block/8:64' Jul 5 10:38:48 Tower ata_id[23013]: HDIO_GET_IDENTITY failed for '/dev/block/8:80' Jul 5 10:38:48 Tower ata_id[23025]: HDIO_GET_IDENTITY failed for '/dev/block/8:96' Jul 5 10:38:48 Tower ata_id[23037]: HDIO_GET_IDENTITY failed for '/dev/block/8:112' Everything seems to be running fine, but I have no idea what that error is, and it is filling my syslog. I have the cache drive and 5 of the samsungs hooked right up to the sata ports on the motherboard, and then the rest are hooked to the supermicro cards. I have attached the syslog, any ideas? syslog-2010-07-05.zip
July 18, 201015 yr Can't help you with your question I'm afraid, but I was wondering how you like the motherboard and Sata controllers? I am currently awaiting delivery of the very same motherboard and controllers. From what I have seen and read they work great with unraid. Have you had any problems are are there any tips or tricks? Have you hooked any drives up to the Drive Xpert SATA ports? If so, does it present a single drive to the OS, or does the OS see the separate drive? What case are you using out of interest? I am using a Norco 4020 with replacement Mini SAS SFF-8087 backplanes. (The case is an early model so the SATA ports were really spaced out. 5 SAS cables will make life much easier than 20 SATA cables).
August 2, 201015 yr yaknow, if you do a quick search of limetech or even google youll realise its just the mv sas driver failing to pass through a non critical command.
August 2, 201015 yr That error is nothing to worry about. Everyone using the AOC-SASLP-MV8 gets the same error.
Archived
This topic is now archived and is closed to further replies.