You have a SATA hard drive.
The reason that you are seeing IDE in there is actually quite simple: SATA can operate in one of two modes, AHCI
or IDE
.
Your controller appears to be in the IDE mode at the moment, as you can clearly see from the command output:
SATA Controller [IDE mode]
As for the difference between the two modes:
Only 2 major differences between AHCI and IDE mode.
AHCI allows for hot swapping of hard drives if the motherboard chipset
also supports it, and it also enables NCQ for hard drives if
they support it. IDE mode does not allow for either of these
functions.
There is a small hard drive performance hit when you use IDE mode due
to NCQ being disabled.
Intel PDf's on the AHCI standard if you wish to do some reading
The above quote is from this answer on Superuser.
And here's some more info about the difference between the two modes from the Crucial forums:
Depending on your system, multiple SATA controller modes may be
available in your BIOS or UEFI to manage how an SSD operates with the
rest of your system.
AHCI (Advance Host Controller Interface): The
modern standard for SATA controller operation, this provides the best
performance possible with a SATA storage device, combined with the
best support for features to optimize an SSD's performance, such as
TRIM. We recommend this mode for a majority of our users, and only
deviating from this if needed for addressing compatibility and
software problems.
IDE (Integrated Drive Electronics): A legacy
standard dating back to the 1990s. Due to slower performance and worse
support for modern hardware, we don't suggest using this mode over
AHCI. An exception to this is if you are using an older system missing
AHCI support, or are experiencing system instability using an SSD in
another mode and need to use this mode for compatibility/testing
purposes.
Note that the above modes may be reference differently by
some motherboards, such as AHCI being called "Serial ATA" or IDE being
labelled "Legacy" or just "ATA." If your SATA modes are not described
in an obvious way, please refer to your system or motherboard
documentation for clarification
.
Best Answer
lsscsi --verbose will provide output similar to this:
which provides the
ataN
port which can matchup with information found in the syslog. Useful if you are trying to determine where an error is coming from .Edit: If
which lsscsi
provides no output you need to install it:Further Edit:
This probably goes without saying, but of course you can filter the output with
grep
to locate what you are interested in for instance if you find an error likeata4: status: { DRDY ERR }
you could simple issue the commandWhich would indicate that the device (Optiarc DVD RW AD-7280S on ata4) wasn't ready when called upon.
This should be enough information to allow you to locate the troubled device.