• Re: LM file transfer/copy issues

    From Axel@3:633/10 to All on Wednesday, December 24, 2025 16:28:50
    Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    So the sad tale thus far. But first, some detail. This PC (specs below) >>>> has LM 22.2 installed on a 1Tb NVME. It also has two mobile racks for
    easy insertion and removal of HD's. The lower rack I use for the
    Timeshift disk, and the upper one for the files disk, a WD 1Tb
    mechanical disk formatted in Ext4. It also has two external USB cases
    for additional hard drives. Following a process of trial and error, I've >>>> discovered that the problem of file errors only occurs when I write to >>>> the files disk in the mobile rack. I can read/write both ways NVME to
    USB without errors, and read/write both ways USB to USB without errors. >>> Does any of that mean you tried the most obvious thing of
    connecting the "files disk" without using the rack, in case the
    drive is faulty?
    not specifically, but the drive is new, and the problem was present with
    any drive in that bay
    C'mon you just said: "today I tried an old 320 Gb NTFS HD in the
    rack, and I could write to it without limitation". Which of you do
    I believe?

    I can also read from the files disk to write to either USB without
    errors. So my trouble shooting has been focused on the mobile rack. I >>>> replaced it, and also the cable, and swapped the cable to another
    motherboard (MB) SATA port. Since USB transfers work, and the USB boxes >>>> have their own power supply, I thought maybe it was a power issue within >>>> the PC. According to the newegg calculator
    [https://promotions.newegg.com/tools/power-supply-calculator/v2/ ] I
    need 600 -700 watts for this PC. The PS was only 550 watts so I swapped >>>> it out with a 750 watt PS. Having said all this, I can write to the
    Files disk if I transfer folders/files in small lots of up to about
    10Gb, and today I tried an old 320 Gb NTFS HD in the rack, and I could >>>> write to it without limitation. ???
    Sounds like you've just narrowed the issue down to the "files disk"
    itself.

    no, unfortunately
    Unfortunately your story changes all the time...


    no it doesn't. read the whole thread if you want the full story

    --
    Linux Mint 22.2
    {I shot Felix and buried him}


    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Axel@3:633/10 to All on Wednesday, December 24, 2025 16:34:28
    Axel wrote:
    Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    So the sad tale thus far. But first, some detail. This PC (specs
    below)
    has LM 22.2 installed on a 1Tb NVME. It also has two mobile racks for >>>>> easy insertion and removal of HD's. The lower rack I use for the
    Timeshift disk, and the upper one for the files disk, a WD 1Tb
    mechanical disk formatted in Ext4. It also has two external USB cases >>>>> for additional hard drives. Following a process of trial and
    error, I've
    discovered that the problem of file errors only occurs when I
    write to
    the files disk in the mobile rack. I can read/write both ways NVME to >>>>> USB without errors, and read/write both ways USB to USB without
    errors.
    Does any of that mean you tried the most obvious thing of
    connecting the "files disk" without using the rack, in case the
    drive is faulty?
    not specifically, but the drive is new, and the problem was present
    with
    any drive in that bay
    C'mon you just said: "today I tried an old 320 Gb NTFS HD in the
    rack, and I could write to it without limitation". Which of you do
    I believe?

    I can also read from the files disk to write to either USB without
    errors. So my trouble shooting has been focused on the mobile
    rack.ÿ I
    replaced it, and also the cable, and swapped the cable to another
    motherboard (MB) SATA port. Since USB transfers work, and the USB
    boxes
    have their own power supply, I thought maybe it was a power issue
    within
    the PC. According to the newegg calculator
    [https://promotions.newegg.com/tools/power-supply-calculator/v2/ ] I >>>>> need 600 -700 watts for this PC. The PS was only 550 watts so I
    swapped
    it out with a 750 watt PS. Having said all this, I can write to the
    Files disk if I transfer folders/files in small lots of up to about
    10Gb, and today I tried an old 320 Gb NTFS HD in the rack, and I
    could
    write to it without limitation. ???
    Sounds like you've just narrowed the issue down to the "files disk"
    itself.

    no, unfortunately
    Unfortunately your story changes all the time...


    no it doesn't. read the whole thread if you want the full story


    or in a nutshell.. the question now is why did it write to that drive
    and not others? is the size of the drive or it's software/technology
    relevant? or is the problem now fixed since i replaced the PS? more
    testing is needed. meanwhile.. Seasons greetings to you and all!

    --
    Linux Mint 22.2
    {I shot Felix and buried him}


    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Computer Nerd Kev@3:633/10 to All on Wednesday, December 24, 2025 16:41:30
    In aus.computers Axel <none@not.here> wrote:
    Axel wrote:
    Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    So the sad tale thus far. But first, some detail. This PC (specs
    below)
    has LM 22.2 installed on a 1Tb NVME. It also has two mobile racks for >>>>>> easy insertion and removal of HD's. The lower rack I use for the
    Timeshift disk, and the upper one for the files disk, a WD 1Tb
    mechanical disk formatted in Ext4. It also has two external USB cases >>>>>> for additional hard drives. Following a process of trial and
    error, I've
    discovered that the problem of file errors only occurs when I
    write to
    the files disk in the mobile rack. I can read/write both ways NVME to >>>>>> USB without errors, and read/write both ways USB to USB without
    errors.
    Does any of that mean you tried the most obvious thing of
    connecting the "files disk" without using the rack, in case the
    drive is faulty?
    not specifically, but the drive is new, and the problem was present
    with
    any drive in that bay
    C'mon you just said: "today I tried an old 320 Gb NTFS HD in the
    rack, and I could write to it without limitation". Which of you do
    I believe?

    I can also read from the files disk to write to either USB without >>>>>> errors. So my trouble shooting has been focused on the mobile
    rack. I
    replaced it, and also the cable, and swapped the cable to another
    motherboard (MB) SATA port. Since USB transfers work, and the USB >>>>>> boxes
    have their own power supply, I thought maybe it was a power issue >>>>>> within
    the PC. According to the newegg calculator
    [https://promotions.newegg.com/tools/power-supply-calculator/v2/ ] I >>>>>> need 600 -700 watts for this PC. The PS was only 550 watts so I
    swapped
    it out with a 750 watt PS. Having said all this, I can write to the >>>>>> Files disk if I transfer folders/files in small lots of up to about >>>>>> 10Gb, and today I tried an old 320 Gb NTFS HD in the rack, and I
    could
    write to it without limitation. ???
    Sounds like you've just narrowed the issue down to the "files disk"
    itself.

    no, unfortunately
    Unfortunately your story changes all the time...


    no it doesn't. read the whole thread if you want the full story


    or in a nutshell.. the question now is why did it write to that drive
    and not others? is the size of the drive or it's software/technology relevant?

    Maybe that drive (or the NTFS driver) is just too slow for whatever
    signal issue you have with the rack to be triggered.

    I'm not sure if they still do it on new HDDs, but maybe there's a
    jumper setting on the other drives to limit the speed? https://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit/s_and_SATA_3_Gbit/s

    --
    __ __
    #_ < |\| |< _#

    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Wednesday, December 24, 2025 10:42:44
    On Wed, 12/24/2025 1:41 AM, Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:

    or in a nutshell.. the question now is why did it write to that drive
    and not others? is the size of the drive or it's software/technology
    relevant?

    Maybe that drive (or the NTFS driver) is just too slow for whatever
    signal issue you have with the rack to be triggered.

    I'm not sure if they still do it on new HDDs, but maybe there's a
    jumper setting on the other drives to limit the speed? https://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit/s_and_SATA_3_Gbit/s

    No guarantees, but maybe an

    lsusb

    and check the detection on the rack, would give
    some idea of the controller being used.

    That would make it easier to quantify what the rack contains.

    $ lsusb

    Bus 002 Device 004: ID 045e:076c Microsoft Corp. Comfort Mouse 4500
    ...
    Bus 006 Device 002: ID 174c:1053 ASMedia Technology Inc. USB3.0 Device

    bullwinkle@Legacy:~$ sudo dmesg

    [ 1.681416] scsi host8: uas
    [ 1.681686] usbcore: registered new interface driver uas
    [ 1.682244] scsi 8:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 6
    [ 1.683985] sd 8:0:0:0: [sdb] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
    [ 1.684041] sd 8:0:0:0: [sdb] 4096-byte physical blocks
    [ 1.684193] sd 8:0:0:0: [sdb] Write Protect is off
    [ 1.684237] sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00
    [ 1.684384] sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.725872] sr 2:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
    [ 1.725929] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 1.730920] sd 8:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
    [ 1.730995] sd 8:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
    [ 1.777719] sdb: sdb1 sdb2 sdb3 sdb4 sdb5
    [ 1.778021] sd 8:0:0:0: [sdb] Attached SCSI disk

    *******

    The 174c:1053 gives:

    ASMedia Technology ASM1053 SATA 3Gb/s bridge

    and it is detecting some 8TB drive.

    Paul



    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Wednesday, December 24, 2025 10:47:02
    On Tue, 12/23/2025 9:13 PM, Axel wrote:
    Paul wrote:
    On Tue, 12/23/2025 12:58 PM, Axel wrote:

    when I do that there's nothing in the right hand pane for grsync

    https://auslink.info/linux/synaptic.png

    grsync is in the menu and loads from the terminal

    I appreciate it very much
    In your picture, you've just done a search on

    ÿÿÿÿ linux_czkawka_gui_x86_64

    and since that is not a .deb and is a portable ELF
    (not packaged properly but still usable), you don't
    expect to find it.

    In your picture, if you'd cursored up or used the mouse
    to select the "grsync" on the left, you would get to review
    the search result for that on the right. And, it would be there.

    I had tried firstly with grsync, as per your example. the result was the same, nothing on the right side. my mistake by not highlighting grsync for the screenshot.

    https://auslink.info/linux/grsync.png


    This is LMDE7.

    ÿÿÿ [Picture]ÿÿ LMDE7-grsync-synaptic.gif

    ÿÿÿÿ https://imgur.com/a/96wnrhS

    I can see the state of the package in the example, and it is
    not installed right now.

    But, the package is available.

    ÿÿÿ Paul

    I set my search to "Description and Name".

    *******

    You can also do it from command line.
    It does not require sudo.

    apt search grsync

    It would normally be followed by

    sudo apt install grsync

    Paul

    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Computer Nerd Kev@3:633/10 to All on Thursday, December 25, 2025 07:28:22
    In aus.computers Paul <nospam@needed.invalid> wrote:
    On Wed, 12/24/2025 1:41 AM, Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    or in a nutshell.. the question now is why did it write to that drive
    and not others? is the size of the drive or it's software/technology
    relevant?

    Maybe that drive (or the NTFS driver) is just too slow for whatever
    signal issue you have with the rack to be triggered.

    I'm not sure if they still do it on new HDDs, but maybe there's a
    jumper setting on the other drives to limit the speed?
    https://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit/s_and_SATA_3_Gbit/s

    No guarantees, but maybe an

    lsusb

    and check the detection on the rack, would give
    some idea of the controller being used.

    He said "swapped the cable to another motherboard (MB) SATA port"
    so that must mean the rack uses SATA connection/s to the
    motherboard, not USB. In that case "lsusb" won't show it. If the
    rack is poorly designed or an old model then maybe it introduces
    too much signal noise for operating at higer data speeds. Or maybe
    there's a bad connection, but he also said he replaced the rack.

    --
    __ __
    #_ < |\| |< _#

    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Thursday, December 25, 2025 01:27:27
    On Wed, 12/24/2025 4:28 PM, Computer Nerd Kev wrote:
    In aus.computers Paul <nospam@needed.invalid> wrote:
    On Wed, 12/24/2025 1:41 AM, Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    or in a nutshell.. the question now is why did it write to that drive >>>> and not others? is the size of the drive or it's software/technology
    relevant?

    Maybe that drive (or the NTFS driver) is just too slow for whatever
    signal issue you have with the rack to be triggered.

    I'm not sure if they still do it on new HDDs, but maybe there's a
    jumper setting on the other drives to limit the speed?
    https://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit/s_and_SATA_3_Gbit/s

    No guarantees, but maybe an

    lsusb

    and check the detection on the rack, would give
    some idea of the controller being used.

    He said "swapped the cable to another motherboard (MB) SATA port"
    so that must mean the rack uses SATA connection/s to the
    motherboard, not USB. In that case "lsusb" won't show it. If the
    rack is poorly designed or an old model then maybe it introduces
    too much signal noise for operating at higer data speeds. Or maybe
    there's a bad connection, but he also said he replaced the rack.


    OK. Maybe we're making progress then.

    It seemed that Southbridge ports were made "kinda ESATA compatible"
    by having their launch amplitude and receive sensitivity designed
    so the port could be used with ESATA.

    However, ESATA only seemed to be validated for SATA II, and not SATA III.
    The higher rate may be too much for it. I've never seem a reference
    to the SATAIO standards people, claiming ESATA was ready for SATA III
    (due to cable length).

    With Linux at least, you don't need to wait for the domain validation
    kind of logic to catch up with things.

    https://www.reddit.com/r/archlinux/comments/hegh2r/how_doshould_i_limit_sata_link_speed_on_a_hard/

    https://serverfault.com/questions/400338/how-to-reduce-the-sata-link-speed-of-drive-in-centos/400347#400347

    A kernel boot line of

    libata.force=3.0 # Gear-down all ports

    libata.force=1:3.0G \___ Makes the boot option port specific
    libata.force=2:3.0G /

    In /etc/default/grub where it says "quiet splash", that is where you could add that clause.

    So at least, now I know there is a lever, and it's a matter of studying
    the particular hardware (what chip is being used), to see if it is
    going to work, or seeing what "port numbering issue" might be at play.

    Some boards have a six port Southbridge plus an add-on chip driving two ESATA ports.
    In which case, I don't know how the ports will get numbered or identified.
    The above URLs go into that at bit.

    Paul

    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Axel@3:633/10 to All on Saturday, December 27, 2025 22:36:56
    Axel wrote:
    Paul wrote:
    On Tue, 12/23/2025 12:58 PM, Axel wrote:

    when I do that there's nothing in the right hand pane for grsync

    https://auslink.info/linux/synaptic.png

    grsync is in the menu and loads from the terminal

    I appreciate it very much
    In your picture, you've just done a search on

    ÿÿÿÿ linux_czkawka_gui_x86_64

    and since that is not a .deb and is a portable ELF
    (not packaged properly but still usable), you don't
    expect to find it.

    In your picture, if you'd cursored up or used the mouse
    to select the "grsync" on the left, you would get to review
    the search result for that on the right. And, it would be there.

    I had tried firstly with grsync, as per your example. the result was
    the same, nothing on the right side. my mistake by not highlighting
    grsync for the screenshot.

    https://auslink.info/linux/grsync.png

    why does no package show?



    This is LMDE7.

    ÿÿÿ [Picture]ÿÿ LMDE7-grsync-synaptic.gif

    ÿÿÿÿ https://imgur.com/a/96wnrhS

    I can see the state of the package in the example, and it is
    not installed right now.

    But, the package is available.

    ÿÿÿ Paul





    --
    Linux Mint 22.2
    {I shot Felix and buried him}


    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Axel@3:633/10 to All on Saturday, December 27, 2025 22:59:40
    Paul wrote:
    On Wed, 12/24/2025 1:41 AM, Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    or in a nutshell.. the question now is why did it write to that drive
    and not others? is the size of the drive or it's software/technology
    relevant?
    Maybe that drive (or the NTFS driver) is just too slow for whatever
    signal issue you have with the rack to be triggered.

    I'm not sure if they still do it on new HDDs, but maybe there's a
    jumper setting on the other drives to limit the speed?
    https://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit/s_and_SATA_3_Gbit/s
    No guarantees, but maybe an

    lsusb

    and check the detection on the rack, would give
    some idea of the controller being used.

    That would make it easier to quantify what the rack contains.

    the rack has no electronics in it. it's a straight pass through from the
    drive to the cable via a connector board at the rear


    $ lsusb

    Bus 002 Device 004: ID 045e:076c Microsoft Corp. Comfort Mouse 4500
    ...
    Bus 006 Device 002: ID 174c:1053 ASMedia Technology Inc. USB3.0 Device

    bullwinkle@Legacy:~$ sudo dmesg

    [ 1.681416] scsi host8: uas
    [ 1.681686] usbcore: registered new interface driver uas
    [ 1.682244] scsi 8:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 6
    [ 1.683985] sd 8:0:0:0: [sdb] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
    [ 1.684041] sd 8:0:0:0: [sdb] 4096-byte physical blocks
    [ 1.684193] sd 8:0:0:0: [sdb] Write Protect is off
    [ 1.684237] sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00
    [ 1.684384] sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.725872] sr 2:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
    [ 1.725929] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 1.730920] sd 8:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
    [ 1.730995] sd 8:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
    [ 1.777719] sdb: sdb1 sdb2 sdb3 sdb4 sdb5
    [ 1.778021] sd 8:0:0:0: [sdb] Attached SCSI disk

    *******

    The 174c:1053 gives:

    ASMedia Technology ASM1053 SATA 3Gb/s bridge

    and it is detecting some 8TB drive.

    Paul




    --
    Linux Mint 22.2
    {I shot Felix and buried him}


    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Axel@3:633/10 to All on Saturday, December 27, 2025 23:11:11
    Paul wrote:
    On Tue, 12/23/2025 9:13 PM, Axel wrote:
    Paul wrote:
    On Tue, 12/23/2025 12:58 PM, Axel wrote:

    when I do that there's nothing in the right hand pane for grsync

    https://auslink.info/linux/synaptic.png

    grsync is in the menu and loads from the terminal

    I appreciate it very much
    In your picture, you've just done a search on

    ÿÿÿÿ linux_czkawka_gui_x86_64

    and since that is not a .deb and is a portable ELF
    (not packaged properly but still usable), you don't
    expect to find it.

    In your picture, if you'd cursored up or used the mouse
    to select the "grsync" on the left, you would get to review
    the search result for that on the right. And, it would be there.
    I had tried firstly with grsync, as per your example. the result was the same, nothing on the right side. my mistake by not highlighting grsync for the screenshot.

    https://auslink.info/linux/grsync.png

    This is LMDE7.

    ÿÿÿ [Picture]ÿÿ LMDE7-grsync-synaptic.gif

    ÿÿÿÿ https://imgur.com/a/96wnrhS

    I can see the state of the package in the example, and it is
    not installed right now.

    But, the package is available.

    ÿÿÿ Paul
    I set my search to "Description and Name".

    *******

    yes, that put it in the package side :)

    You can also do it from command line.
    It does not require sudo.

    apt search grsync

    It would normally be followed by

    sudo apt install grsync

    peter@ASUS:~$ apt search linux_czkawka_gui_x86_64
    peter@ASUS:~$ sudo apt install linux_czkawka_gui_x86_64
    [sudo] password for peter:
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    E: Unable to locate package linux_czkawka_gui_x86_64
    peter@ASUS:~$

    ???

    and searching "description and name" doesn't show anything on the
    package side in Synaptic



    Paul


    --
    Linux Mint 22.2
    {I shot Felix and buried him}


    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Axel@3:633/10 to All on Saturday, December 27, 2025 23:16:23
    Computer Nerd Kev wrote:
    In aus.computers Paul <nospam@needed.invalid> wrote:
    On Wed, 12/24/2025 1:41 AM, Computer Nerd Kev wrote:
    In aus.computers Axel <none@not.here> wrote:
    or in a nutshell.. the question now is why did it write to that drive
    and not others? is the size of the drive or it's software/technology
    relevant?
    Maybe that drive (or the NTFS driver) is just too slow for whatever
    signal issue you have with the rack to be triggered.

    I'm not sure if they still do it on new HDDs, but maybe there's a
    jumper setting on the other drives to limit the speed?
    https://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit/s_and_SATA_3_Gbit/s
    No guarantees, but maybe an

    lsusb

    and check the detection on the rack, would give
    some idea of the controller being used.
    He said "swapped the cable to another motherboard (MB) SATA port"
    so that must mean the rack uses SATA connection/s to the
    motherboard, not USB. In that case "lsusb" won't show it. If the
    rack is poorly designed or an old model then maybe it introduces
    too much signal noise for operating at higer data speeds. Or maybe
    there's a bad connection, but he also said he replaced the rack.


    the rack was in perfect condition. only reason I swapped it for a
    (brand) new one is because I had one on hand, and of course to eliminate
    the possibility that the original was defective in some way.

    --
    Linux Mint 22.2
    {I shot Felix and buried him}


    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Saturday, December 27, 2025 08:14:44
    On Sat, 12/27/2025 6:36 AM, Axel wrote:
    Axel wrote:
    Paul wrote:
    On Tue, 12/23/2025 12:58 PM, Axel wrote:

    when I do that there's nothing in the right hand pane for grsync

    https://auslink.info/linux/synaptic.png

    grsync is in the menu and loads from the terminal

    I appreciate it very much
    In your picture, you've just done a search on

    ÿÿÿÿ linux_czkawka_gui_x86_64

    and since that is not a .deb and is a portable ELF
    (not packaged properly but still usable), you don't
    expect to find it.

    In your picture, if you'd cursored up or used the mouse
    to select the "grsync" on the left, you would get to review
    the search result for that on the right. And, it would be there.

    I had tried firstly with grsync, as per your example. the result was the same, nothing on the right side. my mistake by not highlighting grsync for the screenshot.

    https://auslink.info/linux/grsync.png

    why does no package show?


    I don't know why :-)

    The package has been around for a while.

    https://www.opbyte.it/grsync/

    Notice the last release is 2023, but releases aren't all that
    often anyway, so maybe it still receives fixes.

    If a package has no maintainer, it can be remove from a repository.

    It's unlikely that merely "reloading" your Synaptic repository setting
    would cause the status of the package to change. You could try flipping
    to another mirror and flipping back and hope it reloads the files.

    Your LMDE7 should be a strong descendant of Debian Status, as the
    intention of developing LMDE7 was to have a distro ready in case
    Canonical asked the project to find another home. Or in case the
    smell of SNAPs from Ubuntu was too strong to put up with any more.

    You can see it's been in usage for some time on Mint.

    https://community.linuxmint.com/software/view/grsync

    You can see questions like this.

    https://superuser.com/questions/1073336/list-all-packages-from-a-repository

    If I look on my SSD#11 on the Big Machine, this is what I get for LMDE7.
    I am using a Canadian mirror for the repo.

    cd /var/lib/apt/lists # That's the part I didn't copy over here...
    # You can see I'm in that directory when grep runs.
    # The -i is for "case insensitive search"

    /var/lib/apt/lists$ grep -i grsync mirror.csclub.uwaterloo.ca_debian_dists_trixie_main_binary-amd64_Packages

    Package: grsync
    Source: grsync (1.3.1-1)
    Homepage: http://www.opbyte.it/grsync/
    Filename: pool/main/g/grsync/grsync_1.3.1-1+b1_amd64.deb

    Your file in the "lists" folder, will have some similar words on the
    end of the filename, but if you're using a mirror, the mirror name
    will be on the front of that filename.

    The file is "inconvenient", has long lines and xed did not like it.
    So I just used grep for a quick check. If I were to look on my mirror
    (web access), where the pool is stored, I would expect to find that .deb file in there.

    With mirrors, the mirror contents are all supposed to be the same (plus or minus
    some number of hours for propagation). Only if the mirror was un-maintained and the operator wasn't reading the log on the mirror server, could it "lose" something like that. And using Synaptic for a lookup, it isn't likely
    to actually poke at the pool, until you ask to install the package.

    This sort of command line (does not need root), should also do the search.

    apt search grsync

    Maybe your *_debian_dists_trixie_main_binary-amd64_Packages file is corrupted on your disk ?

    Highly unlikely. That never happens :-)

    And even when I use the "Reload" button on Synaptic on the left, this file does not change.

    bullwinkle@FLOTILLA:/var/lib/apt/lists$ ls -al mirror.csclub.uwaterloo.ca_debian_dists_trixie_main_binary-amd64_Packages

    -rw-r--r-- 1 root root 56512991 Nov 15 05:08 mirror.csclub.uwaterloo.ca_debian_dists_trixie_main_binary-amd64_Packages

    bullwinkle@FLOTILLA:/var/lib/apt/lists$ sha256sum !$ # The !$ means use the item off the "end" of the last command

    sha256sum mirror.csclub.uwaterloo.ca_debian_dists_trixie_main_binary-amd64_Packages

    b4c29549115f07775b03dd65494c4df376fd4f4f827f24339edc5d26bc67a119 mirror.csclub.uwaterloo.ca_debian_dists_trixie_main_binary-amd64_Packages

    If all mirrors are working properly, then that's what your file should have for a sha256 sum.

    Paul

    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Saturday, December 27, 2025 08:20:58
    On Sat, 12/27/2025 7:11 AM, Axel wrote:
    Paul wrote:
    On Tue, 12/23/2025 9:13 PM, Axel wrote:
    Paul wrote:
    On Tue, 12/23/2025 12:58 PM, Axel wrote:

    when I do that there's nothing in the right hand pane for grsync

    https://auslink.info/linux/synaptic.png

    grsync is in the menu and loads from the terminal

    I appreciate it very much
    In your picture, you've just done a search on

    ÿÿÿÿÿ linux_czkawka_gui_x86_64

    and since that is not a .deb and is a portable ELF
    (not packaged properly but still usable), you don't
    expect to find it.

    In your picture, if you'd cursored up or used the mouse
    to select the "grsync" on the left, you would get to review
    the search result for that on the right. And, it would be there.
    I had tried firstly with grsync, as per your example. the result was the same, nothing on the right side. my mistake by not highlighting grsync for the screenshot.

    https://auslink.info/linux/grsync.png

    This is LMDE7.

    ÿÿÿÿ [Picture]ÿÿ LMDE7-grsync-synaptic.gif

    ÿÿÿÿÿ https://imgur.com/a/96wnrhS

    I can see the state of the package in the example, and it is
    not installed right now.

    But, the package is available.

    ÿÿÿÿ Paul
    I set my search to "Description and Name".

    *******

    yes, that put it in the package side :)

    You can also do it from command line.
    It does not require sudo.

    ÿÿÿ apt search grsync

    It would normally be followed by

    ÿÿÿ sudo apt install grsync

    peter@ASUS:~$ apt search linux_czkawka_gui_x86_64
    peter@ASUS:~$ sudo apt install linux_czkawka_gui_x86_64
    [sudo] password for peter:
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    E: Unable to locate package linux_czkawka_gui_x86_64
    peter@ASUS:~$

    ???

    and searching "description and name" doesn't show anything on the package side in Synaptic

    The linux_czkawka_gui_x86_64 file is NOT a .deb and is NOT in
    the repository as such. That is release 10, the Synaptic has the
    release 8 or so in .deb form. That is a "hot-off-the-press" and
    "unvetted goods" with all the dangers entailed in such.

    It's not a surprise as a result, that picking that name spells failure.

    You can search on "czkawka" and as a wild card any string with that
    as a substring should show up. There should be a reference to that
    older package you did not like (too small preview).

    Paul

    --- PyGate Linux v1.5.2
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)