Skip to content

Fix show platform ssdhealth not showing expected output when a usb flash drive is plugged in#3833

Merged
judyjoseph merged 1 commit intosonic-net:masterfrom
tirupatihemanth:hemkt/ssdhealth
Apr 14, 2025
Merged

Fix show platform ssdhealth not showing expected output when a usb flash drive is plugged in#3833
judyjoseph merged 1 commit intosonic-net:masterfrom
tirupatihemanth:hemkt/ssdhealth

Conversation

@tirupatihemanth
Copy link
Copy Markdown
Contributor

Fix show platform ssdhealth not showing expected output when a usb flash drive is plugged in.

What I did

When 'show platform ssdhealth' is not supplied with a device name and a usb flash drive is attached we show incorrect output as we deduce incorrect device name from 'lsblk' command and pass it to ssdutil. I removed this incorrect deduction of the device name.

How I did it

Instead of incorrectly deducing the device using the lsblk command we can instead not pass any device name as argument to the ssdutil and it will automatically choose the device on which /host partition is mounted which is the primary storage device in our case as per the PR: #3399

How to verify it

Run sudo show platform ssdhealth without any arguments with a flash drive plugged into the sonic switch.

Previous command output (if the output of a command-line utility has changed)

root@qa-eth-vt19-1-4280:~# show platform ssdhealth
Disk Type    : NVME
Device Model : N/A
Health       : N/A
Temperature  : N/A

New command output (if the output of a command-line utility has changed)

root@qa-eth-vt19-1-4280:/home/admin# show platform ssdhealth
Disk Type    : NVME
Device Model : Virtium VTPM24CEXI080-BM110006
Health       : 100.0%
Temperature  : 51.0C

In the case where the user passes the device name as argument to the command (show platform ssdhealth /dev/nvme0n1) output remains the same and no changes have been made.

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@tirupatihemanth
Copy link
Copy Markdown
Contributor Author

/azpw run

@mssonicbld
Copy link
Copy Markdown
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@tirupatihemanth
Copy link
Copy Markdown
Contributor Author

/azpw run

@mssonicbld
Copy link
Copy Markdown
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@tirupatihemanth
Copy link
Copy Markdown
Contributor Author

/azpw run

@mssonicbld
Copy link
Copy Markdown
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@liat-grozovik
Copy link
Copy Markdown
Collaborator

@prgeor @keboliu as this is general change i would appreciate your approval as platform changes PIC.
from Nvidia POV this is approved and working.

Copy link
Copy Markdown
Contributor

@judyjoseph judyjoseph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@judyjoseph judyjoseph merged commit b6e2102 into sonic-net:master Apr 14, 2025
7 checks passed
@judyjoseph
Copy link
Copy Markdown
Contributor

judyjoseph commented Apr 14, 2025

Please add any branches it needs to be cherry-picked @tirupatihemanth @liat-grozovik

@mssonicbld
Copy link
Copy Markdown
Collaborator

Cherry-pick PR to msft-202412: Azure/sonic-utilities.msft#166

nmoray pushed a commit to nmoray/sonic-utilities that referenced this pull request Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants