Can I Use External SSD Drive as Primary Storage ?

I am running on Jetpack 2 and i am thinking to add external SSD drive and Merge it with it’s default Storage to use as Primary Storage for like installing Programs or something else

Regards

At this time the most recent JetPack is 3.0, so you might consider upgrading (you can check “head -n 1 /etc/nv_tegra_release” and look for something like “# R27 (release), REVISION: 1.0…” to see if you have the most recent L4T R27.1 version).

Merging two disks as a single disk would be a RAID and/or LVM setup. Due to boot limitations it seems unlikely that you could combine eMMC with an arbitrary disk without some serious difficulties (the U-Boot boot loader would have to be modified to understand RAID and/or LVM).

An alternative to consider is that you could just boot to eMMC and then mount the SSD to a directory. Anything going in that directory would run from SSD while retaining the rest of eMMC. An example is that you could replace “/home” or “/usr/local” with the SSD (or both if you partition the SSD with two partitions). I suppose it might also be possible to cover the SSD with LVM and dynamically change how a mount to both “/home” and “/usr/local” divide up space. It depends on how much trouble you will go to to understand the features…mounting a partition is easy, learning LVM has a learning curve.

@linuxdev Thanks Buddy i already update my Tx2 to L4T R27.1 version . i will let you know the results

Cheers

linuxdev:
May I pick up your brain for a moment:
I am trying to diagnoze sata 2tb samsung hdd intended for laptops
st20000LM007 and it returns the following scriptures:

7.306727] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 7.644846] tegradc 15210000.nvdisplay: hdmi: plugged
[ 9.036460] ata1.00: ATA-10: ST2000LM007-1R8174, SBK2, max UDMA/133
[ 9.043654] ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 9.228250] ata1.00: configured for UDMA/133
[ 9.233640] scsi 0:0:0:0: Direct-Access ATA ST2000LM007-1R81 SBK2 PQ: 0 ANSI: 5
[ 9.243003] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 9.251700] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 9.257933] sd 0:0:0:0: [sda] Write Protect is off
[ 9.263665] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 9.263698] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[ 39.858723] ata1.00: exception Emask 0x0 SAct 0x1000000 SErr 0x150000 action 0x6 frozen
[ 39.867840] ata1: SError: { PHYRdyChg CommWake Dispar }
[ 39.874127] ata1.00: failed command: READ FPDMA QUEUED
[ 39.880347] ata1.00: cmd 60/08:c0:a8:88:e0/00:00:e8:00:00/40 tag 24 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.897286] ata1.00: status: { DRDY }
[ 39.902113] ata1: hard resetting link
[ 49.898714] ata1: softreset failed (1st FIS failed)
[ 49.904849] ata1: hard resetting link
[ 59.906716] ata1: softreset failed (1st FIS failed)
[ 59.912845] ata1: hard resetting link
[ 64.310766] xhci-tegra 3530000.xhci: cannot find firmware…retry after 1 second
[ 65.318742] xhci-tegra 3530000.xhci: Direct firmware load for tegra18x_xusb_firmware failed with error -2
[ 65.329639] xhci-tegra 3530000.xhci: Falling back to user helper
[ 94.914714] ata1: softreset failed (1st FIS failed)
[ 94.921005] ata1: limiting SATA link speed to 1.5 Gbps
[ 94.927563] ata1: hard resetting link
[ 99.958702] ata1: softreset failed (device not ready)
[ 99.965229] ata1: reset failed, giving up
[ 99.970660] ata1.00: disabled
[ 99.975018] ata1.00: device reported invalid CHS sector 0
[ 99.981821] ata1: EH complete
[ 99.986140] sd 0:0:0:0: [sda] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
[ 99.995778] sd 0:0:0:0: [sda] tag#26 CDB: opcode=0x28 28 00 e8 e0 88 a8 00 00 08 00
[ 100.004819] blk_update_request: I/O error, dev sda, sector 3907029160
[ 100.012671] Buffer I/O error on dev sda, logical block 488378645, async page read

Advise desired.
Thanks.

Does the following is the ssd could be used as functioning:

dmesg | grep ata1
[    2.644972] ata1: SATA max UDMA/133 mmio [mem 0x03507000-0x03508fff] port 0x100 irq 25
[    7.306727] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    9.036460] ata1.00: ATA-10: ST2000LM007-1R8174, SBK2, max UDMA/133
[    9.043654] ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    9.228250] ata1.00: configured for UDMA/133
[   39.858723] ata1.00: exception Emask 0x0 SAct 0x1000000 SErr 0x150000 action 0x6 frozen
[   39.867840] ata1: SError: { PHYRdyChg CommWake Dispar }
[   39.874127] ata1.00: failed command: READ FPDMA QUEUED
[   39.880347] ata1.00: cmd 60/08:c0:a8:88:e0/00:00:e8:00:00/40 tag 24 ncq 4096 in
[   39.897286] ata1.00: status: { DRDY }
[   39.902113] ata1: hard resetting link
[   49.898714] ata1: softreset failed (1st FIS failed)
[   49.904849] ata1: hard resetting link
[   59.906716] ata1: softreset failed (1st FIS failed)
[   59.912845] ata1: hard resetting link
[   94.914714] ata1: softreset failed (1st FIS failed)
[   94.921005] ata1: limiting SATA link speed to 1.5 Gbps
[   94.927563] ata1: hard resetting link
[   99.958702] ata1: softreset failed (device not ready)
[   99.965229] ata1: reset failed, giving up
[   99.970660] ata1.00: disabled
[   99.975018] ata1.00: device reported invalid CHS sector 0
[   99.981821] ata1: EH complete

Perhaps there should be some specific tool for diagnosis from the manufacturer

I don’t know for sure what is going on, but it sounds like an error in the physical routing (signal quality problems or electrical fault). Probably one of the best tests is to see how the drive works on another computer, and to also test a similar drive known to work on another computer on this Jetson. The CHS being invalid seems to be from a query of the hardware function and not from data which is written to disk space (the drive’s side of hardware control versus something saved on the drive).

One possible query tool might be the smartdrive command:

sudo smartctl --all /dev/sda
# Or possibly with "-d sat" if it can't figure out the device:
sudo smartctl --all -d sat /dev/sda

Incidentally, I think there is some information stored on the disk itself and errors might be recorded.

thank you for your advice,
I have manage to test other functioning device that way

I am curious if the drive or its cable turned out to be bad?

that is a good question;
I used to test “non-functioning” seagate external hdd which I directly without cable lugged to the jetson corresponding input. That makes me feel that cable is not the issue. I downloaded some seagate tool for windows which displayed fails on the driver test.
In my opinion, unless the manufacturers advises something - the cause is rather the drive, not cable which results in non-functioning.
Thanks for following up!