The problem I am about to describe characterizes my experience
with Slack 15.0 and simply breaks my heart. I have been using
Slackware since the early '90s when Soft Landing Systems shut
down. All along I have waited for a "stable" system to settle
down before updating. I have several systems, most are still
running 14.2, but this, my main computer is running 15.0
with all components and patches up-to-date.

My current problem with 15.0 is that it does not allow me
to mount a 14TB drive that I wrote using 14.2 Slackware.
Here is the dmesg info:

[ 54.872534] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 54.872688] scsi host6: usb-storage 2-1:1.0
[ 55.880582] scsi 6:0:0:0: Direct-Access WD easystore 264D 3012 PQ: 0 ANSI: 6
[ 55.880905] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
[ 55.881055] scsi 6:0:0:1: Enclosure WD SES Device 3012 PQ: 0 ANSI: 6
[ 55.881175] sd 6:0:0:0: [sdd] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
[ 55.881177] sd 6:0:0:0: [sdd] 4096-byte physical blocks
[ 55.882679] ses 6:0:0:1: Attached Enclosure device
[ 55.882940] sd 6:0:0:0: [sdd] Write Protect is off
[ 55.882942] sd 6:0:0:0: [sdd] Mode Sense: 47 00 10 08
[ 55.883203] ses 6:0:0:1: Wrong diagnostic page; asked for 1 got 8
[ 55.883204] ses 6:0:0:1: Failed to get diagnostic page 0x1
[ 55.883205] ses 6:0:0:1: Failed to bind enclosure -19
[ 55.883519] sd 6:0:0:0: [sdd] No Caching mode page found
[ 55.883521] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[ 55.891224] sdd: sdd1
[ 55.892144] sd 6:0:0:0: [sdd] Attached SCSI disk
[ 59.986857] usb 2-1: USB disconnect, device number 18

Here is the 14.2 dmesg:
[6467175.354305] usb 6-2: new SuperSpeed USB device number 100 using xhci_hcd
[6467175.366825] usb 6-2: New USB device found, idVendor=1058, idProduct=264d
[6467175.366829] usb 6-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[6467175.366831] usb 6-2: Product: easystore 264D
[6467175.366833] usb 6-2: Manufacturer: Western Digital
[6467175.366835] usb 6-2: SerialNumber: 59354A3144505543
[6467175.368662] usb-storage 6-2:1.0: USB Mass Storage device detected
[6467175.368816] scsi host34: usb-storage 6-2:1.0
[6467176.398183] scsi 34:0:0:0: Direct-Access WD easystore 264D 3012 PQ: 0 ANSI: 6
[6467176.399076] scsi 34:0:0:1: Enclosure WD SES Device 3012 PQ: 0 ANSI: 6
[6467176.400903] sd 34:0:0:0: [sdg] Spinning up disk...
[6467176.402176] ses 34:0:0:1: Attached Enclosure device
[6467176.402711] ses 34:0:0:1: Wrong diagnostic page; asked for 1 got 8
[6467176.402712] ses 34:0:0:1: Failed to get diagnostic page 0x1
[6467176.402712] ses 34:0:0:1: Failed to bind enclosure -19
[6467177.421725] .
[6467178.445739] .
[6467179.469746] .
[6467180.493724] .
[6467181.517733] .
[6467182.541736] .
[6467183.565714] .
[6467184.589736] .
[6467185.613740] .
[6467186.637741] .
[6467187.661742] .
[6467188.685742] .
[6467189.709740] .
[6467190.733736] .
[6467191.757732] .
[6467192.781713] .
[6467192.781821] ready
[6467192.781956] sd 34:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
[6467192.782085] sd 34:0:0:0: [sdg] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
[6467192.782087] sd 34:0:0:0: [sdg] 4096-byte physical blocks
[6467192.782589] sd 34:0:0:0: [sdg] Write Protect is off
[6467192.782592] sd 34:0:0:0: [sdg] Mode Sense: 47 00 10 08
[6467192.783115] sd 34:0:0:0: [sdg] No Caching mode page found
[6467192.783117] sd 34:0:0:0: [sdg] Assuming drive cache: write through
[6467192.783481] sd 34:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
[6467192.868788] sdg: sdg1
[6467192.869365] sd 34:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
[6467192.870510] sd 34:0:0:0: [sdg] Attached SCSI disk

As you can see, 14.2 is able to recover from whatever problem "Failed to bind enclosure -19"
is. The 14.2 system is a real workhorse with several petabytes of drives.

On 02/28/2023 08:08 AM, root wrote:
> The problem I am about to describe characterizes my experience
> with Slack 15.0 and simply breaks my heart. I have been using
> Slackware since the early '90s when Soft Landing Systems shut
> down. All along I have waited for a "stable" system to settle
> down before updating. I have several systems, most are still
> running 14.2, but this, my main computer is running 15.0
> with all components and patches up-to-date.
>
> My current problem with 15.0 is that it does not allow me
> to mount a 14TB drive that I wrote using 14.2 Slackware.
What do you get when you type fdisk -l in the console?
--
Jimmy Johnson

Slackware64 15.0 - i7-2820QM - EXT4 at sda9
Registered Linux User #380263

On Tue, 28 Feb 2023 16:08:26 +0000, root wrote:

> Here is the dmesg info:

> [55.891224] sdd: sdd1

So Slackware 15.0 seems to find a disk sdd with a partition sdd1.

> [6467192.868788] sdg: sdg1

Slackware 14.2 seems to find a disk sdg with a partition sdg1.

What happens when you try to mount /dev/sdd1 on Slackware 15.0?

regards Henrik

Jimmy Johnson <Jimmy@disposable.invalid> wrote:
> On 02/28/2023 08:08 AM, root wrote:
>> The problem I am about to describe characterizes my experience
>> with Slack 15.0 and simply breaks my heart. I have been using
>> Slackware since the early '90s when Soft Landing Systems shut
>> down. All along I have waited for a "stable" system to settle
>> down before updating. I have several systems, most are still
>> running 14.2, but this, my main computer is running 15.0
>> with all components and patches up-to-date.
>>
>> My current problem with 15.0 is that it does not allow me
>> to mount a 14TB drive that I wrote using 14.2 Slackware.
> What do you get when you type fdisk -l in the console?

I only see the drives that are always connected. It does not
see the one connected as USB.

Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> wrote:
> On Tue, 28 Feb 2023 16:08:26 +0000, root wrote:
>
>> Here is the dmesg info:
>
>> [55.891224] sdd: sdd1
>
> So Slackware 15.0 seems to find a disk sdd with a partition sdd1.
>
>> [6467192.868788] sdg: sdg1
>
> Slackware 14.2 seems to find a disk sdg with a partition sdg1.
>
> What happens when you try to mount /dev/sdd1 on Slackware 15.0?
>
> regards Henrik

Thanks again Henrik. I cannot mount /dev/sdd1:
mount: /sdd1: special device /dev/sdd1 does not exist.

Even though /dev/sdd and /dev/sdd1 do appear.

root <NoEMail@home.org> wrote:
> My current problem with 15.0 is that it does not allow me
> to mount a 14TB drive that I wrote using 14.2 Slackware.
> Here is the dmesg info:

What filesystem is present on this 14TB drive?

Rich <rich@example.invalid> wrote:
> root <NoEMail@home.org> wrote:
>> My current problem with 15.0 is that it does not allow me
>> to mount a 14TB drive that I wrote using 14.2 Slackware.
>> Here is the dmesg info:
>
> What filesystem is present on this 14TB drive?

It is an ext4 file system.

On 02/28/2023 11:36 AM, root wrote:
> Jimmy Johnson <Jimmy@disposable.invalid> wrote:
>> On 02/28/2023 08:08 AM, root wrote:
>>> The problem I am about to describe characterizes my experience
>>> with Slack 15.0 and simply breaks my heart. I have been using
>>> Slackware since the early '90s when Soft Landing Systems shut
>>> down. All along I have waited for a "stable" system to settle
>>> down before updating. I have several systems, most are still
>>> running 14.2, but this, my main computer is running 15.0
>>> with all components and patches up-to-date.
>>>
>>> My current problem with 15.0 is that it does not allow me
>>> to mount a 14TB drive that I wrote using 14.2 Slackware.
>> What do you get when you type fdisk -l in the console?
>
> I only see the drives that are always connected. It does not
> see the one connected as USB.

Does 15.0 see any usb drives? In 14.2 what do you see when you type
fdisk -l?
--
Jimmy Johnson

Alien-19-Linux - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263

On 02/28/2023 02:57 PM, root wrote:
> Rich <rich@example.invalid> wrote:
>> root <NoEMail@home.org> wrote:
>>> My current problem with 15.0 is that it does not allow me
>>> to mount a 14TB drive that I wrote using 14.2 Slackware.
>>> Here is the dmesg info:
>>
>> What filesystem is present on this 14TB drive?
>
> It is an ext4 file system.

A DOS partition table using EXT4 is 4TB. Using a GPT Partition table you
should be okay using EXT4, GPT is pretty much unlimited in size. I use a
DOS partition Table and limit EXT4 partition size to 4TB.
--
Jimmy Johnson

Alien-19-Linux - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263

Jimmy Johnson <Jimmy@disposable.invalid> wrote:
> On 02/28/2023 02:57 PM, root wrote:
>> Rich <rich@example.invalid> wrote:
>>> root <NoEMail@home.org> wrote:
>>>> My current problem with 15.0 is that it does not allow me
>>>> to mount a 14TB drive that I wrote using 14.2 Slackware.
>>>> Here is the dmesg info:
>>>
>>> What filesystem is present on this 14TB drive?
>>
>> It is an ext4 file system.
>
> A DOS partition table using EXT4 is 4TB. Using a GPT Partition table you
> should be okay using EXT4, GPT is pretty much unlimited in size. I use a
> DOS partition Table and limit EXT4 partition size to 4TB.

There is a problem with my 14TB drive that Slack 15.0 can't handle
but 14.2 can. 15.0 can handle (mount) other of my 14TB drives,
but not this one. Based upon the dmesg info I posted earlier,
I think the problem is something like the drive doensn't spin
up fast enough for 15.0.

Thanks for the help.

Jimmy Johnson <Jimmy@disposable.invalid> wrote:
> On 02/28/2023 11:36 AM, root wrote:
>> Jimmy Johnson <Jimmy@disposable.invalid> wrote:
>>> On 02/28/2023 08:08 AM, root wrote:
>>>> The problem I am about to describe characterizes my experience
>>>> with Slack 15.0 and simply breaks my heart. I have been using
>>>> Slackware since the early '90s when Soft Landing Systems shut
>>>> down. All along I have waited for a "stable" system to settle
>>>> down before updating. I have several systems, most are still
>>>> running 14.2, but this, my main computer is running 15.0
>>>> with all components and patches up-to-date.
>>>>
>>>> My current problem with 15.0 is that it does not allow me
>>>> to mount a 14TB drive that I wrote using 14.2 Slackware.
>>> What do you get when you type fdisk -l in the console?
>>
>> I only see the drives that are always connected. It does not
>> see the one connected as USB.
>
> Does 15.0 see any usb drives? In 14.2 what do you see when you type
> fdisk -l?

Yes, the 15.0 drive sees all the other drives I have mounted, I just
have never mounted a 14TB drive on this machine. A few minutes ago
I did mount another 14TB drive and all was well. It is something
different about this drive, which still works on 14.2. It is
a backup for an internal drive in the 14.2 machine.

On 02/28/2023 07:14 PM, root wrote:
> There is a problem with my 14TB drive that Slack 15.0 can't handle
> but 14.2 can. 15.0 can handle (mount) other of my 14TB drives,
> but not this one. Based upon the dmesg info I posted earlier,
> I think the problem is something like the drive doensn't spin
> up fast enough for 15.0.
>
> Thanks for the help.

I hear you saying your computer does not have enough power to handle
that drive. Is that right?
--
Jimmy Johnson

Alien-19-Linux - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263

On Tue, 28 Feb 2023 16:08:26 -0000 (UTC), root wrote:

> The problem I am about to describe characterizes my experience with
> Slack 15.0 and simply breaks my heart. I have been using Slackware since
> the early '90s when Soft Landing Systems shut down. All along I have
> waited for a "stable" system to settle down before updating. I have
> several systems, most are still running 14.2, but this, my main computer
> is running 15.0 with all components and patches up-to-date.
>
> My current problem with 15.0 is that it does not allow me to mount a
> 14TB drive that I wrote using 14.2 Slackware.

Hi,

I have no experience with hard drives that size--I have two USB backup
drives, which I rotate, of 1TB each--but I did find an article on
LinuxQuestions.org that may be of interest:

https://www.linuxquestions.org/questions/slackware-14/4tb-external-
hard-drives-that-are-compatible-with-slackware-linux-4175715094/

Good luck to you!

-Joe

> [snip]

On Wed, 01 Mar 2023 03:14:38 +0000, root wrote:
> There is a problem with my 14TB drive that Slack 15.0 can't handle but
> 14.2 can. 15.0 can handle (mount) other of my 14TB drives, but not this
> one. Based upon the dmesg info I posted earlier,
> I think the problem is something like the drive doensn't spin up fast
> enough for 15.0.

Odd, I have been able to see USB connected drives with sizes up to 20 TB
in Slackware 15.0. Does dmesg say anything if you try "fdisk -l /dev/sdd"
when /dev/sdd and /dev/sdd1 exist but it doesn't work to mount /dev/sdd1?

Is the USB drive connected with a USB 3 cable to a USB 3 port? If not, is
it one of those USB 2 cables with double connectors to the computer, one
connector for data and power and another connector for extra power? If
not, does the USB chassis have some kind of external power supply?

regards Henrik

On 02/28/2023 04:02 PM, Jimmy Johnson wrote:

> I use a I use a DOS partition Table and limit EXT4 partition size to 4TB.

That should have been 3TB. once the partition is made and formatted to
EXT4 it is 2.73TB and works no problems, I have 3 WD NAS drives, 2 USB
and one SSD.
--
Jimmy Johnson

Slackware 15.0 - AMD A8-7600 - EXT4 at sda8
Registered Linux User #380263

I posted a follow-up to my original post which seems to have been lost.
My problem was (is) with the drive. I can connect other 14TB drives
with no problem.

Since the drive works with 14.2 I guess that the problem drive has
a problem such as failure to spin up in time, and the 15.0 driver
drops it, while the 14.2 driver is willing to wait longer.

Thanks for the help.