On Wed, Jan 15, 2025 at 1:37 AM David Christensen <dpchr...@holgerdanske.com> wrote: > > On 1/14/25 10:13, Adam Weremczuk wrote: > > On 14/01/2025 17:02, Michael Stone wrote: > >> On Tue, Jan 14, 2025 at 03:30:17PM +0000, Adam Weremczuk wrote: > >>> I need NTFS to connect it to a WS 2019 machine later. > >> ... (Storage fraud really is a thing, where people sell drives > >> that have less storage than reported, on the theory that most people > >> won't fill it up in time to get their money back.) > >> > > I bought the drive from Amazon and everything looks very genuine. > > > > Nvme tool reports: > > > > $ sudo nvme list > > > > Node SN Model Namespace > > Usage Format FW Rev > > --------------------- -------------------- > > ---------------------------------------- --------- > > -------------------------- ---------------- -------- > > /dev/nvme0n1 S7DSNJ0X910743Z Samsung SSD 990 PRO with > > Heatsink 4TB 1 1.19 TB / 4.00 TB 512 B + 0 B > > 4B2QJXD7 > > > > The firmware seems to be the latest version: https:// > > semiconductor.samsung.com/consumer-storage/support/tools/ > > > > I'm giving exfat a shot and so far I'm impressed with 160 MB/s average > > transfer rate (HDD -> NVMe). > > > > That's significantly faster than before. > > > > Partially because I'm using "rsync -avh --no-perms --no-group --no- > > owner ..." this time. > > I suggest that you unmount any filesystems on the SSD and then fill the > SSD with random bytes using dd(1). Something like: > > # time dd if=/dev/randome of=/dev/nvme0n1 bs=1m status=progress > > Alternatively, fill the drive using a PRNG so that you can read the > stream back and validate it.
Probably better since disk controllers often use compression to minimize writes and blocks written during a write cycle. A pseudo random stream will defeat compression and ensure a write of the expected size actually takes place. > Please post the complete console session -- prompt(s), command(s) > issued, and output displayed. Jeff
