I couldnt find the file pidesktop.deb. The webpage is really complicated.
I couldnt find the file pidesktop.deb. The webpage is really complicated.
Hi gdenicolas ,
You don't need the debian file to boot from the SSD. In the user manual is a step by step guide and explanation on how to set this up:
Pi Desktop User Manual_EN_Rev3.2-FINAL.pdf
I've asked internally about the debian file, and I've read through the manual where there's some typing errors that need to be fixed (eg. capitalization of linux commands).
Feel free to ask me any questions on this as I've been working with this add-on board (and have one sat on my desk).
My concern not loading the pidesktop.deb is that you lose out on :
ppp-hdclone (What it does probably can be done just by dd'ing the image to the mSata)
ppp-boot (This actually changes the /boot/cmdline.txt to change the root, which isn't mentioned. I had previously set the usb variable, but AFTER I put it all together so can't get the card out to test if it isn't needed)
embest.service/embest-shutdown.service/rtc.py/sync-hwclock - Seem like they make sure the HWClock is up to date, not mentioned in the manual.
Tuc
The SDCard isn't needed when booting from USB after the bit is set. The Pi prioritises booting from SDCard if it is inserted as well as the USB device.
If you have only a USB bootable device inserted, and the SDCard removed, you don't have to change the location in /boot/cmdline.txt. It's probably best to set the bit before putting the Pi inside the enclosure.
You're right that it doesn't say which device it prioritises, though it does say on page 15 that the SD Card is no longer needed. Do you feel it should be explicitly stated to remove the SD Card ?
Hi,
Yes, do think it would be useful. I think even more useful is telling you to install the "Type A to micro USB" *BEFORE* you put the lid on. I found I needed to pry the lid off (Whoever designed it meant for it NEVER to come off.
) and press/lift the hat ever so slightly to get it to align JUST right. The 2nd time I put it together when I was testing things I ended up doing it outside the case so I could take out/put in the SD card... So it really is out of the case. Adds a nice blue glow to my work room
Tuc
Hi,
So I shutdown the Pi, pulled the SD card, turned it on, waited 15 seconds... Nothing. Put the card, started up, checked that my /boot and / were running off the mSata (I changed the /boot/cmdline.txt on the SD), and ran "vcgencmd otp_dump | grep 17:" and got the right response of 0x3020000a. Shut down, pulled the card, tried again, nothing.
The mSata was loaded by booting off SD, dd of the Raspbian Jessie to it, then I did by hand the expand of partition 2 (Delete, extend, resize2fs).
Tuc
Hi,
So I shutdown the Pi, pulled the SD card, turned it on, waited 15 seconds... Nothing. Put the card, started up, checked that my /boot and / were running off the mSata (I changed the /boot/cmdline.txt on the SD), and ran "vcgencmd otp_dump | grep 17:" and got the right response of 0x3020000a. Shut down, pulled the card, tried again, nothing.
The mSata was loaded by booting off SD, dd of the Raspbian Jessie to it, then I did by hand the expand of partition 2 (Delete, extend, resize2fs).
Tuc
If you've dd'd the default Raspbian Jessie image from raspberrypi.org to the SSD you don't need to change the contents of cmdline.txt on the SSD.
Hi,
I didn't. It was on the SD I made the changes. But still the issue that despite having the 0x3020000a set, it isn't booting from SSD.
Tuc
Tuc . wrote:
Hi,
I didn't. It was on the SD I made the changes. But still the issue that despite having the 0x3020000a set, it isn't booting from SSD.
Tuc
When I initially imaged the SSD it didn't boot either, and that was because of the software I used to write the image to the SSD didn't do it properly.
What software/commands have you used to write the image to the SSD and under which operating system?
Hi,
Raspbian Pixel, fresh install to the SD.
unzip -p|dd bs=1m of=/dev/sda
I think thats it. Might be uppercase M, I get confused, some platforms take it, others don't. I didn't have space on the 8G card in it, so I had to stream the contents of the download and pipe into dd.
Tuc
I would suggest trying either the hard drive clone script that's included with the debian package to replicate your SDCard raspbian install, or try imaging the SSD by connecting it to another computer (this is outlined in the manual).
Have you tried wiping the SSD and partitioning it via other ways (not imaging it) to see if it's compatible and working in with the Pi HAT add-on? There could be something funny going on there, too.
Hi,
Unfortunately, I can't. I don't own anything else that can take the mSata card (https://smile.amazon.com/gp/product/B00TGIVRYU ). The Pi-Desktop is the only thing.
Tuc
Well, you don't need to connect the mSATA card into something else directly, you can plug it in via USB to another computer. This is covered in the user manual, as the SSD connects to the Pi in the Pi Desktop via USB, so to can it connect to another computer.
When I bought the Kinston SSH I expressed chose a SATA storage as I was having in home a number of recovered SATA-to-USB external powered boards from old HDD external boxes. These was heavy small boards to power externally 5 inches HDD with 5V 2A power supplies. This was to have a larger storage on the Raspberry PI old versions and the multi boot bit never had been mentioned.
I also published an article on how to boot from SD card but using the external USB SATA connected HDD with the entire file system on it. The blog post (from 2015) is here: Meditech: RPI master storage system with some image of the first experimental tests while the disk setup procedure is here: Raspberry PI: USB hard disk boot
As I saw none of the mechanical HDD was powered correctly by the PI including the 2.5 HDD declared as self-powered by the USB connector. Also today I use a couple of 3TB Western Digital USB HDD that work properly only if directly connected to the computer USB; if I use a HUB for these disks I should use a powered USB HUB else stability problems in data transfer still occurs.
Seeing that the concept was working I bought a very low power consumption SSD Sata from my local retailer and a Startech SATA to USB connector supoprting both USB3 (full speed) and USB 2 on Amazon (https://www.amazon.es/gp/product/B00HJZJI84/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 )
Applying the settings mentioned above things worked fine. The PI was anyway booting from the SD card no longer stressed during the normal usage.
Now with the introduction of the multi boot option settings in the PI3 things are working better and it was finally possible to remove the micro SD card.
Just a note: as in terms of reliability an SSD is more durable than the SSD card thinking to make a device that should work for long time boxed (maybe to a client site) it is the worth to use this setup instead of the traditional one despite the advantage of a larger storage space for the file system with a cost of 50-60$
Enrico
Hi,
We might be misunderstanding each other. My card was a true mSATA, came with just the drive. No connectors/enclosures/etc. I connected to the hat, booted off SD, dd'd to the mSATA.
So, I went on Amazon to get a connector. USB to SATA, then a card that converted SATA to mSATA. When I got it, I shut down the machine ready to take out the mSATA and put it into the adapter and run USB. I figured JUST for giggles I'd make sure one more time it didn't work. I already had the machine down, so I just pulled the SD card. Turned it on. Eventually got the 4 raspberrys, colorful screen, seemed to do that again, and finally booted Pixel. I shut down, restarted, and it seemed to be fine. Tried a few more times, worked. <SHRUG> Maybe I was too impatient the first time. But, the news is, I'm fine.
Tuc
For the record I too connected a mSATA SSD to the hat, found it was sda,
downloaded Raspbian to the Raspberry Pi, dd it to /dev/sda then
followed the Raspberry Pi: USB: Hard Disk Boot instructions. Worked like
a charm. df -h now shows /dev/root 230G 16G 202G 8% /