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
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 ?
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.
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').
'Empty'. When you delete a file, typically filesystems tell the
device that the blocks are no longer used
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
but also zeroing the SSD and then leaving 10% (or whatever)
unpartitioned works too.
The drive doesn't know which (logical) blocks are not part of
a file, unless the OS tells it.
"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.
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.Fairy Nuff.
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.
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.
"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.
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.
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.
A normal person would have just downloaded the ISO to a USB stick
and tried it. But Rudi's trolling as per.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498678:25:31 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 912 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,867 |