Vu Duo2 and external usb ssd drive

Have been using a Seagate 2TB BUP (backup plus portable) external usb 3.0 drive to store my openmultiboot images so that I can boot from SDG in flash (latest) to whatever image for testing. Working great so far.

Bought a Vansuny Portable 60gb ssd usb 3.0 drive to experiment with openmultiboot and Duo2 with SDG.

Attachment 5497

Checked the usb drive in Win10 and it works great as an ntfs drive. While in Win10 I used AOMEI Partition Assistant Pro to format the usb drive as ext4. Plugged it into the front port and booted the Duo2 and the drive is not recognized.

Telnet and:

satdreamgr 8 vuduo2

vuduo2 login: root
root@vuduo2:~# mount -t ext4
/dev/sda1 on /media/hdd type ext4 (rw,noatime,data=ordered)
/dev/sda1 on /media/sda1 type ext4 (rw,noatime,data=ordered)
root@vuduo2:~# df -mh
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 862.3M 159.0M 703.3M 18% /
devtmpfs 687.8M 4.0K 687.8M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
/dev/sda1 930.5G 400.5G 528.9G 43% /media/hdd
tmpfs 687.9M 64.0K 687.8M 0% /run
tmpfs 687.9M 80.0K 687.8M 0% /var/volatile
/dev/sda1 930.5G 400.5G 528.9G 43% /media/sda1
root@vuduo2:~#

The only drive recognized is my old Seagate Barracuda internal sata drive.

On my pc I booted to a live ubuntu usb and checked the Vansuny usb ext4 file system and it passed as ok. Just to further check, I transferred a few files between the usb stick and my pc hard drives. Everything worked ok.

Just to be sure, reformatted to ext4 via the disk tool. Checked file system and displayed as ok.

Plugged usb Vansunny back in to Duo2 and booted. Still not recognized.

Plugged usb Vansunny back in to Win10 pc and used AOMEI Partition Assistant Pro to reformat to NTFS. Checked file transfers to/from usb drive and everything OK.

Telnet to Duo2 and:

satdreamgr 8 vuduo2

vuduo2 login: root
Last login: Mon Jul 6 12:29:49 MST 2020 on pts/0
root@vuduo2:~# opkg install kernel-module-ntfs
Installing kernel-module-ntfs (3.13.5) on root
Configuring kernel-module-ntfs.
root@vuduo2:~#

Plugged in Vansuny usb drive and booted Duo2.

Telnet Duo2 and:

satdreamgr 8 vuduo2

vuduo2 login: root
Last login: Mon Jul 6 13:58:31 MST 2020 on pts/0
root@vuduo2:~# mount -t ntfs
root@vuduo2:~#

The ssd drive works great in Ubuntu as ext4 or NTFS and it works great in Win10 as NTFS.

So, does the Duo2 support external usb ssd drives?

Anyone know of a module that I can telnet in SDG that might support this usb ssd?

Code:

---

lsusb

---

command shows something?

and also... it may be a power (supply) problem.the receivers usb gives about 300ma. how many the disk needs?
in that case, a cable like this could do the job

https://i.postimg.cc/65B0jmX8/Screenshot-2.png

Sorry for the delayed response. Don't believe it's a cable or power problem because after I did the mount -t ntfs module and formatted the drive in Win10 as ntfs, and then plugged it into the duo2 front usb port it was recognized as a read only drive.

The supplied cable for the ssd drive is a Micro-B to USB 3.0-A backwards compatible to usb 2.0. But, as I mentioned earlier, it is recognized by the duo2 as a ntfs read only drive but not as a ext4 drive. Also, it works great as a ext4 drive in Ubuntu using the disk tool to copy or read files.

I lent the drive to someone and when I get it back I will try again to format it as ext4 and hopefully solve the problem.

A little late in reply, but I received the Vansys usb ssd back and have been using it successfully as my OpenMultiboot drive for a couple of months now.

Prior to, I was using the Seagate BUP usb drive until I got the Vansys ssd back. A few months ago I did a SDG on line update. In the interim, the Vansys SSD usb was collecting dust so for one last try, I thought I would plug it in to the same usb port as before and it was recognized.

Attached are the speed differences between the two drives. The Vansys boots up noticeably faster than the Seagate and runs cooler. Also, a big difference in start up speed when selecting plugins> openmultiboot while using the Vansys ssd since there is no disk spin up.

Attachment 5654

Attachment 5655