The Limit is about 2TB. The boot partition should be on a drive with MBR partition table (GPT makes trouble) and must have a FAT32 filesystem (exFAT doesn't work).
So to confirm, I can make the boot partition of a Raspbian SD card 2 *tera*bytes? If so, yes, that would suffice.
Code: Select all
/boot FAT32 /volumio EXT4 /volumio_data EXT4
I have thought about heat dissipation, but this is being done with a Pi Zero W. Has anyone had heat issues with a Pi Zero?Imperf3kt wrote: ↑Mon Mar 11, 2019 8:36 pmYour further explanation raises a few questions, are you using the Pi Zero or the Pi3b+?
Where, exactly, are you storing the music? You keep asking for a small usb stick, to transfer files onto an expensive 512GB microSD card, but in my opinion that's pointless as you just unplug the usb stick when you're done so size is irrelevant. In fact, pricewise, you're probably best off buying a small portable HDD or SSD for copying the music between PC and Pi.
Have you considered heat dissipation?
A Pi3b+ in such a cramped space will likely get quite hot.
I know my Pi3b did when encased at 33mm depth. It reached over 70°C just sitting idle at the desktop, and it had ventilation on all four sides.
I'm curious what volumio is using the /volumio and /volumio_data directories *for*, if the /boot directory is the root and boot partition? And I wonder what data it is storing in data?LTolledo wrote: ↑Mon Mar 11, 2019 8:43 pmI've just pop my RPiZWH portable volumio player's 8GB microSD card to this RPi3B to check the partition structure
it would seem that the volumio partition is the equivalent of the "root" partition
Code: Select all
/boot FAT32 /volumio EXT4 /volumio_data EXT4
the volumio_data EXT4 may be shrunk and another NTFS or FAT32 partition can be added (where you can store your music files)
I had a 64gb card set up with Raspbian already. I had copied some music onto it previously. Using gparted, I discovered that the music ended up in the ext4 partition, which Windows cannot see.
Yes, those are all great finds and suggestions, thank you.Imperf3kt wrote: ↑Mon Mar 11, 2019 10:57 pmOK now I see.
You could buy one of these. Up to 128GB
https://www.sandisk.com/home/mobile-dev ... ve-usb-m-3
I have a different brand that's a bit smaller but mine is only 32GB
Or you could buy something like this.
I do believe Volumio creates a network share, so all of this may be moot, but...
Theoretically, yes, but in reality, no. However, that's only because there are no real 2TB micro SD cards available (yet). 1TB cards are supposed to ship next month (April) from SanDisk, Micron and one other company (Lexar, I think). They're going to be expensive, though (and as I said above, you don't really need a giant /boot partition).
Thought you might like that.
Mucking about with partitions seems unnecessarily complicated to me, since there are easy options available.I’m wondering if just making the boot partition take up most of the card is possible and workable, allowing easy file transfer in Windows (you know, for us lazy Windows non-typers )? This is something else I will experiment with. I have a 64gb card I can use to test for now. Since this project is a dedicated music player, and doesn’t need to do anything else, can you think of a downside to this approach?
There are 512GB cards now. The Samsung EVO Select is the cheapest I've seen, but I haven't really monitored prices all that much. I do know that the 512GB cards are much more expensive than the SanDisk Ultra A1 400GB.I will likely order a 400gb card for this project. I can’t imagine running out of storage for music with that much space. If so, bigger cards will become available.
Depends in the screen. Most screens designed for Pi computers use GPIO for touch input. Most standard touch screen monitors use USB.I still need to figure out how the 4.3 inch display sends touch screen data to the pi. I’m assuming it’s on the USB connection, but the Pi Zero USB data port supposedly is only for data, and the other port is for power. If the display powers up via USB, and the data comes from the display via USB, will I need to split the output from the display so data goes to one USB ports, and the power goes to my power source?
I make backup images of all of my operating system SD cards once they are running well. I can just re-flash the card if things go south.
That's the ticket. The 400GB should be plenty large enough capacity, and I've seen them selling for about $72. The 512s are all well over $100.There are 512GB cards now. The Samsung EVO Select is the cheapest I've seen, but I haven't really monitored prices all that much. I do know that the 512GB cards are much more expensive than the SanDisk Ultra A1 400GB.
The monitor I just ordered uses USB data. Problem should be solved.Depends in the screen. Most screens designed for Pi computers use GPIO for touch input. Most standard touch screen monitors use USB.
Gordon from IQaudio indicated that the data USB on the Pi Zero does in fact carry power. This should solve the power issue. Although, I would prefer to split the power output from the UPS board to feed the Pi Zero and the monitor separately, so the Pi Zero isn't dealing with any power issues. This will need to be tested.The power traces are directly connected between the Pi0 Data and Power micro USB ports. When using Pi0 USB Gadget Mode the Data port is used to both power the Pi0 and to transfer data (the power port is not used with USB Gadget Mode). And hey, there's another option! If for some reason you have trouble with Volumio's network share, USB Gadget Mode could be another way to connect your Pi0 to transfer files.
AirFiero wrote: ↑Thu Apr 04, 2019 7:25 pmProject update:
I received the Waveshare 4.3 inch display, and a Lexar 512gb Micro SD card. I'm doing tests on smaller cards with Raspbian and Volumio. Raspbian seems to work nicely on the RPi Zero with Waveshare display. The touchscreen is a little bit off (your finger and where the cursor is ends up about 1/8in apart), but the display came right up. Music plays.
As for Volumio, the GUI isn't showing very well on this monitor, but I haven't done the configuration yet, I just did a "fire it up" test. No problem. At least I know the hardware is compatible.
The Lexar 512 card was from B&H Photo, price was $99. Price is same today on their website. Storage hardware solved, now to experiment with file location and partitions.
https://www.bhphotovideo.com/c/product/ ... _633x.html
In another thread, I learned more details about the /boot partition and potential issues with using it. I'll try the methods listed in this thread for music storage and copying files.
Oh, and the answer to the touch screen data connection...it uses a USB port that connects to the RPi Zero USB data port. Video (and sound, if needed) runs to the display (which has it's own headphone jack).
Here is a picture of the mockup/test of the PiPod...
No it does not. You will still get two partitions.
jahboater wrote: ↑Fri Apr 05, 2019 7:48 amNo it does not. You will still get two partitions.
The filesystem Raspbian uses for its main partition has no practical size limit.
I've been doing tests on smaller cards (16 or 64gb) with some sample music to see what works before I use the 512gb card.
PiCore looks promising. I'll dive into it next tine I fire up the Pi. Thanks.Gavinmc42 wrote: ↑Thu Apr 11, 2019 12:41 amPiCoreplayer uses PiCore the Pi version of TinyCore Linux.
I have also use PiCore for years, the default partition sizes need modifiying to add an other stuff.
For that I use a Linux box and Gparted after the image has been burned.
I increase the boot partition a little and the TinyCore 2nd partition gets increased so I can add apps.
The rest of the SD card is formatted as a third partition for data.
If PiCore is only going on a particular Pi then the alternative kernels can be deleted and the 1st partition shrunk.
Use Linux and Gparted or the command line methods "dd" etc.
I tried Disk manager in Windows 10, blue screen a few times