Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug - Adjusting nvsdkmanager_flash.sh to avoid 14GB nvme SSD partition #45

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rhysdg
Copy link

@rhysdg rhysdg commented May 28, 2024

  • Adding a quick change to flash_jetson_external_storage.sh that modifies `nvsdkmanager_flash.sh at the current L4T version
  • Without this change flashing resulted in a 14GB partition that was difficult to change with gparted due to the fact that it was the the system root/ used for boot etc
  • the solution that lead to this quick change was taken from this tech support [solution] (https://forums.developer.nvidia.com/t/jetpack-5-1-2-l4t-35-4-1-is-now-live/262035/5)

Environment

  • Ubuntu 22.04 (Host)
  • Jetson NX Xavier 8GB Development Kit (Target)
  • Jetson AGX Xavier 32GB Development Kit (Target)

Test Results - Tested succesfully for changes with Jetpack 5.4.1 and a 500GB WD Blue NVMe SSD

@rhysdg rhysdg changed the title Bug - Adjusting nvsdkmanager_flash.sh to handle large nvme Bug - Adjusting nvsdkmanager_flash.sh to handle large nvme SSD May 28, 2024
@rhysdg rhysdg changed the title Bug - Adjusting nvsdkmanager_flash.sh to handle large nvme SSD Bug - Adjusting nvsdkmanager_flash.sh to avoid 14GB nvme SSD partition May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant