04-18-2017 01:55 PM
I'm trying to replace my DVD drive with an SSHD and can't get it to work. Are there any known limitations on what is supported?
I already tried two different adapter cages to put an additional hard drive in the dvd slot.
At first I tried a Seagate FireCuda 2TB which is not recognized most of the times. I got it to work one or twice but don't know how. It always was after I suspended and then resumed the laptop, never after a reboot.
If I replace the stock SSD with the FireCuda the drive is recognized. But the SSD is not recognized when I connect it to the optical drive connector.
I also tried to use an old WD Scorpio Blue 500GB HDD and it works when connected to the optical drive connector.
Why is this so complicated? What can I do about it?
I'm running Ubuntu 16.04 LTS.
22:50 $ dmesg | grep -i ata
[ 0.000000] BIOS-e820: [mem 0x000000008d259000-0x000000008d2fefff] ACPI data
[ 0.000000] NODE_DATA(0) allocated [mem 0x26eff6000-0x26effafff]
[ 0.000000] Memory: 7984780K/8302348K available (8452K kernel code, 1293K rwdata, 3976K rodata, 1484K init, 1316K bss, 317568K reserved, 0K cma-reserved)
[ 0.156296] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20150930/psobject-227)
[ 0.171072] _OSC request data:1 1f 0
[ 0.193337] ACPI : EC: GPE = 0x50, I/O: command/status = 0x66, data = 0x62
[ 0.193611] libata version 3.00 loaded.
[ 0.827987] Write protecting the kernel read-only data: 14336k
[ 0.881343] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[ 0.881990] ata1: SATA max UDMA/133 abar m2048@0xb122c000 port 0xb122c100 irq 123
[ 0.881993] ata2: SATA max UDMA/133 abar m2048@0xb122c000 port 0xb122c180 irq 123
[ 1.200547] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.203092] ata1.00: ATA-9: SAMSUNG MZYLN256HCHP-000L2, EMT63L0Q, max UDMA/133
[ 1.203095] ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.204682] ata1.00: configured for UDMA/133
[ 1.205309] scsi 0:0:0:0: Direct-Access ATA SAMSUNG MZYLN256 3L0Q PQ: 0 ANSI: 5
[ 1.216422] ata2: SATA link down (SStatus 4 SControl 300)
[ 7.194854] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 7.391299] systemd: Listening on LVM2 metadata daemon socket.
As you can see ata2 simply turns down the link and does not come up.
Why is it so? What can I do? If I buy a standard HDD (no SSHD like FireCude) will it work?
I'm really frustrated right now!
04-19-2017 12:44 AM
I'm trying to replace my DVD drive with an SSHD and can't get it to work. Are there any known limitations on what is supported? ... I also tried to use an old WD Scorpio Blue 500GB HDD and it works when connected to the optical drive connector.
I have a 500-15ISK, but it is not my primary system so I have never tried to update the disk or DVD. From reading threads on this web site over many months, my recollection is:
(1) Users have found that the DVD SATA connection does not work with disks bigger than 1 TB.
(2) Many disk caddies that replace the DVD don't work at all.
(3) The DVD SATA connection is only SATA 2, and not SATA 3. If you put a HDD in the DVD location, you may not notice this difference (except when running benchmark tests). But replacing the DVD with an SSD would probably be a bad idea (you would notice the difference in performance).
This is based only on my recollection; I cannot direct you to the relevant threads. Please be aware that my recollection may be faulty!
-- from CyberSimian in the UK
04-19-2017 02:38 AM - edited 04-19-2017 02:40 AM
Well, somtimes the 2TB disc is recognized, so I assume it should be possbile somehow to get this thing running.
Yes, I also heard that some caddies might not work. But the same caddy works with no problems at all with my old Lenovo G560. (with the 2TB FireCuda installed)
Performance is not so much an issue for me. I just need more space for backups. I recognized that the 500GB drive always uses SATA2. But even if I use libata.force=3.0 or even 1.5 to force linux to use SATA2/1 the FireCuda is not recognized.
To put the SSD in the DVD slot was just a try to see if it is an issue with disc size. Last night I even put my old Samsung 830 128GB SSD in the caddy and it didn't work.
So my current guess is, that there is something wrong with
a) newer hard drives in general or
b) drives that utilize SSD
If I get out of work soon enough today I'll ask at a local store if they have a standard 2TB HDD to test or which I can return if it does not work.