Hitachi Touro 2TB USB3 connected to TS-253 Pro

Printers, HDDs, USB/eSATA drives, 3rd-party programs
Post Reply
Kees66
Starting out
Posts: 20
Joined: Wed Sep 02, 2015 4:56 pm

Hitachi Touro 2TB USB3 connected to TS-253 Pro

Post by Kees66 »

Has anyone got this working? When I connect my Hitachi Touro 2tb USB3 external drive to my QNap TS-253 Pro it responds with 3 beeps and in the log I see the message "A drive has been detected but is inaccessible. Please check it for faults". The drive works fine when connected straight to my Windows machine or to my other (Synology) NAS so the drive itself is ok. I connected a different USB device (WD Elements USB2) to the same ports and that works fine also. So it seems a compatibility issue between the QNap system and the Hitachi Touro drive. On the compatibility list on the QNap site I only see the HGST Touro mobile 1tb drive as recommended but that list is very limited.

When I connect the drive to my system and run lsusb I very briefly see it appear with the following specifics:
Bus 002 Device 004: ID 4971:1013 SimpleTech
But as soon as I get the three beeps, it is gone again.

Anything I could try to get this working? I was hoping to use the USB disk for a daily backup...
User avatar
pwilson
Guru
Posts: 22533
Joined: Fri Mar 06, 2009 11:20 am
Location: Victoria, BC, Canada (UTC-08:00)

Re: Hitachi Touro 2TB USB3 connected to TS-253 Pro

Post by pwilson »

Kees66 wrote:Has anyone got this working? When I connect my Hitachi Touro 2tb USB3 external drive to my QNap TS-253 Pro it responds with 3 beeps and in the log I see the message "A drive has been detected but is inaccessible. Please check it for faults". The drive works fine when connected straight to my Windows machine or to my other (Synology) NAS so the drive itself is ok. I connected a different USB device (WD Elements USB2) to the same ports and that works fine also. So it seems a compatibility issue between the QNap system and the Hitachi Touro drive. On the compatibility list on the QNap site I only see the HGST Touro mobile 1tb drive as recommended but that list is very limited.

When I connect the drive to my system and run lsusb I very briefly see it appear with the following specifics:
Bus 002 Device 004: ID 4971:1013 SimpleTech
But as soon as I get the three beeps, it is gone again.

Anything I could try to get this working? I was hoping to use the USB disk for a daily backup...
Please provide output for:

Code: Select all

echo "Firmware: QTS $(getcfg system version) Build $(getcfg system 'Build Number')"
testparm -s -l --section-name=USBDisk1 --parameter-name=path 2>/dev/null
mount | grep external
df -h | grep external
dmesg
  1. What type of File System did you put on it? NTFS?
  2. How did you format it?
  3. Did you "label" the drive?

Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs

Please review: When you're asking a question, please include the following.
Kees66
Starting out
Posts: 20
Joined: Wed Sep 02, 2015 4:56 pm

Re: Hitachi Touro 2TB USB3 connected to TS-253 Pro

Post by Kees66 »

[~] # echo "Firmware: QTS $(getcfg system version) Build $(getcfg system 'Build Number')"
Firmware: QTS 4.2.0 Build 20150925
[~] # testparm -s -l --section-name=USBDisk1 --parameter-name=path 2>/dev/null
[~] # mount | grep external
[~] # df -h | grep external
[~] # dmesg
[ 731.772540] scsi5 : usb-storage 2-1.2:1.0
[ 742.778897] scsi 5:0:0:0: Direct-Access Hitachi Hitachi HDS72302 A5C0 PQ: 0 ANSI: 4
[ 742.787141] Check proc_name[usb-storage].
[ 742.791341] sd 5:0:0:0: Attached scsi generic sg4 type 0
[ 742.876612] sd 5:0:0:0: [sde] 3907024896 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 742.884713] usb 2-1.2: Disable of device-initiated U1 failed.
[ 742.890623] usb 2-1.2: Disable of device-initiated U2 failed.
[ 742.959131] usb 2-1.2: Device not responding to set address.
[ 743.165493] usb 2-1.2: Device not responding to set address.
[ 743.371462] usb 2-1.2: device not accepting address 4, error -71
[ 743.389991] usb 2-1.2: USB disconnect, device number 4
[ 743.395479] sd 5:0:0:0: [sde] Write Protect is off
[ 743.400281] sd 5:0:0:0: [sde] Mode Sense: 4b 00 10 08
[ 743.400333] sd 5:0:0:0: [sde] No Caching mode page found
[ 743.405652] sd 5:0:0:0: [sde] Assuming drive cache: write through
[ 743.413013] sd 5:0:0:0: [sde] READ CAPACITY failed
[ 743.417828] sd 5:0:0:0: [sde]
[ 743.420991] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 743.427043] sd 5:0:0:0: [sde] Sense not available.
[ 743.431918] sd 5:0:0:0: [sde] Asking for cache data failed
[ 743.437418] sd 5:0:0:0: [sde] Assuming drive cache: write through
[ 743.443514] sde: detected capacity change from 2000396746752 to 0
[ 743.449780] sd 5:0:0:0: [sde] READ CAPACITY failed
[ 743.454583] sd 5:0:0:0: [sde]
[ 743.457728] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 743.463735] sd 5:0:0:0: [sde] Sense not available.
[ 743.468571] sd 5:0:0:0: [sde] Asking for cache data failed
[ 743.474065] sd 5:0:0:0: [sde] Assuming drive cache: write through
[ 743.480198] sd 5:0:0:0: [sde] Attached SCSI disk
[ 743.486022] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88004b760680
[ 743.495082] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88004b760640
[21779.851044] PPP generic driver version 2.4.2
[21779.858836] PPP MPPE Compression module registered
[21779.865174] PPP BSD Compression module registered
[21779.871417] PPP Deflate Compression module registered
[21779.883234] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[23287.042688] Initializing XFRM netlink socket
[23287.057544] NET: Registered protocol family 15
[23287.076005] IPv6: ah6_init: can't add xfrm type
[23287.108390] IPv6: esp6_init: can't add xfrm type
[23287.188460] ipcomp6: Unknown symbol xfrm6_tunnel_alloc_spi (err 0)
[23287.194689] ipcomp6: Unknown symbol xfrm6_tunnel_spi_lookup (err 0)
[23287.289309] l2tp_core: L2TP core driver, V2.0
[23287.299023] l2tp_debugfs: L2TP debugfs support
[23287.309088] l2tp_netlink: L2TP netlink interface
[23287.318956] l2tp_eth: L2TP ethernet pseudowire support (L2TPv3)
[23287.371234] NET: Registered protocol family 24
[23287.386175] l2tp_ppp: PPPoL2TP kernel driver, V2.0
[27859.154657] NET: Unregistered protocol family 15
[28514.344299] usb 1-1.4: USB disconnect, device number 4
[28525.479280] usb 2-1.2: new SuperSpeed USB device number 5 using xhci_hcd
[28525.504080] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[28525.510783] scsi6 : usb-storage 2-1.2:1.0
[28536.517123] scsi 6:0:0:0: Direct-Access Hitachi Hitachi HDS72302 A5C0 PQ: 0 ANSI: 4
[28536.525656] Check proc_name[usb-storage].
[28536.529887] sd 6:0:0:0: Attached scsi generic sg3 type 0
[28536.717437] sd 6:0:0:0: [sdd] 3907024896 512-byte logical blocks: (2.00 TB/1.81 TiB)
[28536.725474] usb 2-1.2: Disable of device-initiated U1 failed.
[28536.731366] usb 2-1.2: Disable of device-initiated U2 failed.
[28536.799379] usb 2-1.2: Device not responding to set address.
[28537.005727] usb 2-1.2: Device not responding to set address.
[28537.211693] usb 2-1.2: device not accepting address 5, error -71
[28537.230169] usb 2-1.2: USB disconnect, device number 5
[28537.235769] sd 6:0:0:0: [sdd] Write Protect is off
[28537.240572] sd 6:0:0:0: [sdd] Mode Sense: 4b 00 10 08
[28537.240610] sd 6:0:0:0: [sdd] Asking for cache data failed
[28537.246103] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[28537.252445] sd 6:0:0:0: [sdd] READ CAPACITY failed
[28537.257257] sd 6:0:0:0: [sdd]
[28537.260405] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[28537.266413] sd 6:0:0:0: [sdd] Sense not available.
[28537.271388] sd 6:0:0:0: [sdd] Asking for cache data failed
[28537.276883] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[28537.282977] sdd: detected capacity change from 2000396746752 to 0
[28537.289229] sd 6:0:0:0: [sdd] READ CAPACITY failed
[28537.294027] sd 6:0:0:0: [sdd]
[28537.297169] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[28537.303178] sd 6:0:0:0: [sdd] Sense not available.
[28537.308003] sd 6:0:0:0: [sdd] Asking for cache data failed
[28537.313496] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[28537.319590] sd 6:0:0:0: [sdd] Attached SCSI disk
[28537.324955] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880064112d00
[28537.334020] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880064112cc0
[28634.906113] usb 2-1.2: new SuperSpeed USB device number 6 using xhci_hcd
[28639.924575] usb 2-1.2: Set SEL for device-initiated U1 failed.
[28639.933876] usb 2-1.2: Set SEL for device-initiated U2 failed.
[28639.939930] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[28639.946336] scsi7 : usb-storage 2-1.2:1.0
[28639.953879] usb 2-1.2: Set SEL for device-initiated U1 failed.
[28639.963123] usb 2-1.2: Set SEL for device-initiated U2 failed.
[28639.969449] usb 2-1.2: USB disconnect, device number 6
[28647.767085] usb 2-1.2: new SuperSpeed USB device number 7 using xhci_hcd
[28647.791937] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[28647.798892] scsi8 : usb-storage 2-1.2:1.0
[28658.804953] scsi 8:0:0:0: Direct-Access Hitachi Hitachi HDS72302 A5C0 PQ: 0 ANSI: 4
[28658.813494] Check proc_name[usb-storage].
[28658.817691] sd 8:0:0:0: Attached scsi generic sg3 type 0
[28658.823729] sd 8:0:0:0: [sdd] 3907024896 512-byte logical blocks: (2.00 TB/1.81 TiB)
[28658.832525] usb 2-1.2: Disable of device-initiated U1 failed.
[28658.839015] usb 2-1.2: Disable of device-initiated U2 failed.
[28658.908201] usb 2-1.2: Device not responding to set address.
[28659.114556] usb 2-1.2: Device not responding to set address.
[28659.320522] usb 2-1.2: device not accepting address 7, error -71
[28659.339049] usb 2-1.2: USB disconnect, device number 7
[28659.346552] sd 8:0:0:0: [sdd] Write Protect is off
[28659.351359] sd 8:0:0:0: [sdd] Mode Sense: 4b 00 10 08
[28659.351393] sd 8:0:0:0: [sdd] Asking for cache data failed
[28659.356896] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[28659.363387] sd 8:0:0:0: [sdd] READ CAPACITY failed
[28659.368193] sd 8:0:0:0: [sdd]
[28659.371341] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[28659.377347] sd 8:0:0:0: [sdd] Sense not available.
[28659.382177] sd 8:0:0:0: [sdd] Asking for cache data failed
[28659.387667] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[28659.393766] sdd: detected capacity change from 2000396746752 to 0
[28659.400019] sd 8:0:0:0: [sdd] READ CAPACITY failed
[28659.404820] sd 8:0:0:0: [sdd]
[28659.407966] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[28659.413972] sd 8:0:0:0: [sdd] Sense not available.
[28659.418801] sd 8:0:0:0: [sdd] Asking for cache data failed
[28659.424290] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[28659.430385] sd 8:0:0:0: [sdd] Attached SCSI disk
[28659.435761] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880019bf4480
[28659.444823] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880019bf4440
[~] #

As you can see it does not actually mount the drive, it does not come up as an external device so the output of some of those commands are empty.

The disk is NTFS formatted with label "Hitachi". Ran a chkdsk from my Windows box on it. That did repair some minor issue, but it did not help with my problem, still reports inaccessible when I connect it to my QNAP. I probably formatted it from my Windows box once... long ago. I'd happily reformat it if that would resolve it, but of course before I can do that from the Qnap it first has to be recognized and show up in the External Devices...
tristus
Starting out
Posts: 10
Joined: Fri Aug 07, 2015 11:31 pm

Re: Hitachi Touro 2TB USB3 connected to TS-253 Pro

Post by tristus »

pwilson wrote:
Kees66 wrote:Has anyone got this working? When I connect my Hitachi Touro 2tb USB3 external drive to my QNap TS-253 Pro it responds with 3 beeps and in the log I see the message "A drive has been detected but is inaccessible. Please check it for faults". The drive works fine when connected straight to my Windows machine or to my other (Synology) NAS so the drive itself is ok. I connected a different USB device (WD Elements USB2) to the same ports and that works fine also. So it seems a compatibility issue between the QNap system and the Hitachi Touro drive. On the compatibility list on the QNap site I only see the HGST Touro mobile 1tb drive as recommended but that list is very limited.

When I connect the drive to my system and run lsusb I very briefly see it appear with the following specifics:
Bus 002 Device 004: ID 4971:1013 SimpleTech
But as soon as I get the three beeps, it is gone again.

Anything I could try to get this working? I was hoping to use the USB disk for a daily backup...
Please provide output for:

Code: Select all

echo "Firmware: QTS $(getcfg system version) Build $(getcfg system 'Build Number')"
testparm -s -l --section-name=USBDisk1 --parameter-name=path 2>/dev/null
mount | grep external
df -h | grep external
dmesg
  1. What type of File System did you put on it? NTFS?
  2. How did you format it?
  3. Did you "label" the drive?
Hi Patrick,

I have a TS251 NAS. I recently bought a new 6Tb drive to replace my 2 x 2Tb Raid1 drives. I have only one of the 2 2Tb drives anymore (the other is formated).
I wanted to copy all the data from my 2Tb drive to my NAS (with the 6Tb drive inside the NAS).
So I connected the 2Tb drive to the NAS usb port (via a sata/usb adapter).
I had exactly the same error message as kees66.
I red your answer and ssh the command you advise...Tried to understand the log but this is clearly beyond my (very limited) linux skills.
Would you, by chance, see something wrong in this log ?

[~] # echo "Firmware: QTS $(getcfg system version) Build $(getcfg system 'Build Number')"
Firmware: QTS 4.2.0 Build 20151118
[~] # testparm -s -l --section-name=USBDisk1 --parameter-name=path 2>/dev/null
[~] # mount | grep external
[~] # df -h | grep external
[~] # dmesg
[ 477.238187] ata6: EH complete
[ 477.241341] scsi 5:0:0:0: Direct-Access WDC WD60EFRX-68MYMN1 82.0 PQ : 0 ANSI: 5
[ 477.249462] ata6.00: set queue depth = 31
[ 477.253595] Check proc_name[ahci].
[ 477.257178] sd 5:0:0:0: Attached scsi generic sg1 type 0
[ 477.257584] sd 5:0:0:0: [sdb] 11721045168 512-byte logical blocks: (6.00 TB/5 .45 TiB)
[ 477.257586] sd 5:0:0:0: [sdb] 4096-byte physical blocks
[ 477.257677] sd 5:0:0:0: [sdb] Write Protect is off
[ 477.257680] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 477.257719] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, does n't support DPO or FUA
[ 477.353878] sdb: sdb1 sdb2 sdb3 sdb4 sdb5
[ 477.359183] sd 5:0:0:0: [sdb] Attached SCSI disk
[ 782.851393] md: bind<sdb1>
[ 782.855085] md/raid1:md9: active with 1 out of 24 mirrors
[ 782.860650] created bitmap (1 pages) for device md9
[ 782.865663] md9: bitmap initialized from disk: read 1 pages, set 9 of 9 bits
[ 782.892869] md9: detected capacity change from 0 to 542769152
[ 782.928374] md9: unknown partition table
[ 783.274417] kjournald starting. Commit interval 5 seconds
[ 783.279961] EXT3-fs (md9): using internal journal
[ 783.284701] EXT3-fs (md9): mounted filesystem with ordered data mode
[ 788.508777] md: bind<sdb4>
[ 788.512437] md/raid1:md13: active with 1 out of 24 mirrors
[ 788.518089] created bitmap (1 pages) for device md13
[ 788.523208] md13: bitmap initialized from disk: read 1 pages, set 8 of 8 bits
[ 788.550275] md13: detected capacity change from 0 to 469893120
[ 788.604889] md13: unknown partition table
[ 800.457138] kjournald starting. Commit interval 5 seconds
[ 800.462683] EXT3-fs (md13): using internal journal
[ 800.467509] EXT3-fs (md13): mounted filesystem with ordered data mode
[ 801.684349] md: bind<sdb2>
[ 801.688234] md/raid1:md256: active with 1 out of 2 mirrors
[ 801.693922] created bitmap (1 pages) for device md256
[ 801.699306] md256: bitmap initialized from disk: read 1 pages, set 9 of 9 bit s
[ 801.725847] md256: detected capacity change from 0 to 542834688
[ 801.764935] md256: unknown partition table
[ 801.816181] Adding 530108k swap on /dev/md256. Priority:-1 extents:1 across: 530108k
[ 802.019619] md: bind<sdb3>
[ 802.023277] md/raid1:md1: active with 1 out of 1 mirrors
[ 802.028652] md1: detected capacity change from 0 to 5990981238784
[ 802.099734] md1: unknown partition table
[ 803.300872] drbd r1: Starting worker thread (from drbdsetup-84 [29216])
[ 803.307782] block drbd1: disk( Diskless -> Attaching )
[ 803.313197] drbd r1: Method to ensure write ordering: flush
[ 803.318803] block drbd1: Adjusting my ra_pages to backing device's (32 -> 102 4)
[ 803.326143] block drbd1: drbd_bm_resize called with capacity == 11701132088
[ 803.333559] block drbd1: resync bitmap: bits=11426887 words=178546 pages=349
[ 803.340646] block drbd1: size = 5580 GB (5850566044 KB)
[ 803.351709] block drbd1: Writing the whole bitmap, size changed
[ 803.363223] block drbd1: bitmap WRITE of 349 pages took 5 jiffies
[ 803.369350] block drbd1: 5580 GB (11426887 bits) marked out-of-sync by on dis k bit-map.
[ 803.492699] block drbd1: recounting of set bits took additional 1 jiffies
[ 803.499528] block drbd1: 5580 GB (11426887 bits) marked out-of-sync by on dis k bit-map.
[ 803.507591] block drbd1: Suspended AL updates
[ 803.511985] block drbd1: disk( Attaching -> Inconsistent )
[ 803.517581] block drbd1: attached to UUIDs 0000000000000004:0000000000000000: 0000000000000000:0000000000000000
[ 803.540511] drbd r1: conn( StandAlone -> Unconnected )
[ 803.545810] drbd r1: Starting receiver thread (from drbd_w_r1 [29217])
[ 803.553610] drbd r1: receiver (re)started
[ 803.557687] drbd r1: conn( Unconnected -> WFConnection )
[ 803.563159] drbd r1: connect failed, err = -22
[ 803.567201] drbd r1: conn( WFConnection -> Disconnecting )
[ 803.573256] drbd r1: Discarding network configuration.
[ 803.578483] drbd r1: Connection closed
[ 803.582289] drbd r1: conn( Disconnecting -> StandAlone )
[ 803.587716] drbd r1: receiver terminated
[ 803.591668] drbd r1: Terminating drbd_r_r1
[ 803.596789] block drbd1: role( Secondary -> Primary ) disk( Inconsistent -> U pToDate )
[ 803.612356] block drbd1: Forced to consider local data as UpToDate!
[ 803.618666] block drbd1: new current UUID 2ED10B5F91F275BF:0000000000000004:0 000000000000000:0000000000000000
[ 804.841593] bio: create slab <bio-1> at 1
[ 805.818209] md: bind<sdb5>
[ 805.821844] md/raid1:md321: active with 1 out of 2 mirrors
[ 805.827502] created bitmap (1 pages) for device md321
[ 805.832716] md321: bitmap initialized from disk: read 1 pages, set 110 of 110 bits
[ 805.859706] md321: detected capacity change from 0 to 7340032000
[ 805.904699] md321: unknown partition table
[ 805.994592] Adding 7167996k swap on /dev/md321. Priority:-2 extents:1 across :7167996k
[ 806.531818] bio: create slab <bio-1> at 1
[ 807.247014] flashcache flashcache_ctr
[ 834.350856] EXT4-fs (dm-1): Mount option "noacl" will be removed by 3.5
[ 834.350856] Contact linux-ext4@vger.kernel.org if you think we should keep it .
[ 834.350856]
[ 834.690259] ext4_init_reserve_inode_table0: dm-1, 0
[ 834.696143] ext4_init_reserve_inode_table2: dm-1, 44190, 44190, 22625279, 409 6
[ 834.703487] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,delalloc,noacl
[ 834.758847] EXT4-fs (device dm-1): ext4lazyinit start (start from 0, total 44 190)
[ 835.791757] EXT4-fs (dm-1): re-mounted. Opts: (null)
[ 835.830372] EXT4-fs (dm-1): re-mounted. Opts: (null)
[ 835.977632] EXT4-fs (device dm-1): ext4lazyinit start (start from 10, total 4 4180)
[ 883.159725] warning: `proftpd' uses 32-bit capabilities (legacy support in us e)
[ 896.701987] md321: detected capacity change from 7340032000 to 0
[ 896.708084] md: md321 stopped.
[ 896.711215] md: unbind<sdb5>
[ 896.719136] md: export_rdev(sdb5)
[ 920.418230] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery d irectory
[ 920.426163] NFSD: starting 90-second grace period (net ffffffff81a76200)
[ 1004.221783] Bluetooth: Core ver 2.16
[ 1004.226149] NET: Registered protocol family 31
[ 1004.230634] Bluetooth: HCI device and connection manager initialized
[ 1004.237270] Bluetooth: HCI socket layer initialized
[ 1004.242312] Bluetooth: L2CAP socket layer initialized
[ 1004.247435] Bluetooth: SCO socket layer initialized
[ 1004.257226] usbcore: registered new interface driver btusb
[ 1126.295930] Set msys_nodify as 6300
[ 1174.386400] Loading iSCSI transport class v2.0-870.
[ 1174.403395] iscsi: registered transport (tcp)
[ 1187.359747] nfsd: last server has exited, flushing export cache
[ 1194.578659] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery d irectory
[ 1194.586561] NFSD: starting 90-second grace period (net ffffffff81a76200)
[ 1656.487688] EXT4-fs (device dm-1): ext4lazyinit finish
[ 1689.706422] usb 1-1.3: new high-speed USB device number 4 using xhci_hcd
[ 1689.725993] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 1689.732380] scsi7 : usb-storage 1-1.3:1.0
[ 1690.740768] scsi 7:0:0:0: Direct-Access PQ : 0 ANSI: 2 CCS
[ 1690.749674] Check proc_name[usb-storage].
[ 1690.754175] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 1690.761059] sd 7:0:0:0: [sdc] Test WP failed, assume Write Enabled
[ 1690.768748] sd 7:0:0:0: [sdc] Asking for cache data failed
[ 1690.774278] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 1690.783177] sd 7:0:0:0: [sdc] Test WP failed, assume Write Enabled
[ 1690.790516] sd 7:0:0:0: [sdc] Asking for cache data failed
[ 1690.796064] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 1690.802209] sd 7:0:0:0: [sdc] Attached SCSI disk
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: Hitachi Touro 2TB USB3 connected to TS-253 Pro

Post by schumaku »

@tristus: Afraid, we have to inform you that Patrick is no longer with us - RIP! http://forum.qnap.com/viewtopic.php?f=45&t=116613
Post Reply

Return to “Hardware & Software Compatibility”