Announcement

Collapse
No announcement yet.

3 programs truncate, missing fields.

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    3 programs truncate, missing fields.

    Problem:
    3 of 4 Kubuntu programs truncate, fields missing.
    Note difference below in Disk model field:

    Code:
      
    WD Blue SA510 M.2 2280 1000GB    lsblk from util-linux 2.37.2  
    WD Blue SA510 M.                 fdisk from util-linux 2.37.2  
    WD Blue SA510 M.                sfdisk from util-linux 2.37.2
ATA WD Blue SA510 M. (scsi)         parted (GNU parted) 3.4
    Who to notify?
    Where to post this? web page?
    How can the code writer be notified of above missing information?


    details ...


    A drive was purchased.
    WD (Western Digital) M.2 sata 1TB 2280

    drive is raw from store
    drive is not partitioned
    drive is not formatted, no filesystem, yet


    with Kubuntu 22.04


    Code:
    lsblk --version  
lsblk from util-linux 2.37.2
    Code:
      
lsblk -ido KNAME,TYPE,SIZE,MODEL |grep -i 'sd\|disk\|size'  
 
KNAME   TYPE   SIZE MODEL  
sda     disk 931.5G WD Blue SA510 M.2 2280 1000GB
    .


    Code:
      
fdisk --version  
fdisk from util-linux 2.37.2
    Code:
      
sudo fdisk -l /dev/sda  
 
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WD Blue SA510 M.
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
    .

    Code:
      
sfdisk --version  
sfdisk from util-linux 2.37.2
    Code:
      
sudo sfdisk -l /dev/sda  
 
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WD Blue SA510 M.
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
sfdisk: cannot open  : No such file or directory
    .

    Code:
      
parted --version  
parted (GNU parted) 3.4
    Code:
      
sudo parted -l  
  
Error: /dev/sda: unrecognised disk label
Model: ATA WD Blue SA510 M. (scsi)                                        
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

    --​
    Tags: desktop, kubuntu
    • Top
    • Bottom
    #2
    I'm not seeing those results here and you don't say whether or not your other drives show the same results.

    It's also unclear as to why this is a "problem." I can't think of a reason why it matters much. you're not going to use the drive label for anything that I can think of.

    What's the output of sudo smartctl -i /dev/sda | grep 'Device Model'

    If you just want to make a bug report, it's probably a Western Digital issue unless you can repeat the results with another device.

    Please Read Me
    • Top
    • Bottom

    Comment

      #3
      Originally posted by oshunluvr View Post
      What's the output of
      sudo smartctl -i /dev/sda | grep 'Device Model'

      sudo smartctl -i /dev/sda | grep 'Device Model'
      Code:
      Device Model:     WD Blue SA510 M.2 2280 1000GB
      Code:
      smartctl --verison
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-70-generic] (local build)
      Thus smartctl 7.2 agrees with lsblk :
      WD Blue SA510 M.2 2280 1000GB

      .

      Two other drives plugged-in do not have a period in their name.
      do not have a period . as in M.2
      Code:
      lsblk -ido KNAME,TYPE,SIZE,MODEL |grep -i 'sd\|disk\|size'  
KNAME   TYPE   SIZE MODEL
sda     disk 931.5G WD Blue SA510 M.2 2280 1000GB
sdb     disk  29.2G Extreme
nvme0n1 disk 465.8G KINGSTON SNVS500G

      We have:
      2 of 5 programs show full name (Device Model)
      3 of 5 programs show truncating in mid-field of M.2 at the period.
      Code:
        
    WD Blue SA510 M.2 2280 1000GB    smartctl 7.2 2020-12-30
    WD Blue SA510 M.2 2280 1000GB    lsblk from util-linux 2.37.2  
    WD Blue SA510 M.                 fdisk from util-linux 2.37.2  
    WD Blue SA510 M.                sfdisk from util-linux 2.37.2
ATA WD Blue SA510 M. (scsi)         parted (GNU parted) 3.4
      ​
      • Top
      • Bottom

      Comment

        #4
        The fdisk, sfdisk
        Originally posted by joseph22 View Post
        Who to notify?
        Where to post this? web page?
        How can the code writer be notified of above missing information?
        The developers of these utilities, but just as likely to be WD's formatting of the info?
        Maybe check out their bug/issues:
        https://github.com/util-linux/util-linux/issues


        I am not seeing this on mine, which includes a WD stick, as well as another that has 'M.2' in the model name:
        Code:
        sudo fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDS100T3X0C-00SJG0
        Code:
        sudo fdisk -l /dev/nvme1n1
Disk /dev/nvme1n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: SPCC M.2 PCIe SSD
        ​
        Code:
        sudo fdisk -l /dev/sda
Disk /dev/sda: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: SPCC Solid State
        Code:
        $ sudo parted -l
Model: ATA SPCC Solid State (scsi)


Model: WDS100T3X0C-00SJG0 (nvme)


Model: SPCC M.2 PCIe SSD (nvme)

        It makes me think that something about the model name is triggering this.
        ​

        ​
        • Top
        • Bottom

        Comment

        • oshunluvr
          #4.1
          oshunluvr commented
          Apr 19, 2023, 10:44 AM
          Editing a comment
          Agreed. Seems like an unprintable character got in the device name somehow.
          • Top
          • Bottom
        #5
        more examples of truncated fields:

        grep . /sys/class/block/sd*/device/model
        Code:
        /sys/class/block/sda/device/model:WD Blue SA510 M.
/sys/class/block/sdc/device/model:Extreme

        sudo lshw -class disk |grep 'product:'
        Code:
        product: Extreme
product: WD Blue SA510 M.
        ​
        • Top
        • Bottom

        Comment

          #6
          Originally posted by claydoh View Post
          It makes me think that something about the model name is triggering this.
          ​​
          Does above suggest these 2 program filter out non-printables?
          smartctl 7.2 2020-12-30 and
          lsblk from util-linux 2.37.2

          Resulting in:
          WD Blue SA510 M.2 2280 1000GB


          .


          To test, What command can be done?
          How to pull fields from drive to test for non-printables? in:
          WD Blue SA510 M.2 2280 1000GB

          For example:
          grep '[^[:print:]]' filePath

          reference:
          https://stackoverflow.com/questions/25720471/how-to-find-non-printable-characters-in-the-file

          --​
          • Top
          • Bottom

          Comment

            #7
            No clue. Far too technical for me, and unfortunately far too unimportant to take up too much of my workday to go down any rabbit holes.

            Who knows what these tools are using to parse the info, it could be perl or any other number of things. Don't know what sort of format the devices use to record this on the device's firmware or wherever they stash this - it ain't gonna be a text file. May even require actual hardware tools to see it directly.
            I linked to the tools' home (or rather the home of lsblk, sfdisk and fdisk), the Issues page specifically. Maybe search around there for anyone else seeing this?
            It isn't something at the desktop level and likely isn't even at the Ubuntu level. You might need to find more general Linux venue that has more low-level Linux and hardware expertise that our tiny corner of Linux-land.

            I still say it is something on WD's end. A small bit of non-standard encoding or hex, or whatever. But not off enough to show a problem in Windows (assuming it shows correctly there).
            My drive with 'm.2'' doesn't exhibit this behavior, so it seems logical enough.
            Last edited by claydoh; Apr 19, 2023, 03:41 PM.
            • Top
            • Bottom

            Comment

            Previous template Next
            Working...
            X