March 12, 201214 yr I have a 400G ATA drive (Seagate Barracuda ST3400832A) that I'm trying to add to my array. I've precleared it but am getting all sorts of errors related to it in my syslog and my attempts have been unsuccessful to date. Log file is attached. syslog.txt
March 12, 201214 yr Author As requested: [font=courier]smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) === START OF INFORMATION SECTION === Device Model: [No Information Found] Serial Number: [No Information Found] Firmware Version: [No Information Found] Device is: Not in smartctl database [for details use: -P showall] ATA Version is: [No Information Found] ATA Standard is: [No Information Found] Local Time is: Mon Mar 12 09:18:59 2012 EDT SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled. A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. terminate called after throwing an instance of 'int' Aborted root@unraid:~#[/font]
March 12, 201214 yr Author I used: smartctl --all -T permissive /dev/hda The other version returns: root@unraid:/boot# smartctl -d ata -a /dev/hda smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. terminate called after throwing an instance of 'int' Aborted root@unraid:/boot# The drive is connected via standard IDE.
March 12, 201214 yr Author I don't know what you mean by "does it show up in the BIOS?" Can you be more specific. I don't have the jumper information at the moment. I'll confirm and add a reply.
March 14, 201214 yr I don't know what you mean by "does it show up in the BIOS?" Can you be more specific. I don't have the jumper information at the moment. I'll confirm and add a reply. When booting, hit whatever key you need to get into the BIOS. Does the IDE disk show in the list of disks connected? (can you see its model/serial number in the list of possible boot devices?) If not seen by the BIOS, the OS will never see it. In other words, it might have a bad cable, or no power, or be a dead drive, and BIOS will not see it, and neither will unRAID once it starts.
March 14, 201214 yr Author The device is definitely visible in the OS and in the unRAID Server, so this is not an issue. It shows up in the dropdown to add it to the array - but fails if I attempt actually to add it (it can be added to the array, then I get the "new disk" warning. If I check the "I want to to this" box to acknowledge that the disk might be cleared, and press start, I'm returned to the "new disk" warning page, with a bunch of errors in syslog (attached). syslog-2012-03-13.txt
March 14, 201214 yr The device is definitely visible in the OS and in the unRAID Server, so this is not an issue. It shows up in the dropdown to add it to the array - but fails if I attempt actually to add it (it can be added to the array, then I get the "new disk" warning. If I check the "I want to to this" box to acknowledge that the disk might be cleared, and press start, I'm returned to the "new disk" warning page, with a bunch of errors in syslog (attached). The errors all point to communications issues with the disk. Did you use the proper cable. I see CRC errors in the syslog, that lead me to think you used a cable that is not rated for the speed used to communicate with the disk. The older IDE cables were 40 conductor, and are used to connect to floppy drives or CD drives. The newer, and higher speed cables are 80 conductor and are rated to communicate with disk-drives. In most cases they have a blue, gray, and black connector. The three connectors are typically different colors and attach to specific items: The blue connector attaches to the motherboard. The black connector attaches to the primary, or master, drive. The gray connector attaches to the secondary, or slave, drive. If you only have one disk (the "primary/master") it must be connected to the end of the cable (the black connector) See here for more info: http://www.mikeshardware.com/howtos/howto_connect_ide_hd.html I have a feeling you might have used a 40 conductor cable. Joe L.
March 14, 201214 yr Author Thanks, Joe, that could be. It's a pretty old box - circa 2005. I'm not at home but I'll take a look at that.
March 15, 201214 yr Author Joe, it turns out that the hard drive was already connected to the last (end) connector of an 80-conductor ribbon cable, as it was supposed to be, so that's not it. Any other thoughts?
March 19, 201214 yr Author Someone asked for the preclear reports from the IDE drive. I've attached them. preclear_start__No_Information_Found_2012-03-12.txt preclear_finish__No_Information_Found_2012-03-12.txt preclear_finish__No_Information_Found_2012-03-12.txt
Archived
This topic is now archived and is closed to further replies.