thatchunkylad198966
Posts: 126
Joined: Thu Jul 04, 2019 10:21 am
Location: UK, Birmingham

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Sat Jul 06, 2019 5:29 pm

Damn...
I was awake until 7am the other morning trying to get it to boot with /boot on the SDCARD and ROOTFS on my SSD via USB to SATA.
After reading this, think I'll try again!

Awesome. :D
One man's trash is another man's treasure! :) Pi's I have; Pi Zero, Pi Zero W, Pi 2 x2, Pi 3 x2, Pi 4 4GB x2.

thatchunkylad198966
Posts: 126
Joined: Thu Jul 04, 2019 10:21 am
Location: UK, Birmingham

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Sat Jul 06, 2019 5:36 pm

romprod wrote:
Sat Jul 06, 2019 2:46 pm
I've just this minute figured out why it wouldn't work....

So, found out that it would work using the PARTUUID method as per the guides etc but only when plugged into the USB2 socket.

The I found this site https://wiki.odroid.com/odroid-xu4/soft ... _fw_update and updated the firmware as below

Code: Select all

sudo ./JMS578FwUpdate -d /dev/sda -v
Bridge Firmware Version: v133.2.0.2

Code: Select all

sudo ./JMS578FwUpdate -d /dev/sda -f ./JMS578-Hardkenel-Release-v173.01.00.02-20190306.bin -b ./backup.bin
Update Firmware file name: ./JMS578-Hardkenel-Release-v173.01.00.02-20190306.bin
Backup Firmware file name: ./backup.bin
Backup the ROM code sucessfully.
Programming & Compare Success!!
Give everything a cold reboot (if you have power to your USB->SATA device

Code: Select all

sudo ./JMS578FwUpdate -d /dev/sda -v
Bridge Firmware Version: v173.1.0.2

Voila!

It now boots from USB3 ports!


Previous speed test on USB2

Code: Select all

sudo hdparm -tT /dev/sda                    

/dev/sda:
 Timing cached reads:   1754 MB in  2.00 seconds = 877.30 MB/sec
 Timing buffered disk reads: 102 MB in  3.05 seconds =  33.39 MB/sec
New speed test on USB3

Code: Select all

 hdparm -tT /dev/sda

/dev/sda:
 Timing cached reads:   1826 MB in  2.00 seconds = 913.42 MB/sec
 Timing buffered disk reads: 1122 MB in  3.00 seconds = 373.49 MB/sec
I have this USB to SATA:

https://www.amazon.co.uk/Sabrent-2-5-In ... b3+to+sata

Will that still work?
One man's trash is another man's treasure! :) Pi's I have; Pi Zero, Pi Zero W, Pi 2 x2, Pi 3 x2, Pi 4 4GB x2.

romprod
Posts: 20
Joined: Sat Jun 09, 2012 6:31 pm

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Sat Jul 06, 2019 6:23 pm

Run lsb as below and see if you get the following results. If you do, then go for it. Although I ain't promising that it doesn't brick it!

Code: Select all

[email protected]:/data/docker $ lsusb

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

thatchunkylad198966
Posts: 126
Joined: Thu Jul 04, 2019 10:21 am
Location: UK, Birmingham

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Sat Jul 06, 2019 6:39 pm

romprod wrote:
Sat Jul 06, 2019 6:23 pm
Run lsb as below and see if you get the following results. If you do, then go for it. Although I ain't promising that it doesn't brick it!

Code: Select all

[email protected]:/data/docker $ lsusb

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I don't get the exact same?

Code: Select all

[email protected]:~ $ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 1058:107c Western Digital Technologies, Inc. Elements Desktop (WDBWLG)
Bus 002 Device 003: ID 152d:1561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS561U two ports SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04b4:f02f Cypress Semiconductor Corp. 
Bus 001 Device 003: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~ $ 
One man's trash is another man's treasure! :) Pi's I have; Pi Zero, Pi Zero W, Pi 2 x2, Pi 3 x2, Pi 4 4GB x2.

romprod
Posts: 20
Joined: Sat Jun 09, 2012 6:31 pm

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Sat Jul 06, 2019 7:07 pm

Sorry, not sure.

Maybe try looking for a new firmware for that device or try the one that I've used. It backups up the current firmware so I'm going to assume that you get the ability to reflash it if the new one doesn't work.

thatchunkylad198966
Posts: 126
Joined: Thu Jul 04, 2019 10:21 am
Location: UK, Birmingham

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Sat Jul 06, 2019 7:14 pm

romprod wrote:
Sat Jul 06, 2019 7:07 pm
Sorry, not sure.

Maybe try looking for a new firmware for that device or try the one that I've used. It backups up the current firmware so I'm going to assume that you get the ability to reflash it if the new one doesn't work.
I'll have a look around, at least I know it's not my fault that it wasn't working.
Stayed awake until 7am too; sigh.

Thanks dude! :D :mrgreen:
One man's trash is another man's treasure! :) Pi's I have; Pi Zero, Pi Zero W, Pi 2 x2, Pi 3 x2, Pi 4 4GB x2.

romprod
Posts: 20
Joined: Sat Jun 09, 2012 6:31 pm

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Mon Jul 08, 2019 11:04 am

I've reverted back to having / on the SSD card.

For some reason the storage was being set to read only and other strange behaviour.

It'll have to do for for now, but there's still something wrong with the SSD USB drivers and this USB3 port.

sbtagain
Posts: 3
Joined: Mon Dec 24, 2012 4:06 pm

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Tue Aug 13, 2019 7:23 pm

I am able to successfully mount the file system to a SSD ONLY if I attach the SSD device to a USB2 port directly on the pi board. The USB3 port simply does not work at all. Yea - I'm loosing performance but I want the extra storage...

romprod
Posts: 20
Joined: Sat Jun 09, 2012 6:31 pm

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Tue Aug 13, 2019 7:36 pm

Have you updated the firmware on your SATA to USB cable?

User avatar
SyncBerry
Posts: 53
Joined: Sat Sep 21, 2019 11:13 am
Location: France (S-W)

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Thu Sep 26, 2019 10:12 am

romprod wrote:
Tue Aug 13, 2019 7:36 pm
Have you updated the firmware on your SATA to USB cable?
Hi Romprod, I did :D, successfully, and now Pi4 boots with rootfs in a SSD on USB3. I was afraid as lsusb reports a JMS567 chip and the FW was for JMS578. Although a closer look to the command output shows ...ID 152d:0578 JMicron.... Whatever I just tried, first only to have a look to the current FW (as I saw your captures, Romprod, show the same mismatch). IIRC the FW was something low as 0.00.05. Then I flashed. On first boot I was afraid I bricked the bridge because I seemed longer than before to boot, but after a coffee I went back and could log in. Nice.

Romprod, do you have these new lines in dmesg? :

Code: Select all

[    7.216011] 8021q: 802.1Q VLAN Support v1.8
[   37.611596] sd 0:0:0:0: [sda] tag#28 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD IN 
[   37.611614] sd 0:0:0:0: [sda] tag#28 CDB: opcode=0x28 28 00 14 c0 09 80 00 00 08 00
[   37.611758] sd 0:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD IN 
[   37.611771] sd 0:0:0:0: [sda] tag#27 CDB: opcode=0x28 28 00 14 c0 09 78 00 00 08 00
[   37.612005] sd 0:0:0:0: [sda] tag#26 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD IN 
[   37.612017] sd 0:0:0:0: [sda] tag#26 CDB: opcode=0x28 28 00 14 c0 09 70 00 00 08 00
...
[   37.619069] sd 0:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 22 inflight: CMD IN 
[   37.619081] sd 0:0:0:0: [sda] tag#3 CDB: opcode=0x28 28 00 14 c0 09 a0 00 00 08 00
[   37.619368] sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD IN 
[   37.619379] sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x28 28 00 14 c0 09 98 00 00 08 00
[   37.619670] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD IN 
[   37.619682] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 14 c0 09 90 00 00 08 00
[   37.619970] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD IN 
[   37.619982] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 14 c0 09 88 00 00 08 00
[   37.701643] scsi host0: uas_eh_device_reset_handler start
[   37.852207] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[   37.886050] scsi host0: uas_eh_device_reset_handler success
[   38.260119] Adding 102396k swap on /var/swap.  Priority:-2 extents:4 across:151548k FS
[   38.359993] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   38.360002] brcmfmac: power management disabled
[   68.971583] sd 0:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD IN 
[   68.971600] sd 0:0:0:0: [sda] tag#27 CDB: opcode=0x28 28 00 0c 80 09 d0 00 00 08 00
...
[   68.972505] sd 0:0:0:0: [sda] tag#22 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN 
[   68.972517] sd 0:0:0:0: [sda] tag#22 CDB: opcode=0x28 28 00 08 44 40 00 00 00 98 00
[   68.972960] sd 0:0:0:0: [sda] tag#19 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
[   68.972972] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x28 28 00 0c 80 09 08 00 00 08 00
[   68.973213] sd 0:0:0:0: [sda] tag#5 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN 
[   68.973225] sd 0:0:0:0: [sda] tag#5 CDB: opcode=0x28 28 00 0c 47 0d 98 00 01 00 00
[   68.973649] sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD IN 
[   68.973661] sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x28 28 00 0c 80 09 f8 00 00 08 00
[   68.973892] sd 0:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD IN 
[   68.973904] sd 0:0:0:0: [sda] tag#3 CDB: opcode=0x28 28 00 0c 80 09 f0 00 00 08 00
[   68.974012] sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD IN 
[   68.974024] sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x28 28 00 0c 80 09 e8 00 00 08 00
[   73.691578] sd 0:0:0:0: [sda] tag#28 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT 
[   73.691593] sd 0:0:0:0: [sda] tag#28 CDB: opcode=0x2a 2a 00 10 04 08 f8 00 00 90 00
[   93.291578] sd 0:0:0:0: [sda] tag#20 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN 
[   93.291592] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x28 28 00 17 c4 20 00 00 00 08 00
[   99.051580] sd 0:0:0:0: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT 
[   99.051595] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 00 01 2f 08 00 00 08 00
[   99.051820] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD OUT 
[   99.051833] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 08 8e c3 88 00 00 08 00
[   99.091600] scsi host0: uas_eh_device_reset_handler start
[   99.242464] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[   99.277612] scsi host0: uas_eh_device_reset_handler success
[   99.972032] bcmgenet fd580000.genet: configuring instance for external RGMII (no delay)
[   99.972378] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  101.031651] bcmgenet fd580000.genet eth0: Link is Down
[  103.112148] bcmgenet fd580000.genet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[  103.112170] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[
Did you get rid of them? Do you know if we can query the config flags of the bridge for parameters "hot-plug support" and "spin-down timer" explained on o-droid if these ones make sense and would conflict for a rootfs + SSD ? Or we could see these from syslog or lsusb or something else ?
A quick search on the web give a huge amount of pages about a USB3 UAS problem with linux we could disable, but my english is so bad I don't understand: I don't know if our driver is loaded buitin or from a later module loading.

ciB89
Posts: 1
Joined: Fri Oct 04, 2019 1:42 pm

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Fri Oct 04, 2019 1:44 pm

I am really confused.. I flashed the latest rasbian lite on my SSD and my SD card, plugged them in and ran blkid - but for some weird reasons they have the exact same partuuid? How is that possible? What can I do to change this?

User avatar
SyncBerry
Posts: 53
Joined: Sat Sep 21, 2019 11:13 am
Location: France (S-W)

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Fri Oct 04, 2019 5:34 pm

Did you image both from the ISO, or first one from the ISO then the other from the first ?

RonR
Posts: 644
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: [PI4:] how do I move the filesystem to a USB stick/Drive

Fri Oct 04, 2019 6:28 pm

ciB89 wrote:
Fri Oct 04, 2019 1:44 pm
I am really confused.. I flashed the latest rasbian lite on my SSD and my SD card, plugged them in and ran blkid - but for some weird reasons they have the exact same partuuid? How is that possible? What can I do to change this?

This is a known problem with the latest Raspbian Buster release: 2019-09-26 Raspbian Image PTUUID

usb-boot will detect this problem and allow you to correct it: Running Raspbian from USB Devices : Made Easy

Return to “Advanced users”