Flash drive won't mount? #20
Comments
|
The first suspicion that comes to mind is general incompatibility of some USB drives. Are you able to manually mount the drive using instructors mentioned here? Another thing to consider is whether the power supply is able to provide enough voltage for the USB drive and the pi. This post provides a few ways to diagnose if your pi is operating under low voltage. |
I am using a 2.5 amp power supply, so I don't think that power delivery is an issue here. I am able to manually mount the drive and share it's contents through SMB. Pretty sure that the problem is that the drive isn't being automatically mounted on boot for whatever reason. Therefore, it falls back to the share directory on the microSD card. I don't want to have to configure this manually through SSH every time I turn on the Pi. I tried this method for mounting the flash drive permanently, but it broke the installation and I had to re-write the image to the card to get it working again. |
|
Since the issue is specific to the drive you are using, it's a bit difficult to diagnose on the other side. The mechanism for auto-mounting USB drives is contained here, it may be possible to modify this to work with your device. Does the drive auto-mount if you hot-plug it after booting? Have you tried using a different USB drive to see if the issue still exists? |
|
I tried a 32 GB Kingston USB 2.0 flash drive, and if I remember correctly, the Pi was actually able to mount it to a directory, but the SMB share was still set to the directory on the microSD card instead. Hot-plugging didn't seem to work with the 64 GB flash drive when I first tried doing that, but I'll try doing it again when I get home, but this time, I'll try to look closer at what's going on in the SSH terminal. I'll also try hot-plugging with the 32 GB drive. It should also be noted that a year or two ago, I tried using my same Pi with the same 64 GB drive (formatted to NTFS) to play games through Ethernet on my slim PS2 with OPL by installing and configuring OpenMediaVault on my Pi according to this tutorial, and it actually worked. I was able to view, boot, and play games off the flash drive on my Pi wired to my PS2 through Ethernet. So this might be an issue with how psx-pi-smdshare handles certain flash drives compared to OpenMediaVault. |
|
I've verified with a generic USB stick and latest image release that the auto-mounting / sharing feature is working as intended on my end, but am curious as to why this would not work with either of your Kingston flash drives. First a brief overview of how automount-usb.sh works: The Now we can look at ways to diagnose these mechanism with your USB drives: When you plug in your USB drive, it should be mounted to a path at If the mounting of the drive is successful, but you still do not see the drive over SMB, then we need to look at the recreated samba share point. The recreated share point will still be served over SMB at a path named If you have verified both of these mechanisms to be successful, you should be able to see the contents of your USB drive are now served at the SMB path |
|
While testing, I did notice that USB drives do not automatically get shared on boot. This is because a crontab entry is created which essentially falls back to sharing the SD on boot. Ideally, if a USB drive is plugged in on boot, we should share the USB drive and not the SD. This has been addressed in d49fda3. I have published an updated release containing this fix. |
|
I updated my psx-pi-smbshare installation. My 32 GB Kingston USB 2.0 flash drive now gets automatically mounted and shared every time it gets plugged in. My 64 GB PNY USB 3.0 flash drive, however, doesn't. I have to mount the 64 GB drive to (for example) I'm not sure why my 64 GB drive isn't being mounted automatically, and I'm not sure how I can troubleshoot this. Should I just straight up run the command Below are the outputs of different disk info-related commands for both my flash drives. Hopefully, these will be useful for debugging. Thanks. Kingston 32 GB (works fine)
PNY 64 GB (does NOT automatically mount)
|
|
I'm glad to hear the 32GB disk is working! Thanks a ton for providing detailed debug info, at first glance I noticed that when looking at the output of The 32GB disk is recognized as gpt with a vfat filesystem and a single partition at (/dev/sdf1) The 64GB disk is recognized as dos (MBR) with a BBT filesystem and four partitions at (/dev/sdg1, /dev/sdg2, /dev/sdg3, and /dev/sdg4 ) with enormous sizes (2T!?) This makes me wonder if this drive would report the same result with a stock Raspbian image. Does the 64 GB disk also fail to mount when formatted with a gpt partition table? For more information on the difference between GPT and MBR see: https://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-when-partitioning-a-drive This could also be an issue with pmount. What happens when you run the following (Assuming the 64GB drive is mapped to /dev/sdg*)? After running this command, navigate to /media/sdg1 to check if the drive mounted appropriately. If this command fails, it should provide output that will give a clue as to the root cause of failure. |
|
Shortly after I posted my disk command outputs, I decided to reformat my 64 GB drive from MBR exFAT to GPT exFAT (my 32 GB drive was already GPT, so I left that drive alone) to see if it that would make it work. And lo and behold, my 64 GB drive was finally automatically mounted and shared by the Pi! Thank you very much for the help. I might try fooling around with an MBR-formatted flash drive and seeing what happens if I try to mount it with that |
|
Huge congrats! Thanks for working with me together on this, no doubt others will find this info useful and major props on uncovering the issue of automount not working on boot. Glad everything is working, going to close the issue. Feel free to reopen the issue if tests prove anything of interest. |
|
Very curious what was the root cause for this particular issue. I happen to use a 8gb usb 2.0 corsair flash drive and my raspberry pi never had an issue detecting it for my ps2 games during testing. It is FAT32 and MBR partition style. Very glad this issue got fixed, as I recommended to op to make a github ticket. :) |
|
Thanks for suggesting the idea to OP to create the issue @VersatileNinja. This project aims to be user-friendly + issue-free and you’ve been a great contributor to the cause. If I had to guess, the root cause is either some odd combination of MBR with an unsupported filesystem OR a temporarily corrupted drive given the weird output from ‘lsusb-l’. |
I'm trying to get this software to work properly with my Pi 3 Model B+ and a PNY 64 GB USB 3.0 flash drive so I can play games off the flash drive using OPL (ver. 1815) on my slim PS2. However, for whatever reason, the flash drive doesn't appear to get mounted. I found this out after browsing the share folder through SMB and then browsing the same folder directly on the Pi's microSD card plugged into my laptop. In both those cases, the DVD and CD folders were empty while the ART folder contained files for Tobal 2 and X - Unmei No Sentaku. On my flash drive, the DVD and CD folders contain 20 ISOs and 1 ISO respectively, while the ART folder contains the art for all those games. My Pi detects the flash drive as a USB device, as
lsusbreturnsBus 001 Device 006: ID 154b:00d2 PNY, but for some reason, the microSD card's share folder is shared instead. Why is this happening? I've tried all 3 formats compatible with Windows so far for my flash drive: FAT32, NTFS, and exFAT. Thanks.The text was updated successfully, but these errors were encountered: