You can see the kernel log
dmesg | grep sda
<...>
[ 0.618438] sd 2:0:0:0: [sda] Attached SCSI disk
<...>
The log is talking about a scsi disk, and sd 2:0:0:0 is the device that generated that message. You can inspect the sysfs for more details:
cd /sys/block/
cd /sys/block/sda/
Here you can find the information about all your block devices. If you look into the directory of your specific device you should see its information.
Here the information about the scsi bus. There are two directories: drivers and devices.
cd /sys/bus/scsi
cd /sys/bus/scsi/devices
cd /sys/bus/scsi/drivers
Here there is the list of drivers on the scsi bus.
ls /sys/bus/scsi/drivers
sd sr
The log said sd 2:0:0:0
cd /sys/bus/scsi/drivers/sd/2:0:0:0
Here my device, so sd is my driver.
The disk is a block device, you should see the directory block
cd /sys/bus/scsi/drivers/sd/2:0:0:0/block/sda
Probably there is a program that do this automatically :)
If the wrong driver is handling your device you can unbind the device from that driver, and you can bind it to another one.
ls /sys/bus/scsi/drivers/sd
2:0:0:0 bind uevent unbind
You can write the device identifier on the unbind file to detach that device from the driver.
echo -n "2:0:0:0" > unbind
Then you can attach your device to another driver
cd /sys/bus/scsi/drivers/<a-driver>
echo -n "2:0:0:0" > bind
Obviously (1), you cannot bind a scsi device to non scsi driver.
Obviously (2), this is not the answer for your specific problem, but it is a way to retrieve the information that you need to resolve the problem