Re: READ CAPACITY(16) failed with 4TB iscsi HDD

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

Re: READ CAPACITY(16) failed with 4TB iscsi HDD

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 wrote: > On Sun,

Re: READ CAPACITY(16) failed with 4TB iscsi HDD

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

Bug#879768: linux: Backport regulator: fan53555: fix I2C device ids

On 25/10/17 16:38, Guillaume Tucker wrote: Source: linux Version: 4.9.30-2 Severity: normal Tags: upstream patch Dear Maintainer, The attached fix is a backport from mainline which has also been Sorry about the same patch being attached twice, that was a glitch when I ran reportbug... (my

Bug#879768: linux: Backport regulator: fan53555: fix I2C device ids

Source: linux Version: 4.9.30-2 Severity: normal Tags: upstream patch Dear Maintainer, The attached fix is a backport from mainline which has also been submitted to linux-4.9 stable:

Bug#879767: firmware-amd-graphics: Debian 9 just reboot once load the driver radeon with the firmwares on AMD A8-6500APU

Package: firmware-amd-graphics Version: 20161130-3 Severity: important Dear Maintainer, * Just booting try with the standard kernel of Debian 9 and the package installation. * Get LiveDisk of Debian 9 with the standard kernel and the package and try to load from it on AMD A8-6500APU. *

Bug#878403: linux-image-4.13.0-1-686-pae (and prior version!) crashes at boot

Dear maintainers, got the kernel now running. Solution: In /etc/default/grub I had to comment the following lines: GRUB_GFXMODE=1024x600 GRUB_GFXPAYLOAD_LINUX=keep I believe, the latest kernel-module is not capable to run the resolution of 1024x600 (which is the native resolution of my

[debian/stretch64] lxc-copy: Snapshot with OverlayFS backingstorage fails with Linux-4.9.y

[ Please CC me - I am not subscribed to lxc-users and debian-kernel MLs ] Hi, I am playing with LXC and OverlayFS. The Debian-kernel shipped with stretch64 fails when using lxc-copy for a snapshot. Later I tried the latest Debian-kernel from stretch-backports APT-repository [0] and the issue

linux_4.13.4-2~bpo9+1_multi.changes ACCEPTED into stretch-backports, stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Oct 2017 17:18:02 +0100 Source: linux Binary: linux-source-4.13 linux-support-4.13.0-0.bpo.1 linux-doc-4.13 linux-kbuild-4.13 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.13 usbip hyperv-daemons

firmware-nonfree_20170823-1~bpo9+1_amd64.changes ACCEPTED into stretch-backports, stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 20 Oct 2017 01:34:42 +0100 Source: firmware-nonfree Binary: firmware-linux firmware-linux-nonfree firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium

linux-latest_80+deb9u2~bpo8+1_multi.changes ACCEPTED into jessie-backports->backports-policy, jessie-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Oct 2017 22:12:01 +0100 Source: linux-latest Binary: linux-source linux-doc linux-perf linux-image-alpha-generic linux-headers-alpha-generic linux-image-alpha-smp linux-headers-alpha-smp linux-image-amd64