GT-AX6000 cannot recognize/mount SSD on USB 3.0 mode

[megamoz]

Hi,

I have just purchased GT-AX6000 to replace my old RT-AC3200. Among others, I also use my router to stream from USB attached SSD. So, I have Sandisk Ultra 3D 2TB SSD connected to the USB 3.0 port. the SSD has an USB 3.0 enclosure as well. Once attached the GT-AX6000 tries to read/recognize/mount this storage, but fails to do, so during which the GUI shortly freezes. This reading sequence never ends and the drive is not being mounted. The SSD is just fine, my computer recognizes it, there`s no error on it, already formatted to NTFS. I also have tried with Samsung SSD EVO 1 TB on USB 3.0 mode, it is not mounted. My old AC3200 didn't have this bug and mounted the disk straight away.
Then I decided to try to mount it on USB 2.0 mode, and it worked, the SSD was recognized.

In the system log, I get the following endless errors in the USB 3.0 mode. Do you have any idea of what causes this bug and solution?
Thanks very much.


May 25 22:32:07 kernel: scsi 1:0:0:0: Direct-Access ATA SanDisk SDSSDH3 20RL PQ: 0 ANSI: 6
May 25 22:32:07 kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
May 25 22:32:07 kernel: sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 25 22:32:07 kernel: sd 1:0:0:0: [sdb] Write Protect is off
May 25 22:32:07 kernel: sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 25 22:32:07 kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
May 25 22:32:08 Timemachine: daemon is stoped
May 25 22:32:08 avahi-daemon[7623]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 25 22:32:09 avahi-daemon[7623]: Alias name "GT-AX6000" successfully established.
May 25 22:32:32 kernel: print_req_error: I/O error, dev sdb, sector 66
May 25 22:32:32 kernel: buffer_io_error: 20 callbacks suppressed
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 17, async page read
May 25 22:32:32 kernel: print_req_error: I/O error, dev sdb, sector 130
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 18, async page read
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 19, async page read
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 17, async page read
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 18, async page read
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 19, async page read
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 17, async page read
May 25 22:32:32 Samba Server: daemon is started
May 25 22:32:32 rc_service: hotplug 7199:notify_rc restart_nasapps
May 25 22:32:32 rc_service: waitting "restart_nasapps" via ...
May 25 22:32:32 iTunes: daemon is stoped
May 25 22:32:32 FTP Server: daemon is stopped
May 25 22:32:32 wsdd2[7743]: Terminated received.
May 25 22:32:32 Samba Server: smb daemon is stopped
May 25 22:32:33 kernel: scsi 1:0:0:0: Direct-Access ATA SanDisk SDSSDH3 20RL PQ: 0 ANSI: 6
May 25 22:32:33 kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
May 25 22:32:33 kernel: sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 25 22:32:33 kernel: sd 1:0:0:0: [sdb] Write Protect is off
May 25 22:32:33 kernel: sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 25 22:32:33 kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
May 25 22:32:34 Timemachine: daemon is stoped
May 25 22:32:34 avahi-daemon[7867]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 25 22:32:35 avahi-daemon[7867]: Alias name "GT-AX6000" successfully established.
May 25 22:32:58 kernel: print_req_error: I/O error, dev sdb, sector 66
May 25 22:32:58 kernel: print_req_error: I/O error, dev sdb, sector 130
May 25 22:32:58 Samba Server: daemon is started
May 25 22:32:58 rc_service: hotplug 7752:notify_rc restart_nasapps
May 25 22:32:58 rc_service: waitting "restart_nasapps" via ...
May 25 22:32:58 iTunes: daemon is stoped
May 25 22:32:58 FTP Server: daemon is stopped
May 25 22:32:58 wsdd2[7999]: Terminated received.
May 25 22:32:58 Samba Server: smb daemon is stopped
May 25 22:32:59 kernel: scsi 1:0:0:0: Direct-Access ATA SanDisk SDSSDH3 20RL PQ: 0 ANSI: 6
May 25 22:32:59 kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
May 25 22:32:59 kernel: sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 25 22:32:59 kernel: sd 1:0:0:0: [sdb] Write Protect is off
May 25 22:32:59 kernel: sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 25 22:32:59 kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
May 25 22:33:00 Timemachine: daemon is stoped
May 25 22:33:00 avahi-daemon[8146]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 25 22:33:01 avahi-daemon[8146]: Alias name "GT-AX6000" successfully established.

 

[Crimliar]

I'm sure one of the more knowledgeable amongst us will be able to give you more details, but this looks like it's related to ASPI (Advanced SCSI Protocol Interface). This is a protocol which in part is supposed to give us more performance from our USB-attached SSDs - but too often just doesn't quite work properly. As you've already discovered use USB2 and the issue will disappear. On other systems, it's often possible to include commands during the boot process that will alleviate the issue.
*Using an Integral 120GB SSD (no need to tell me its performance sucks) on USB3 with no issues, but I have a Sandisk drive that will do exactly the same as you are seeing!

In case anyone wondered what the power drain on the SSD I'm using is

 

[megamoz]

I'm sure one of the more knowledgeable amongst us will be able to give you more details, but this looks like it's related to ASPI (Advanced SCSI Protocol Interface). This is a protocol which in part is supposed to give us more performance from our USB-attached SSDs - but too often just doesn't quite work properly. As you've already discovered use USB2 and the issue will disappear. On other systems, it's often possible to include commands during the boot process that will alleviate the issue.
*Using an Integral 120GB SSD (no need to tell me its performance sucks) on USB3 with no issues, but I have a Sandisk drive that will do exactly the same as you are seeing!

Actually, now USB 2.0 mode also produces the same error. So could it be the enclosure that causes all this fuss?

 

[ColinTaylor]

@Crimliar ASPI is the ancient Adaptec protocol from the 1990's. I think you're thinking of UAS/UASP which is part of the USB 3 improvements over USB 2.

Actually, now USB 2.0 mode also produces the same error. So could it be the enclosure that causes all this fuss?

The drive is being recognised but you appear to be getting random errors trying to read the information. Other than a basic incompatibility with the firmware, it could be a physical problem like a USB cable fault, RF interference, loose plug or socket, etc. Try a different USB cable and move the enclosure as far away from the router as possible.

 

[sfx2000]

May 25 22:32:32 kernel: print_req_error: I/O error, dev sdb, sector 66
May 25 22:32:32 kernel: buffer_io_error: 20 callbacks suppressed
May 25 22:32:32 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read

I suspect a bad cable at first glance...

Second would be a power issue, not enough current to the drive...

 

[megamoz]

Thank you for your replies. Let me add to what I wrote above, I just in case reformatted the SSD, recoppied the content, so SSD is fine.

I have another USB 2.0 casing of 1 TB SSD (Samsung EVO) which I also use it with my router. This time I put the 2TB SSD into this one, plugged it into Router's both USB 2.0 and USB 3.0 ports, both worked and the drive was recognized.

So, it could be the enclosure that is either incompatible with this router or lack of power issue. I decided to buy a new and more up-to-date casing, I'll see if it works.

 

[Tech9]

So, it could be the enclosure

It's usually controller issue with router port incompatibility. Most enclosures work with no issues when plugged into PC. I have some USB sticks with the same issue - they don't auto mount in USB3 mode after router boots. What I found works with routers is Ugreen and Orico USB-to-SATA enclosures, but manufacturers swap components all the time and it's still not guaranteed. You have to find what works for you.

 

[megamoz]

The new SSD enclosure (Sabrent) from Amazon was delivered yesterday. I connected it to the Router's USB 3.0 port and it was immediately recognized and mounted. Thank you all for your replies.

 

[Tech9]

The new SSD enclosure from Amazon was delivered yesterday.

Share the brand/model to help others with similar issues.