[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: testing new sdm drive



Alexander V. Makartsev writes:

On 08.02.2024 12:14, gene heskett wrote:
gene@coyote:/etc$ sudo smartctl --all -dscsi /dev/sdm
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, <URL:http://www.smartmontools.org>www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:
Product:              SSD 3.0

[...]

Looks like a scam. Probably a reprogrammed controller to falsely report 2TB of space to the system.

I support this view :)

This is how I would test it.
First create a new GPT partition table and a new 2TB partition:
    $ sudo gdisk /dev/sdX

/!\  Make double sure you've selected the right device by using "lsblk" and "blkid" utilities.  /!\ /!\                            It could change from 'sdm' to another name after reboot.                              /!\

At gdisk prompt press "o" to create a new GPT table, next press "n" to create a new partition, accept default values by pressing "enter". To verify setup press "p", to accept configuration and write it to device press "w".

Next format partition to ext4 filesystem:
    $ sudo mkfs.ext4 -m 0 -e remount-ro /dev/sdX1

Next mount the filesystem:
    $ sudo mkdir /mnt/disktest
    $ sudo mount /dev/sdX1 /mnt/disktest

Next create reference 1GB file filled with dummy data:
    $ cd /mnt/disktest

From here on I'd suggest trying the tools from package `f3`.

After installing it, find the documentation under
/usr/share/doc/f3/README.rst.gz. Basic usage requires only two commands:

	f3write .

Fills the drive until it is full (No Space Left on Device). Umount and re- mount it to ensure that data is actually written to the disk. Then switch back to /mnt/disktest and read it back using

	f3read .

It should output a tabular summary about what could be read successfully and what couldn't.

As to whether this affects the stability of the running system: If the drive is fake (which I think is a real possibility) then it may as well cause hickups in the system. If the work you are doing on the machine is mission- critical, don't run tests with suspect hardware on it...

HTH
Linux-Fan

öö

[...]

Attachment: pgpce2yakp2s1.pgp
Description: PGP signature


Reply to: