• Re: RPi desktop on a Acer Aspire TC-780 - any gotya's ?

    From The Natural Philosopher@3:633/10 to All on Friday, November 20, 2026 15:45:02
    On 20/11/2026 15:38, R.Wieser wrote:
    Theo,

    If you keep some amount like 10% of the SSD zeroed then the
    controller can use those blocks to improve the wear lifetime
    ('over provisioning').

    Do you mean unpartitioned, or would something special (zeroed?) be needed ?

    And thanks for the suggestion.

    Regards,
    Rudy Wieser


    I've been using swap on SSD on this machine for several years. No issues
    at all

    I think one key thing is use a much bugger drive than you (think you)
    need. I have 250GB here and use about 130GB


    --
    "What do you think about Gay Marriage?"
    "I don't."
    "Don't what?"
    "Think about Gay Marriage."



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Theo@3:633/10 to All on Friday, November 20, 2026 16:16:58
    In comp.sys.raspberry-pi R.Wieser <address@is.invalid> wrote:
    Theo,

    If you keep some amount like 10% of the SSD zeroed then the
    controller can use those blocks to improve the wear lifetime
    ('over provisioning').

    Do you mean unpartitioned, or would something special (zeroed?) be needed ?

    'Empty'. When you delete a file, typically filesystems tell the device that the blocks are no longer used (this is called 'TRIM') and it can put them
    back into the empty block pool. The more empty blocks there are, the more breathing space the SSD has to use when parts of the flash wear out.

    If you zero blocks, the SSD can also decide they're 'empty'. If you leave parts unpartitioned but still containing data from the last time it was
    used, the SSD is still contractually obliged to keep the data in case you
    need it another time and so it can't reallocate them to cover wear.

    Just making a big file and then deleting it is usually enough to trigger
    TRIM of the blocks, but also zeroing the SSD and then leaving 10% (or
    whatever) unpartitioned works too.

    This can also help with 'performance consistency': if you want to write but
    the SSD has to do a lot of juggling to find an empty block, maybe erasing
    and shuffling some other blocks, then you can get erratic performance under heavy load. But that's only really an issue with big write workloads like database servers, not domestic desktop use.

    Theo

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Richard Kettlewell@3:633/10 to All on Friday, November 20, 2026 17:39:44
    "R.Wieser" <address@is.invalid> writes:
    Theo,
    'Empty'. When you delete a file, typically filesystems tell the
    device that the blocks are no longer used

    Off by default in ext4, I believe.

    Ah, you mean I should never fully use the whole partition ("Used
    space" vs "Free space"). With 128GB to work with I'm not going to
    worry about that. :-)

    If you zero blocks, the SSD can also decide they're 'empty'.

    I don't understand : when a block is not part of any file chain than its unused. The wear-leveling process could commandeer such blocks at any
    time - even though that could twart a later "undelete" attempt.

    The drive doesn?t know which (logical) blocks are not part of a file,
    unless the OS tells it.

    --
    https://www.greenend.org.uk/rjk/

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From R.Wieser@3:633/10 to All on Friday, November 20, 2026 16:38:22
    Theo,

    If you keep some amount like 10% of the SSD zeroed then the
    controller can use those blocks to improve the wear lifetime
    ('over provisioning').

    Do you mean unpartitioned, or would something special (zeroed?) be needed ?

    And thanks for the suggestion.

    Regards,
    Rudy Wieser



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From R.Wieser@3:633/10 to All on Friday, November 20, 2026 18:29:41
    Theo,

    'Empty'. When you delete a file, typically filesystems tell the
    device that the blocks are no longer used

    Ah, you mean I should never fully use the whole partition ("Used space" vs "Free space"). With 128GB to work with I'm not going to worry about that.
    :-)

    If you zero blocks, the SSD can also decide they're 'empty'.

    I don't understand : when a block is not part of any file chain than its unused. The wear-leveling process could commandeer such blocks at any
    time - even though that could twart a later "undelete" attempt.

    Hmmm ... Does Linux even have an "undelete" method ?

    Also, files can contain lots of zeroes. How will the wear-leveling
    mechanism know that such in-use blocks filled with zeroes should not be
    taken ?

    If you leave parts unpartitioned but still containing data from
    the last time it was used, the SSD is still contractually obliged
    to keep the data in case you need it another time

    That doesn't make any sense. The data in blocks not part of any partition
    (or file!) needs to be kept ? For what reason ?

    but also zeroing the SSD and then leaving 10% (or whatever)
    unpartitioned works too.

    Again, I do not understand. The blocks in the unpartitioned area might be zeroed out, but the moment the wear-leveling mechanism swaps such a block
    out with one inside a partition that swapped-out block now in the unpartitioned area is going to contain data.

    Regards,
    Rudy Wieser



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From R.Wieser@3:633/10 to All on Saturday, November 21, 2026 09:54:52
    Richard,

    The drive doesn't know which (logical) blocks are not part of
    a file, unless the OS tells it.

    Inxdeed. I mixed up the drive smarts with the filesystem the OS puts on the drive.

    iow, the drive has no concept of used and non-used blocks. It just goes for the (write)usage-count of each block on its drive. Contents are irrelevant. It could swap two blocks that are both in use by a partition and the filesystem on it.

    The /only/ reason I could imagine for having blocks in their erased state
    (not sure if that is all zeroes or all ones) is that, when swapping such a block in, the erase cycle could be skipped - making it a bit faster.

    Regards,
    Rudy Wieser



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Paul@3:633/10 to All on Sunday, November 22, 2026 08:24:50
    On Sat, 11/21/2026 5:42 AM, Andy Burns wrote:
    "R.Wieser" wrote:

    Unless ... there is some gotya there ofcourse.ÿÿ Is there ?
    Given you don't care about the existing windows installation, I have a suggestion ... stop looking for gotchas, boot it from usb, nuke the disk contents, let PiOS choose its default partitioning scheme on the 128GB M.2 drive, leave the 1TB drive for later use.

    Standard best practice for installations, is to unplug the
    things you do not want the installer to use.

    That's so boot materials do not end up on the drive
    opposite the one that got the OS files.

    Some people who come to USENET, have the most convoluted
    combination of GRUB on this disk, they unplug something,
    something else no longer boots and so on. A royal mess.
    Criss-cross boot materials. And a royal mess, means you're
    wasting personal time, every time you have to sort that out.

    The OP probably doesn't even know that modern installers
    have a UEFI bias, some curb-side machines have legacy BIOS,
    and installing on them is extra difficult, because the
    small-BIOS-partition is missing, and the *installer*
    will not make one for you. You have to know that partition
    is necessary, you can pre-stage it using gparted. But you
    can only be doing that, if you happen to know about the
    Legacy thing.

    There was a time, when boot media was Hybrid, and it
    did not have a bias, and it treated Legacy and UEFI
    machines with the same level of respect. Certain people
    in the industry have an axe to grind now, which is
    why they treat Legacy machines badly.

    Paul

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From The Natural Philosopher@3:633/10 to All on Saturday, November 21, 2026 12:37:53
    On 21/11/2026 11:55, R.Wieser wrote:
    And yes, nuking whats on the drive(s) and and installing Linux is what my initial thought was. I just wanted to make sure that I would not run into any known problems - to anyone in these newsgroups - while attempting to do so.

    Mind you, it would be my first time installing this OS as well as doing it
    on a 64-bit UEFI 'puter. Don't blame me for being a bit carefull.
    Fairy Nuff.

    Only issue I had last time I had an issue was needing to cycle through
    various boot options in the BIOS before I found one that worked, I think secure boot and legacy boot did not, but UEFI did...several years now. I forget.

    Once that hurdle was cleared it was painless

    --
    "When one man dies it's a tragedy. When thousands die it's statistics."

    Josef Stalin



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From R.Wieser@3:633/10 to All on Saturday, November 21, 2026 12:55:22
    Andy,

    Unless ... there is some gotya there ofcourse. Is there ?

    Given you don't care about the existing windows installation, I have a suggestion ... stop looking for gotchas, boot it from usb, nuke the disk contents, let PiOS choose its default partitioning scheme on the 128GB M.2 drive, leave the 1TB drive for later use.

    Are you aware of any possible gotya's in your above-described process ?

    Nothing about the UEFI possibly being difficult for example ? Nothing about
    a Linux stub for it that needs to be pre-configured ? Maybe the Linux ISO needs some kind of special handling? Or a reason why I would not be able
    to boot the Linux ISO from USB on 64bit hardware ?

    That is the kind of gotya's I'm asking about.

    And yes, nuking whats on the drive(s) and and installing Linux is what my initial thought was. I just wanted to make sure that I would not run into any known problems - to anyone in these newsgroups - while attempting to do so.

    Mind you, it would be my first time installing this OS as well as doing it
    on a 64-bit UEFI 'puter. Don't blame me for being a bit carefull.

    Regards,
    Rudy Wieser



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From mm0fmf@3:633/10 to All on Saturday, November 21, 2026 12:40:59
    On 21/11/2026 10:42, Andy Burns wrote:
    "R.Wieser" wrote:

    Unless ... there is some gotya there ofcourse.ÿÿ Is there ?
    Given you don't care about the existing windows installation, I have a suggestion ... stop looking for gotchas, boot it from usb, nuke the disk contents, let PiOS choose its default partitioning scheme on the 128GB
    M.2 drive, leave the 1TB drive for later use.

    Rudi has no intention of doing anything. This is typical of most of his trolling posts. Ask a question. Respond to each answer with why the
    answer is sub-optimal for his specific instance. Garner further
    responses from people trying to help and knock them back. Lather, rinse, repeat.

    Just look at his output in the archives for proof.

    Your suggestion is eminently sensible. He got the computer for free so
    even if he totals it to a non-booting hulk, he's lost nothing and can
    always strip it for parts. But his response to your suggestion is to
    offer more possible things that could go wrong and hope he can continue
    the trolling.

    A normal person would have just downloaded the ISO to a USB stick and
    tried it. But Rudi's trolling as per.



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From R.Wieser@3:633/10 to All on Saturday, November 21, 2026 10:14:38
    Paul,

    I can boot into Win10 alright, but than I'm shown a user-login screen.
    Which I can't pass (?). So, no access to Disk Management either (?).

    A technical challenge then :-)

    OK, now I see why you're in a paving mood.

    One problem is, there were some nice (reasonably easy)
    hacks to become Administrator while booting.

    I could do all that you described there, but I do not really see the need
    for it (other than to gain some insight into Win10 that I will never use). I only powered the 'puter up because I wanted to check if it still functioned
    (I took it from the curb, so it could have been a paperweight).

    I'm assuming that the Linux installation media includes a way to do some
    disk management (like Windows does on its installation media), and thats al
    I need. Heck, it might even make suggestions ! :-)

    Unless ... there is some gotya there ofcourse. Is there ?

    (nonwithstanding, I saved your post for post for eventual future use)

    Regards,
    Rudy Wieser



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From R.Wieser@3:633/10 to All on Saturday, November 21, 2026 14:40:26
    mm0fmf,

    Rudi has no intention of doing anything. This is typical of most of his trolling posts. Ask a question. Respond to each answer with why the
    answer is sub-optimal for his specific instance.

    Really ? I asked a question which, as to date , *noone* has even
    acknowledged - even though I made quite clear I wanted to have it answered
    (a "none that I know of" would have been enough).

    The other responses, like what kind of drive I would actually have or how wear-leveling works or how the drives are partitioned and formatted under Windows ? Interresting, but in no way anything that would have any
    influence to if I would be able to install Linux.

    ... or it would fall under the "gotya's" I asked for.

    Iow, next time think you see me "rejecting" something, ask yourself how it
    is of any consequence to the question I asked. If its not, than do perhaps realize that its *you* are who is refusing to answer the question.

    A normal person would have just downloaded the ISO to a USB stick
    and tried it. But Rudi's trolling as per.

    A *normal* person would, before engaging in something new to them, ask
    people around them if they have any advice.

    You ? You implicitily claim you just ... do something - and than ofcourse, when
    something goes wrong, complain about how you could not have known that.
    Yeah, duh!

    Regards,
    Rudy Wieser



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