Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #59250 > unrolled thread

READ CAPACITY(16) failed with 4TB iscsi HDD

Started byElias Pereira <empbilly@gmail.com>
First post2017-10-22 06:20 +0200
Last post2017-10-26 18:50 +0200
Articles 6 — 2 participants

Back to article view | Back to linux.debian.kernel

Contents

  READ CAPACITY(16) failed with 4TB iscsi HDD Elias Pereira <empbilly@gmail.com> - 2017-10-22 06:20 +0200
    Re: READ CAPACITY(16) failed with 4TB iscsi HDD Ritesh Raj Sarraf <rrs@researchut.com> - 2017-10-25 20:40 +0200
      Re: READ CAPACITY(16) failed with 4TB iscsi HDD Elias Pereira <empbilly@gmail.com> - 2017-10-25 22:00 +0200
    Re: READ CAPACITY(16) failed with 4TB iscsi HDD Ritesh Raj Sarraf <rrs@researchut.com> - 2017-10-26 06:40 +0200
      Re: READ CAPACITY(16) failed with 4TB iscsi HDD Elias Pereira <empbilly@gmail.com> - 2017-10-26 15:40 +0200
        Re: READ CAPACITY(16) failed with 4TB iscsi HDD Ritesh Raj Sarraf <rrs@researchut.com> - 2017-10-26 18:50 +0200

#59250 — READ CAPACITY(16) failed with 4TB iscsi HDD

FromElias Pereira <empbilly@gmail.com>
Date2017-10-22 06:20 +0200
SubjectREAD CAPACITY(16) failed with 4TB iscsi HDD
Message-ID<uDfTX-2mz-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hello,

I created a 4T dataset to use in a debian server as hdd backup. I have
open-iscsi installed on debian and working correctly, but after logging in
(iscsiadm -m node --targetname...), I can not see the 4T dataset (/dev/sdc).

fdisk -l shows only sda and sdb, both of 1TB that I had already set up some
time ago.

Debian dmesg shows:

[ 5266.620369] sd 7:0:0:4: [sdc] READ CAPACITY(16) failed
>
> [ 5266.620373] sd 7:0:0:4: [sdc]
>
> [ 5266.620375] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>
> [ 5266.620378] sd 7:0:0:4: [sdc]
>
> [ 5266.620380] Sense Key : Not Ready [current]
>
> [ 5266.620383] sd 7:0:0:4: [sdc]
>
> [ 5266.620386] Add. Sense: Logical unit not ready, manual intervention
>> required
>
> [ 5266.621129] sd 7:0:0:4: [sdc] READ CAPACITY failed
>
> [ 5266.621136] sd 7:0:0:4: [sdc]
>
> [ 5266.621143] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>
> [ 5266.621147] sd 7:0:0:4: [sdc]
>
> [ 5266.621150] Sense Key : Not Ready [current]
>
> [ 5266.621154] sd 7:0:0:4: [sdc]
>
> [ 5266.621158] Add. Sense: Logical unit not ready, manual intervention
>> required
>
> [ 5266.622251] sd 7:0:0:4: [sdc] Write Protect is off
>
> [ 5266.622256] sd 7:0:0:4: [sdc] Mode Sense: 73 00 10 08
>
> [ 5266.622667] sd 7:0:0:4: [sdc] Write cache: enabled, read cache:
>> enabled, supports DPO and FUA
>
> [ 5266.625062] sd 7:0:0:4: [sdc] READ CAPACITY(16) failed
>
> [ 5266.625066] sd 7:0:0:4: [sdc]
>
> [ 5266.625068] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>
> [ 5266.625070] sd 7:0:0:4: [sdc]
>
> [ 5266.625072] Sense Key : Not Ready [current]
>
> [ 5266.625076] sd 7:0:0:4: [sdc]
>
> [ 5266.625078] Add. Sense: Logical unit not ready, manual intervention
>> required
>
> [ 5266.625817] sd 7:0:0:4: [sdc] READ CAPACITY failed
>
> [ 5266.625823] sd 7:0:0:4: [sdc]
>
> [ 5266.625826] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>
> [ 5266.625830] sd 7:0:0:4: [sdc]
>
> [ 5266.625832] Sense Key : Not Ready [current]
>
> [ 5266.625837] sd 7:0:0:4: [sdc]
>
> [ 5266.625842] Add. Sense: Logical unit not ready, manual intervention
>> required
>
> [ 5266.627836] sd 7:0:0:4: [sdc] Attached SCSI disk
>
>
Any idea about the problem?

-- 
Elias Pereira

[toc] | [next] | [standalone]

#59265

FromRitesh Raj Sarraf <rrs@researchut.com>
Date2017-10-25 20:40 +0200
Message-ID<uEyKS-3hK-21@gated-at.bofh.it>
In reply to#59250
On Sun, 2017-10-22 at 02:13 -0200, Elias Pereira wrote:
> I created a 4T dataset to use in a debian server as hdd backup. I
> have open-iscsi installed on debian and working correctly, but after
> logging in (iscsiadm -m node --targetname...), I can not see the 4T
> dataset (/dev/sdc).
> 
> fdisk -l shows only sda and sdb, both of 1TB that I had already set
> up some time ago.

What iSCSI Target are you using ?

-- 
Given the large number of mailing lists I follow, I request you to CC
me in replies for quicker response

[toc] | [prev] | [next] | [standalone]

#59266

FromElias Pereira <empbilly@gmail.com>
Date2017-10-25 22:00 +0200
Message-ID<uEA0h-41x-3@gated-at.bofh.it>
In reply to#59265

[Multipart message — attachments visible in raw view] — view raw

Hello Ritesh, thanks for the reply!!! :D

If I understood your questioning, I'm using the freebsd/freenas target.

Would it be this? I have a debian with bacula that has as its target the
freenas.

On Wed, Oct 25, 2017 at 5:49 AM, Ritesh Raj Sarraf <rrs@researchut.com>
wrote:

> On Sun, 2017-10-22 at 02:13 -0200, Elias Pereira wrote:
> > I created a 4T dataset to use in a debian server as hdd backup. I
> > have open-iscsi installed on debian and working correctly, but after
> > logging in (iscsiadm -m node --targetname...), I can not see the 4T
> > dataset (/dev/sdc).
> >
> > fdisk -l shows only sda and sdb, both of 1TB that I had already set
> > up some time ago.
>
> What iSCSI Target are you using ?
>
> --
> Given the large number of mailing lists I follow, I request you to CC
> me in replies for quicker response
>
>


-- 
Elias Pereira

[toc] | [prev] | [next] | [standalone]

#59267

FromRitesh Raj Sarraf <rrs@researchut.com>
Date2017-10-26 06:40 +0200
Message-ID<uEI7v-PD-13@gated-at.bofh.it>
In reply to#59250
Based on your comment that the target is a FreeNAS appliance, I'd first
look into the target for errors.

READ CAPACITY failure looks like a very generic, target side,
unsupported feature on a very large device.

Are you sure FreeNAS support devices that large ?



On Sun, 2017-10-22 at 02:13 -0200, Elias Pereira wrote:
> Hello,
> 
> I created a 4T dataset to use in a debian server as hdd backup. I
> have open-iscsi installed on debian and working correctly, but after
> logging in (iscsiadm -m node --targetname...), I can not see the 4T
> dataset (/dev/sdc).
> 
> fdisk -l shows only sda and sdb, both of 1TB that I had already set
> up some time ago.
> 
> Debian dmesg shows:
> 
> > > [ 5266.620369] sd 7:0:0:4: [sdc] READ CAPACITY(16) failed
> > > [ 5266.620373] sd 7:0:0:4: [sdc] 
> > > [ 5266.620375] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > > [ 5266.620378] sd 7:0:0:4: [sdc] 
> > > [ 5266.620380] Sense Key : Not Ready [current] 
> > > [ 5266.620383] sd 7:0:0:4: [sdc] 
> > > [ 5266.620386] Add. Sense: Logical unit not ready, manual
> > > intervention required
> > > [ 5266.621129] sd 7:0:0:4: [sdc] READ CAPACITY failed
> > > [ 5266.621136] sd 7:0:0:4: [sdc] 
> > > [ 5266.621143] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > > [ 5266.621147] sd 7:0:0:4: [sdc] 
> > > [ 5266.621150] Sense Key : Not Ready [current] 
> > > [ 5266.621154] sd 7:0:0:4: [sdc] 
> > > [ 5266.621158] Add. Sense: Logical unit not ready, manual
> > > intervention required
> > > [ 5266.622251] sd 7:0:0:4: [sdc] Write Protect is off
> > > [ 5266.622256] sd 7:0:0:4: [sdc] Mode Sense: 73 00 10 08
> > > [ 5266.622667] sd 7:0:0:4: [sdc] Write cache: enabled, read
> > > cache: enabled, supports DPO and FUA
> > > [ 5266.625062] sd 7:0:0:4: [sdc] READ CAPACITY(16) failed
> > > [ 5266.625066] sd 7:0:0:4: [sdc] 
> > > [ 5266.625068] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > > [ 5266.625070] sd 7:0:0:4: [sdc] 
> > > [ 5266.625072] Sense Key : Not Ready [current] 
> > > [ 5266.625076] sd 7:0:0:4: [sdc] 
> > > [ 5266.625078] Add. Sense: Logical unit not ready, manual
> > > intervention required
> > > [ 5266.625817] sd 7:0:0:4: [sdc] READ CAPACITY failed
> > > [ 5266.625823] sd 7:0:0:4: [sdc] 
> > > [ 5266.625826] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > > [ 5266.625830] sd 7:0:0:4: [sdc] 
> > > [ 5266.625832] Sense Key : Not Ready [current] 
> > > [ 5266.625837] sd 7:0:0:4: [sdc] 
> > > [ 5266.625842] Add. Sense: Logical unit not ready, manual
> > > intervention required
> > > [ 5266.627836] sd 7:0:0:4: [sdc] Attached SCSI disk
> 
> Any idea about the problem? 
> 
-- 
Given the large number of mailing lists I follow, I request you to CC
me in replies for quicker response

[toc] | [prev] | [next] | [standalone]

#59268

FromElias Pereira <empbilly@gmail.com>
Date2017-10-26 15:40 +0200
Message-ID<uEQy6-5Wv-5@gated-at.bofh.it>
In reply to#59267

[Multipart message — attachments visible in raw view] — view raw

At first freenas supports this size.

On Thu, Oct 26, 2017 at 2:15 AM, Ritesh Raj Sarraf <rrs@researchut.com>
wrote:

> Based on your comment that the target is a FreeNAS appliance, I'd first
> look into the target for errors.
>
> READ CAPACITY failure looks like a very generic, target side,
> unsupported feature on a very large device.
>
> Are you sure FreeNAS support devices that large ?
>
>
>
> On Sun, 2017-10-22 at 02:13 -0200, Elias Pereira wrote:
> > Hello,
> >
> > I created a 4T dataset to use in a debian server as hdd backup. I
> > have open-iscsi installed on debian and working correctly, but after
> > logging in (iscsiadm -m node --targetname...), I can not see the 4T
> > dataset (/dev/sdc).
> >
> > fdisk -l shows only sda and sdb, both of 1TB that I had already set
> > up some time ago.
> >
> > Debian dmesg shows:
> >
> > > > [ 5266.620369] sd 7:0:0:4: [sdc] READ CAPACITY(16) failed
> > > > [ 5266.620373] sd 7:0:0:4: [sdc]
> > > > [ 5266.620375] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > > > [ 5266.620378] sd 7:0:0:4: [sdc]
> > > > [ 5266.620380] Sense Key : Not Ready [current]
> > > > [ 5266.620383] sd 7:0:0:4: [sdc]
> > > > [ 5266.620386] Add. Sense: Logical unit not ready, manual
> > > > intervention required
> > > > [ 5266.621129] sd 7:0:0:4: [sdc] READ CAPACITY failed
> > > > [ 5266.621136] sd 7:0:0:4: [sdc]
> > > > [ 5266.621143] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > > > [ 5266.621147] sd 7:0:0:4: [sdc]
> > > > [ 5266.621150] Sense Key : Not Ready [current]
> > > > [ 5266.621154] sd 7:0:0:4: [sdc]
> > > > [ 5266.621158] Add. Sense: Logical unit not ready, manual
> > > > intervention required
> > > > [ 5266.622251] sd 7:0:0:4: [sdc] Write Protect is off
> > > > [ 5266.622256] sd 7:0:0:4: [sdc] Mode Sense: 73 00 10 08
> > > > [ 5266.622667] sd 7:0:0:4: [sdc] Write cache: enabled, read
> > > > cache: enabled, supports DPO and FUA
> > > > [ 5266.625062] sd 7:0:0:4: [sdc] READ CAPACITY(16) failed
> > > > [ 5266.625066] sd 7:0:0:4: [sdc]
> > > > [ 5266.625068] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > > > [ 5266.625070] sd 7:0:0:4: [sdc]
> > > > [ 5266.625072] Sense Key : Not Ready [current]
> > > > [ 5266.625076] sd 7:0:0:4: [sdc]
> > > > [ 5266.625078] Add. Sense: Logical unit not ready, manual
> > > > intervention required
> > > > [ 5266.625817] sd 7:0:0:4: [sdc] READ CAPACITY failed
> > > > [ 5266.625823] sd 7:0:0:4: [sdc]
> > > > [ 5266.625826] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > > > [ 5266.625830] sd 7:0:0:4: [sdc]
> > > > [ 5266.625832] Sense Key : Not Ready [current]
> > > > [ 5266.625837] sd 7:0:0:4: [sdc]
> > > > [ 5266.625842] Add. Sense: Logical unit not ready, manual
> > > > intervention required
> > > > [ 5266.627836] sd 7:0:0:4: [sdc] Attached SCSI disk
> >
> > Any idea about the problem?
> >
> --
> Given the large number of mailing lists I follow, I request you to CC
> me in replies for quicker response
>
>


-- 
Elias Pereira

[toc] | [prev] | [next] | [standalone]

#59269

FromRitesh Raj Sarraf <rrs@researchut.com>
Date2017-10-26 18:50 +0200
Message-ID<uETvX-7Kh-1@gated-at.bofh.it>
In reply to#59268

[Multipart message — attachments visible in raw view] — view raw

On Thu, 2017-10-26 at 11:34 -0200, Elias Pereira wrote:
> At first freenas supports this size.
> 

I just booted into my LIO Target + Open iSCSI Initiator setup, to
ensure that nothing is broken. I sure do not have that large a drive to
test. But basic iSCSI setup on Linux is working fine in local
configuration.


Looking at FreeNAS, yours' must be a ZFS based setup, which means your
iSCSI Target is the one that ZFS provides. I have never worked on that
setup, so I can't comment.

But, to pin-point the issue, better debug logs are needed.


> On Thu, Oct 26, 2017 at 2:15 AM, Ritesh Raj Sarraf
> <rrs@researchut.com> wrote:
> > Based on your comment that the target is a FreeNAS appliance, I'd
> > first
> > look into the target for errors.
> > 
> > READ CAPACITY failure looks like a very generic, target side,
> > unsupported feature on a very large device.
> > 
> > Are you sure FreeNAS support devices that large ?
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web