I'll share the PARTUUID and UUID configuration which works for me just in case somebody else comes across this issue (perhaps after reading all the conflicting advice available on the internet). NOTE: I do not use a USB stick, but the following is the way I mount the main MicroSD card on my B+ running Raspbian Jessie (3.18.1+):miamia wrote:I found on internet this: root=/dev/disk/by-uuid/xxxxxxx. Maybe it helps.miamia wrote:thanks, but what prefix for blkid shoudl I use in /boot/cmdline.txt? "root=PARTUUID="?
EDITED: my RPi cannot boot with root=/dev/disk/by-uuid/xxxxxxx. With root=dev/sda1 everything works ok.
The RPi has been developed for learning something, not to supply one click solutions for everything. And you can learn a lot, if you work through this great HOWTO.jamesdinsmore wrote:OMG! Way too many steps! Maybe something could be adapted from Berryboot, which as a matter of course allows you to select whether to install to an SD card or to USB memory, etc (effortlessly!) http://www.berryterminal.com/doku.php/berryboot
The RPi can only have the boot partition on the SD Cardmmfc wrote:I'm trying to set up the boot partition to be on my hdd that is normally connected to my pi
DougieLawson wrote:The boot partition MUST be the first primary FAT or FAT32 partition on the SDCard or the Raspberry Pi can't boot.
The root filesystem for any Linux based operating system must use a Linux native filesystem (ext2, ext3, ext4, reiserfs, etc), you can't use Windows native filesystems (FAT, FAT32, exFAT or NTFS).
An USB stick is no great alternative to running it from SD, but a HDD really is: much faster, no SD card corruption any more and lots of space for data.Joe Schmoe wrote:...
Now, having said all that, let me comment that, from a purely functional point of view (i.e., not counting the aesthetics of the situation), there really isn't all that much point in "moving the filesystem to a USB stick" (the title and nominal subject matter of this thread). To my mind, because of the fact that you always have to have the SD card for booting, means that you might as well just leave the system there as well.
Aesthetically, I can see reasons for doing it, but if you're the "I just want it to work" type, then it is probably not necessary.
Code: Select all
[ 3475.526102] EXT4-fs error (device sda1): htree_dirblock_to_tree:896: inode #2: block 9249: comm ls: bad entry in directory: inode out of bounds - offset=0(0), inode=2922024487, rec_len=1096, name_len=213
rsync errors meant corrupted files, I suppose. The error message when mounting is the result.jhaprade wrote:Hello,
I followed the instructions and was able to mount the USB stick on /dev/sda1 on /mnt.
But when I did the "rsync" step, I got some errors. And after that, when I do "cd /mnt; ls", I get the following message:
None of the following commands are working. Any suggestions?Code: Select all
[ 3475.526102] EXT4-fs error (device sda1): htree_dirblock_to_tree:896: inode #2: block 9249: comm ls: bad entry in directory: inode out of bounds - offset=0(0), inode=2922024487, rec_len=1096, name_len=213
Try again and if you are getting errors again have a look at the error messages. They will give you (and us) a hint what went wrong.jhaprade wrote:I am sorry but I didn't understand. How do I deal with this rsync error?
Overclocking / Overvolting is a bit different between Pi1 and 2. Remove all overclocking settings in config.txt.359 wrote:Hi. Thanks to this thread, I have been running an old PiB for many months from a usb stick. Thank you all
My PiB sd card is actually a micro sd running in an Adafruit adapter.
Now I have a Pi2. I wish to move the PiB micro sd and usb to the Pi2 as is, hoping to avoid lot of configuration. On the PiB, have run sudo update, upgrade and so on, I have read this is needed to move a SD card to the Pi2. Then plugged the micro sd into the Pi2, usb into a slot but it doesn't boot, no nothing if hdmi is plugged in, just a red light. The psu is a 1.5A 5v supply so pretty sure it is not that.
Any thoughts on how to accomplish this?