JPICentral
Posts: 33
Joined: Wed Jul 18, 2018 3:22 am
Location: Almost in the Mojave Desert

SSD Boot Process

Sat Aug 18, 2018 1:42 am

Having read much about SSD Boot (pro/con/undecided/incomplete/outdated/incorrect per another/etc.) I think I would like to give it a try. Unfortunately the trail seems to have died near the end of 2016 with a very tiny bit in 2017. I learned the hard way not to trust "old" but not-indicated-as-deprecated information floating around about the Raspberry Pi!

Unfortunately, I do not yet have enough experience in "reading correctly" what should be done and what should not be done. I have reviewed the documentation on the Raspberry site. I have read the dialogue elsewhere that says yes/no/okay but/ and the like.

What are the proper and correct steps needed to prepare the Pi 3B+ for booting from an SSD? I have a Raspberry Pi 3B+. What is the correct way to boot the O/S from an SSD without the need/requirement of an SD(HC|XC) or Flash drive or ... .

Not-with-standing among many reasons why or why not: Boot speed is not all that big of a deal. Availability of Flash or SD cards is not important. I have a laptop and desktop and a tablet and ... !

What is important is: I am in an area with horrible internet service (goes on and off without rhyme or reason when I am right in the middle of something). Stuff gets stolen. An SD card or Flash does not live-up-to-the-task(s) though the Raspberry Pi 3B+ is adequate "IF" it had enough storage. The SSD will remove the limited storage obstacle!

I have a Kingston SSD

Would someone suggest/list the steps? Or identify an article that is current and doesn't do strange things! No video suggestions because it eats up the scarce and expensive bandwidth that is metered/measured here. BTW the article on the Raspberry site is beyond my pay-grade at the moment!

User avatar
rpdom
Posts: 12741
Joined: Sun May 06, 2012 5:17 am
Location: Ankh-Morpork

Re: SSD Boot Process

Sat Aug 18, 2018 2:12 am

With the 3B+ it should just be a matter of downloading the latest Raspbian or Raspbian Lite image and using Etcher to write it to the SSD. Connect the SSD to the Pi. Connect network, also monitor, keyboard, mouse if wanted. Switch on Pi and wait for it to boot and resize the image to fill the SSD.

This is not 100% guaranteed, but will work with most devices.

LTolledo
Posts: 533
Joined: Sat Mar 17, 2018 7:29 am

Re: SSD Boot Process

Sat Aug 18, 2018 3:36 am

This is one of my setup:

1. RPI3B+, with heatsinks on SoC, LAN, memory (underside), in a modded case with 5v fan.
2. 5v 3.0A PSU
3. 1 USB port occupied by wireless dongle for keyboard and mouse
4. Sandisk 240GB SSD connected to Eluteng SATA to USB3.0 adapter cable, which in turn connected to RPi3B's USB port.
5. 7" HDMI monitor

What I did.
a. in a win10pc, flash the SSD with latest raspbian stretch with desktop
b. connected the SSD to RPi3B+
c. turned on the power. (for some here insert "pray" :D )
d. it booted... then proceeded to the installation.
e. selected WiFi to connect to network. (used default country setting GB)
f. after raspbian installation finished, reboot
g. after reboot, made changes in raspi-config, ran update and upgrade (and a couple of beers later... ;) .) installed/deleted software/packages/apps
h. setup samba.
i. test samba connection from other RPi, pc, other SBCs.
j. watched video using Kodi (file accessed from other SBC NAS)

that's it.

I've also tried 1TB Marshall HDD (in place of SSD), same results.
Also tried using Orico 2.5" HDD Clear case USB3.0, but wont boot. For me, the Eluteng cable is so far the best cable for SSD/HDD boot.
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

fruitoftheloom
Posts: 17288
Joined: Tue Mar 25, 2014 12:40 pm

Re: SSD Boot Process

Sat Aug 18, 2018 4:14 am

JPICentral wrote:
Sat Aug 18, 2018 1:42 am
Having read much about SSD Boot (pro/con/undecided/incomplete/outdated/incorrect per another/etc.) I think I would like to give it a try. Unfortunately the trail seems to have died near the end of 2016 with a very tiny bit in 2017. I learned the hard way not to trust "old" but not-indicated-as-deprecated information floating around about the Raspberry Pi!

Unfortunately, I do not yet have enough experience in "reading correctly" what should be done and what should not be done. I have reviewed the documentation on the Raspberry site. I have read the dialogue elsewhere that says yes/no/okay but/ and the like.

What are the proper and correct steps needed to prepare the Pi 3B+ for booting from an SSD? I have a Raspberry Pi 3B+. What is the correct way to boot the O/S from an SSD without the need/requirement of an SD(HC|XC) or Flash drive or ... .

Not-with-standing among many reasons why or why not: Boot speed is not all that big of a deal. Availability of Flash or SD cards is not important. I have a laptop and desktop and a tablet and ... !

What is important is: I am in an area with horrible internet service (goes on and off without rhyme or reason when I am right in the middle of something). Stuff gets stolen. An SD card or Flash does not live-up-to-the-task(s) though the Raspberry Pi 3B+ is adequate "IF" it had enough storage. The SSD will remove the limited storage obstacle!

I have a Kingston SSD

Would someone suggest/list the steps? Or identify an article that is current and doesn't do strange things! No video suggestions because it eats up the scarce and expensive bandwidth that is metered/measured here. BTW the article on the Raspberry site is beyond my pay-grade at the moment!

It was never a trial, it was an option that was added to the BCM2837 SoC bootcode:

https://www.raspberrypi.org/blog/pi-3-b ... rage-boot/


With the RPi 3B+ that option is now enabled by default so if no SD Card is present it will search for a USB MSD with the required ""boot"" files:

https://www.raspberrypi.org/blog/raspbe ... le-now-35/
Adieu

JPICentral
Posts: 33
Joined: Wed Jul 18, 2018 3:22 am
Location: Almost in the Mojave Desert

Re: SSD Boot Process

Sat Aug 18, 2018 6:52 am

The bit on the second link I never saw it which is not all that unusual in the plethora of material that has been generated over the years: " ... Improved PXE network and USB mass-storage booting ... ." So that is good, REAL good. I'll go poke the O/S on the SSD and plug it into the Pi and see what happens? That is the suggestion I believe was made. Sleep comes first followed by seven (7) cases of bottled water (my life is a mixture of all sorts of stuff).

I have had trouble with all the various tools to properly prepare the drive. The windows image tool put crap on the SD cards. Etcher did sorta something that made it almost impossible since the target device icon would never illuminate. The Berry->Accessories->SD Card Copier on the O/S desktop for jessie is the only one that has worked directly for me without a lot of putt-zing to fix the copied mess. dd was not pleasurable either since it never did what it was told (Cygwin on Win 10). It did a wonderful job of doing what it chose to do. dd on the Pi was another exercise in futility for me -- even following all the examples in the boundless literature I reviewed.

I like the thought that mass-storage booting is now a part of the Pi 3B+. I am glad I inquired and did NOT follow all of the possible rabbit-trails-to-no-where!

This will be a good project tomorrow when it is cool in the afternoon ( probably about 110 deg F in the shade ).

I'll put my notes as to what happened here (well, I will do my best).

It is really weird in the Pi-world where old and incomplete information is further used to exacerbate the issues. The other link gives, " still in beta testing ". I suppose it is better that the Pi hardware works.

JPICentral
Posts: 33
Joined: Wed Jul 18, 2018 3:22 am
Location: Almost in the Mojave Desert

Re: SSD Boot Process

Sat Aug 18, 2018 8:58 pm

<r>20180818 (1254 TZ=P)The news from here in the colonies next to the Mojave! The SSD boot, of course, did "NOT" work. I tried two (2) drives (Transcend 1tb USB and Kingston 640gb SSD) both did nothing whether directly connected to the Pi or to a powered hub.<br/>
<br/>
Now the good news! The Pi still boots from the SD card ... ! Then there is another bit: Etcher actually prepared both drives without barfing some incomprehensible (to me) error and subsequently failing to finish!<br/>
<br/>
Steps:<br/>
2018-06-27 Raspbian-stretch.img<br/>
Kingston SUV 400 240 Gb SSD<br/>
Etcher

Then a collection of "stuff" from articles that may show clues to the knowledgable ... The "stuff" follows ...
<CODE><s>

Code: Select all

</s><i>
</i>[email protected]:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  4.9G   24G  18% /
devtmpfs        460M     0  460M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M   13M  452M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   22M   21M  52% /boot
tmpfs            93M     0   93M   0% /run/user/1000
/dev/sdf2       4.4G  3.9G  233M  95% /media/pi/rootfs
/dev/sdf1        43M   22M   21M  51% /media/pi/boot
/dev/sde1       932G   13G  919G   2% /media/pi/PI3_HD_2018
<e>
</e></CODE>

I found an article that indicated the use of dmesg would be suitable for viewing the boot sequence ...
<CODE><s>

Code: Select all

</s><i>
</i>[email protected]:~ $ dmesg | more
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.52-v7+ ([email protected]) (gcc version 4.9.3
 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1123 SMP Wed Jun 27 17:35:49 B
ST 2018
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio
n cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c85000, node_mem_map ba3a100
0
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] percpu: Embedded 17 pages/cpu @ba34a000 s38720 r8192 d22720 u6963
2
[    0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1824 bcm2
708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_si
ze=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTU
UID=c82d2f70-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet
 splash plymouth.ignore-serial-consoles
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940236K/970752K available (7168K kernel code, 575K rwdata
, 2072K rodata, 1024K init, 706K bss, 22324K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c8fef4   ( 576 kB)
                      .bss : 0x80c96f40 - 0x80d47874   ( 707 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 25258 entries in 75 pages
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles:
 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 43980
46511078ns
[    0.000019] Switching to timer-based delay loop, resolution 52ns
[    0.000268] Console: colour dummy device 80x30
[    0.000285] console [tty1] enabled
[    0.000310] Calibrating delay loop (skipped), value calculated using timer fr
equency.. 38.40 BogoMIPS (lpj=192000)
[    0.000325] pid_max: default: 32768 minimum: 301
[    0.000642] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000656] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001591] Disabling memory control group subsystem
[    0.001667] CPU: Testing write buffer coherency: ok
[    0.002059] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002438] Setting up static identity map for 0x100000 - 0x10003c
[    0.002555] Hierarchical SRCU implementation.
[    0.003188] smp: Bringing up secondary CPUs ...
[    0.003865] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.004612] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.005344] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.005447] smp: Brought up 1 node, 4 CPUs
[    0.005458] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.005463] CPU: All CPU(s) started in HYP mode.
[    0.005467] CPU: Virtualization extensions available.
[    0.006320] devtmpfs: initialized
[    0.016333] random: get_random_u32 called from bucket_table_alloc+0xfc/0x24c 
with crng_init=0
[    0.017088] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3
 rev 4
[    0.017306] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ma
x_idle_ns: 19112604462750000 ns
[    0.017324] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.017879] pinctrl core: initialized pinctrl subsystem
[    0.018621] NET: Registered protocol family 16
[    0.021338] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.026238] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint 
registers.
[    0.026246] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.026454] Serial: AMBA PL011 UART driver
[    0.028107] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.028566] uart-pl011 3f201000.serial: could not find pctldev for node /soc/
[email protected]/uart0_pins, deferring probe
[    0.060166] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb813000, dma
chans=0x1
[    0.061582] SCSI subsystem initialized
[    0.061799] usbcore: registered new interface driver usbfs
[    0.061852] usbcore: registered new interface driver hub
[    0.061941] usbcore: registered new device driver usb
[    0.070084] raspberrypi-firmware soc:firmware: Attached to firmware from 2018
-07-03 14:15
[    0.071492] clocksource: Switched to clocksource arch_sys_counter
[    0.147545] VFS: Disk quotas dquot_6.6.0
[    0.147633] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.147814] FS-Cache: Loaded
[    0.148014] CacheFiles: Loaded
[    0.156842] NET: Registered protocol family 2
[    0.157565] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.157674] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.157859] TCP: Hash tables configured (established 8192 bind 8192)
[    0.157989] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.158033] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.158259] NET: Registered protocol family 1
[    0.158709] RPC: Registered named UNIX socket transport module.
[    0.158715] RPC: Registered udp transport module.
[    0.158720] RPC: Registered tcp transport module.
[    0.158725] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.160301] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counter
s available
[    0.163028] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.170963] FS-Cache: Netfs 'nfs' registered for caching
[    0.171593] NFS: Registering the id_resolver key type
[    0.171625] Key type id_resolver registered
[    0.171630] Key type id_legacy registered
[    0.171645] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.173532] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2
51)
[    0.173655] io scheduler noop registered
[    0.173661] io scheduler deadline registered (default)
[    0.173935] io scheduler cfq registered
[    0.173942] io scheduler mq-deadline registered
[    0.173948] io scheduler kyber registered
[    0.176610] BCM2708FB: allocated DMA memory [email protected]:~ $ dmesg | more
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.52-v7+ ([email protected]) (gcc version 4.9.3
 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1123 SMP Wed Jun 27 17:35:49 B
ST 2018
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio
n cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c85000, node_mem_map ba3a100
0
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] percpu: Embedded 17 pages/cpu @ba34a000 s38720 r8192 d22720 u6963
2
[    0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1824 bcm2
708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_si
ze=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTU
UID=c82d2f70-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet
 splash plymouth.ignore-serial-consoles
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940236K/970752K available (7168K kernel code, 575K rwdata
, 2072K rodata, 1024K init, 706K bss, 22324K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c8fef4   ( 576 kB)
                      .bss : 0x80c96f40 - 0x80d47874   ( 707 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 25258 entries in 75 pages
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles:
 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 43980
46511078ns
[    0.000019] Switching to timer-based delay loop, resolution 52ns
[    0.000268] Console: colour dummy device 80x30
[    0.000285] console [tty1] enabled
[    0.000310] Calibrating delay loop (skipped), value calculated using timer fr
equency.. 38.40 BogoMIPS (lpj=192000)
[    0.000325] pid_max: default: 32768 minimum: 301
[    0.000642] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000656] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001591] Disabling memory control group subsystem

[    0.176636] BCM2708FB: allocated DMA channel 0 @ bb813000
[    0.226642] Console: switching to colour frame buffer device 228x61
[    0.256848] bcm2835-rng 3f104000.rng: hwrng registered
[    0.256979] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000
000(1024 MiB)
[    0.257464] vc-sm: Videocore shared memory driver
[    0.257732] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f2
00000
[    0.267405] brd: module loaded
[    0.276300] loop: module loaded
[    0.276314] Loading iSCSI transport class v2.0-870.
[    0.276978] libphy: Fixed MDIO Bus: probed
[    0.277085] usbcore: registered new interface driver lan78xx
[    0.277141] usbcore: registered new interface driver smsc95xx
[    0.277157] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.505271] Core Release: 2.80a
[    0.505280] Setting default values for core params
[    0.505310] Finished setting default values for core params
[    0.705559] Using Buffer DMA mode
[    0.705565] Periodic Transfer Interrupt Enhancement - disabled
[    0.705570] Multiprocessor Interrupt Enhancement - disabled
[    0.705577] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.705587] Dedicated Tx FIFOs mode
[    0.705925] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbad
04000 dma = 0xfad04000 len=9024
[    0.705952] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.705974] dwc_otg: Microframe scheduler enabled
[    0.706060] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805e7fa8
[    0.706072] WARN::hcd_init_fiq:460: FIQ ASM at 0x805e8310 length 36
[    0.706084] WARN::hcd_init_fiq:486: MPHI regs_base at 0xbb87e000
[    0.706141] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.706173] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number
 1
[    0.706205] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.706254] Init: Port Power? op_state=1
[    0.706259] Init: Power Port (0)
[    0.706462] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.706472] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=
1
[    0.706480] usb usb1: Product: DWC OTG Controller
[    0.706488] usb usb1: Manufacturer: Linux 4.14.52-v7+ dwc_otg_hcd
[    0.706496] usb usb1: SerialNumber: 3f980000.usb
[    0.707116] hub 1-0:1.0: USB hub found
[    0.707157] hub 1-0:1.0: 1 port detected
[    0.707700] dwc_otg: FIQ enabled
[    0.707706] dwc_otg: NAK holdoff enabled
[    0.707710] dwc_otg: FIQ split-transaction FSM enabled
[    0.707720] Module dwc_common_port init
[    0.707965] usbcore: registered new interface driver usb-storage
[    0.708131] mousedev: PS/2 mouse device common for all mice
[    0.708208] IR NEC protocol handler initialized
[    0.708213] IR RC5(x/sz) protocol handler initialized
[    0.708219] IR RC6 protocol handler initialized
[    0.708224] IR JVC protocol handler initialized
[    0.708229] IR Sony protocol handler initialized
[    0.708234] IR SANYO protocol handler initialized
[    0.708239] IR Sharp protocol handler initialized
[    0.708244] IR MCE Keyboard/mouse protocol handler initialized
[    0.708249] IR XMP protocol handler initialized
[    0.708923] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.709210] bcm2835-cpufreq: min=600000 max=1200000
[    0.709559] sdhci: Secure Digital Host Controller Interface driver
[    0.709565] sdhci: Copyright(c) Pierre Ossman
[    0.709913] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.710232] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    0.710324] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.711760] ledtrig-cpu: registered to indicate activity on CPUs
[    0.711948] hidraw: raw HID events driver (C) Jiri Kosina
[    0.712073] usbcore: registered new interface driver usbhid
[    0.712078] usbhid: USB HID core driver
[    0.712835] vchiq: vchiq_init_state: slot_zero = bad80000, is_master = 0
[    0.714341] [vc_sm_connected_init]: start
[    0.723768] [vc_sm_connected_init]: end - returning 0
[    0.724407] Initializing XFRM netlink socket
[    0.724430] NET: Registered protocol family 17
[    0.724525] Key type dns_resolver registered
[    0.725061] Registering SWP/SWPB emulation handler
[    0.725639] registered taskstats version 1
[    0.731600] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    0.731679] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud 
= 0) is a PL011 rev2
[    0.733452] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.733462] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    0.792111] sdhost: log_buf @ bad07000 (fad07000)
[    0.830974] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    0.832540] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.834090] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.836868] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    0.871512] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.872502] of_cfs_init
[    0.872591] of_cfs_init: OK
[    0.873169] Waiting for root device PARTUUID=c82d2f70-02...
[    0.914430] random: fast init done
[    0.921616] Indeed it is in host mode hprt0 = 00021501
[    0.988679] mmc0: host does not support reading read-only switch, assuming wr
ite-enable
[    0.991322] mmc0: new high speed SDHC card at address 0001
[    0.991868] mmcblk0: mmc0:0001 GB1QT 29.8 GiB
[    0.993283]  mmcblk0: p1 p2
[    1.014418] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. O
pts: (null)
[    1.014475] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.017880] mmc1: new high speed SDIO card at address 0001
[    1.023417] devtmpfs: mounted
[    1.026583] Freeing unused kernel memory: 1024K
[    1.131546] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.131688] Indeed it is in host mode hprt0 = 00001101
[    1.371815] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.371830] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.372472] hub 1-1:1.0: USB hub found
[    1.372568] hub 1-1:1.0: 5 ports detected
[    1.459292] systemd[1]: System time before build time, advancing clock.
[    1.588579] NET: Registered protocol family 10
[    1.589774] Segment Routing with IPv6
[    1.599892] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.619192] random: systemd: uninitialized urandom read (16 bytes read)
[    1.624440] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SEL
INUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +
XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    1.625036] systemd[1]: Detected architecture arm.
[    1.626069] systemd[1]: Set hostname to <raspberrypi>.
[    1.668176] random: systemd: uninitialized urandom read (16 bytes read)
[    1.691643] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.700696] random: systemd-cryptse: uninitialized urandom read (16 bytes rea
d)
[    1.821842] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    1.821857] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber
=0
[    1.824580] smsc95xx v1.0.6
[    1.925079] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-
1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:60:73:59
[    2.021550] usb 1-1.2: new high-speed USB device number 4 using dwc_otg
[    2.122428] systemd[1]: Listening on Syslog Socket.
[    2.122870] systemd[1]: Reached target Swap.
[    2.123654] systemd[1]: Created slice System Slice.
[    2.126431] systemd[1]: Mounting RPC Pipe File System...
[    2.126981] systemd[1]: Listening on udev Control Socket.
[    2.127545] systemd[1]: Started Forward Password Requests to Wall Directory W
atch.
[    2.127983] systemd[1]: Listening on Journal Socket.
[    2.153095] usb 1-1.2: New USB device found, idVendor=2109, idProduct=2812
[    2.153111] usb 1-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber
=0
[    2.153120] usb 1-1.2: Product: USB 2.0 HUB
                     
[    2.153923] hub 1-1.2:1.0: USB hub found
[    2.154138] hub 1-1.2:1.0: 4 ports detected
[    2.237140] i2c /dev entries driver
[    2.608888] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    2.730125] systemd-journald[93]: Received request to flush runtime journal f
rom PID 1
[    3.198309] snd_bcm2835: module is from the staging directory, the quality is
 unknown, you have been warned.
[    3.203333] bcm2835_alsa bcm2835_alsa: card created with 8 channels
[    3.338736] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    3.347851] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdi
o.bin for chip 0x00a9a6(43430) rev 0x000001
[    3.348149] usbcore: registered new interface driver brcmfmac
[    3.381656] usb 1-1.2.2: new high-speed USB device number 5 using dwc_otg
[    3.525782] usb 1-1.2.2: New USB device found, idVendor=0781, idProduct=b7b9
[    3.525802] usb 1-1.2.2: New USB device strings: Mfr=3, Product=4, SerialNumb
er=5
[    3.525810] usb 1-1.2.2: Product: SDDR-189
[    3.525819] usb 1-1.2.2: Manufacturer: SanDisk
[    3.525827] usb 1-1.2.2: SerialNumber: 2008081401127
[    3.527122] usb-storage 1-1.2.2:1.0: USB Mass Storage device detected
[    3.576718] scsi host0: usb-storage 1-1.2.2:1.0
[    3.584148] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2
017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[    3.585216] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.
11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data:
 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-10-23 03:47:1
4 
[    3.681591] usb 1-1.2.3: new high-speed USB device number 6 using dwc_otg
[    3.830059] usb 1-1.2.3: New USB device found, idVendor=174c, idProduct=5106
[    3.830079] usb 1-1.2.3: New USB device strings: Mfr=2, Product=3, SerialNumb
er=1
[    3.830087] usb 1-1.2.3: Product: StoreJet Transcend
[    3.830095] usb 1-1.2.3: Manufacturer: StoreJet Transcend
[    3.830105] usb 1-1.2.3: SerialNumber: S318J9AF640309      
[    3.830935] usb-storage 1-1.2.3:1.0: USB Mass Storage device detected
[    3.831352] scsi host1: usb-storage 1-1.2.3:1.0
[    3.941629] usb 1-1.2.4: new high-speed USB device number 7 using dwc_otg
[    4.083494] usb 1-1.2.4: New USB device found, idVendor=174c, idProduct=1351
[    4.083514] usb 1-1.2.4: New USB device strings: Mfr=2, Product=3, SerialNumb
er=1
[    4.083522] usb 1-1.2.4: Product: USB3.1 Device
[    4.083531] usb 1-1.2.4: Manufacturer: Generic
[    4.083539] usb 1-1.2.4: SerialNumber: 12345678912B
[    4.084525] usb-storage 1-1.2.4:1.0: USB Mass Storage device detected
[    4.086355] scsi host2: usb-storage 1-1.2.4:1.0
[    4.409495] usb 1-1.2: USB disconnect, device number 4
[    4.409518] usb 1-1.2.2: USB disconnect, device number 5
[    4.478897] usb 1-1.2.3: USB disconnect, device number 6
[    4.565003] usb 1-1.2.4: USB disconnect, device number 7
[    4.747470] uart-pl011 3f201000.serial: no DMA platform data
[    4.931631] usb 1-1.2: new high-speed USB device number 8 using dwc_otg
[    5.031563] usb 1-1.2: device descriptor read/64, error -71
[    5.292991] usb 1-1.2: New USB device found, idVendor=2109, idProduct=2812
[    5.293007] usb 1-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber
=0
[    5.293016] usb 1-1.2: Product: USB 2.0 HUB
                     
[    5.293824] hub 1-1.2:1.0: USB hub found
[    5.294021] hub 1-1.2:1.0: 4 ports detected
[    5.609131] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    5.609191] brcmfmac: power management disabled
[    5.631556] usb 1-1.2.2: new high-speed USB device number 9 using dwc_otg
[    5.758354] random: crng init done
[    5.758371] random: 7 urandom warning(s) missedFilesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  4.9G   24G  18% /
devtmpfs        460M     0  460M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M   13M  452M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   22M   21M  52% /boot
tmpfs            93M     0   93M   0% /run/user/1000
/dev/sdf2       4.4G  3.9G  233M  95% /media/pi/rootfs
/dev/sdf1        43M   22M   21M  51% /media/pi/boot
/dev/sde1       932G   13G  919G   2% /media/pi/PI3_HD_2018Filesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  4.9G   24G  18% /
devtmpfs        460M     0  460M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M   13M  452M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   22M   21M  52% /boot
tmpfs            93M     0   93M   0% /run/user/1000
/dev/sdf2       4.4G  3.9G  233M  95% /media/pi/rootfs
/dev/sdf1        43M   22M   21M  51% /media/pi/boot
/dev/sde1       932G   13G  919G   2% /media/pi/PI3_HD_2018 due to ratelimiting
[    5.775605] usb 1-1.2.2: New USB device found, idVendor=0781, idProduct=b7b9
[    5.775625] usb 1-1.2.2: New USB device strings: Mfr=3, Product=4, SerialNumb
er=5
[    5.775636] usb 1-1.2.2: Product: SDDR-189
[    5.775644] usb 1-1.2.2: Manufacturer: SanDisk
[    5.775653] usb 1-1.2.2: SerialNumber: 2008081401127
[    5.776833] usb-storage 1-1.2.2:1.0: USB Mass Storage device detected
[    5.777259] scsi host0: usb-storage 1-1.2.2:1.0
[    5.891559] usb 1-1.2.3: new high-speed USB device number 10 using dwc_otg
[    6.033433] usb 1-1.2.3: New USB device found, idVendor=174c, idProduct=5106
[    6.033452] usb 1-1.2.3: New USB device strings: Mfr=2, Product=3, SerialNumb
er=1
[    6.033462] usb 1-1.2.3: Product: StoreJet Transcend
[    6.033470] usb 1-1.2.3: Manufacturer: StoreJet Transcend
[    6.033479] usb 1-1.2.3: SerialNumber: S318J9AF640309      
[    6.034520] usb-storage 1-1.2.3:1.0: USB Mass Storage device detected
[    6.037715] scsi host1: usb-storage 1-1.2.3:1.0
[    6.151626] usb 1-1.2.4: new high-speed USB device number 11 using dwc_otg
[    6.293675] usb 1-1.2.4: New USB device found, idVendor=174c, idProduct=1351
[    6.293699] usb 1-1.2.4: New USB device strings: Mfr=2, Product=3, SerialNumb
er=1
[    6.293708] usb 1-1.2.4: Product: USB3.1 Device
[    6.293716] usb 1-1.2.4: Manufacturer: Generic
[    6.293724] usb 1-1.2.4: SerialNumber: 12345678912B
[    6.294940] usb-storage 1-1.2.4:1.0: USB Mass Storage device detected
[    6.302478] scsi host2: usb-storage 1-1.2.4:1.0
[    6.375507] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    6.375983] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.562125] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:1
02396k SSFS1020000a
[    6.792853] scsi 0:0:0:0: Direct-Access     SanDisk  mSD SDDR-189     1804 PQ
: 0 ANSI: 0
[    6.796021] scsi 0:0:0:1: Direct-Access     SanDisk  SD  SDDR-189     1804 PQ
: 0 ANSI: 0
[    6.797668] sd 0:0:0:1: [sdb] Attached SCSI removable disk
[    6.798677] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    6.800563] scsi 0:0:0:2: Direct-Access     SanDisk  MSxDSDDR-189     1804 PQ
: 0 ANSI: 0
[    6.802500] scsi 0:0:0:3: Direct-Access     SanDisk  CF  SDDR-189     1804 PQ
: 0 ANSI: 0
[    6.806362] sd 0:0:0:3: [sdd] Attached SCSI removable disk
[    6.807632] sd 0:0:0:2: [sdc] Attached SCSI removable disk
[    6.813533] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    6.813671] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    6.813795] sd 0:0:0:2: Attached scsi generic sg2 type 0
[    6.813937] sd 0:0:0:3: Attached scsi generic sg3 type 0
[    7.118476] scsi 1:0:0:0: Direct-Access     StoreJet Transcend        0    PQ
: 0 ANSI: 6
[    7.119478] sd 1:0:0:0: [sde] 1953525168 512-byte logical blocks: (1.00 TB/93
2 GiB)1020000a
[    7.119507] sd 1:0:0:0: Attached scsi generic sg4 type 01020000a
[    7.119920] sd 1:0:0:0: [sde] Write Protect is off
[    7.119932] sd 1:0:0:0: [sde] Mode Sense: 43 00 00 00
[    7.120384] sd 1:0:0:0: [sde] Write cache: enabled, read cache: enabled, does
n't support DPO or FUA
[    7.155440]  sde: sde1
[    7.157540] sd 1:0:0:0: [sde] Attached SCSI disk
[    7.352612] scsi 2:0:0:0: Direct-Access     KINGSTON  SUV400S37240G   0    PQ
: 0 ANSI: 6
[    7.353176] sd 2:0:0:0: Attached scsi generic sg5 type 0
[    7.353521] sd 2:0:0:0: [sdf] 468862128 512-byte logical blocks: (240 GB/224 
GiB)
[    7.353977] sd 2:0:0:0: [sdf] Write Protect is off
[    7.353983] sd 2:0:0:0: [sdf] Mode Sense: 43 00 00 00
[    7.354394] sd 2:0:0:0: [sdf] Write cache: enabled, read cache: enabled, does
n't support DPO or FUA
[    7.356243]  sdf: sdf1 sdf2
[    7.358029] sd 2:0:0:0: [sdf] Attached SCSI disk
[    9.282218] Bluetooth: Core ver 2.22
[    9.282313] NET: Registered protocol family 31
[    9.282320] Bluetooth: HCI device and connection manager initialized
[    9.282342] Bluetooth: HCI socket layer initialized
[    9.282356] Bluetooth: L2CAP socket layer initialized
[    9.282390] Bluetooth: SCO socket layer initialized
[    9.303527] Bluetooth: HCI UART driver ver 2.3
[    9.303543] Bluetooth: HCI UART protocol H4 registered
[    9.303551] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    9.303760] Bluetooth: HCI UART protocol Broadcom registered
[    9.478069] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.478080] Bluetooth: BNEP filters: protocol multicast
[    9.478100] Bluetooth: BNEP socket layer initialized
[    9.622640] Bluetooth: RFCOMM TTY layer initialized
[    9.622670] Bluetooth: RFCOMM socket layer initialized
[    9.622695] Bluetooth: RFCOMM ver 1.11
[   10.543219] fuse init (API version 7.26)
[   13.612073] EXT4-fs (sdf2): mounted filesystem with ordered data mode. Opts: 
(null)Filesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  4.9G   24G  18% /
devtmpfs        460M     0  460M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M   13M  452M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   22M   21M  52% /boot
tmpfs            93M     0   93M   0% /run/user/1000
/dev/sdf2       4.4G  3.9G  233M  95% /media/pi/rootfs
/dev/sdf1        43M   22M   21M  51% /media/pi/boot
/dev/sde1       932G   13G  919G   2% /media/pi/PI3_HD_2018
[   22.655879] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   22.655912] Bluetooth: HIDP socket layer initialized
[   22.659999] hid-generic 0005:045E:0700.0001: unknown main item tag 0x0
[   22.660420] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/platfo
rm/soc/3f201000.serial/tty/ttyAMA0/hci0/hci0:11/0005:045E:0700.0001/input/input0
[   22.664856] hid-generic 0005:045E:0700.0001: input,hidraw0: BLUETOOTH HID v1.
00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on b8:27:eb:ca:d9:f3
[   36.717023] hid-generic 0005:046D:B330.0002: unknown main item tag 0x0
[   36.717804] input: Logitech Keyboard K480 as /devices/platform/soc/3f201000.s
erial/tty/ttyAMA0/hci0/hci0:12/0005:046D:B330.0002/input/input1
[   36.720519] hid-generic 0005:046D:B330.0002: input,hidraw1: BLUETOOTH HID v28
.00 Keyboard [Logitech Keyboard K480] on b8:27:eb:ca:d9:f3

<e>
</e></CODE></r>
So the output from dmesg should give someone who knows what they are doing maybe half-a-clue what my Pi is doing and why it will not boot from the SSD?

NEXT:
An article gave the following tidbit that uses vcgencmd command that is undocumented on my Pi but produces output that may be meaningful to those who have been here before ...

Code: Select all

{{ $ vcgencmd otp_dump | grep 17: This queries the hardware registers for the boot mode. It will print a number other than 0x3020000a . Next, edit /boot/config.txt and at the end of the file insert this line: program_usb_boot_mode=1 When the Rapberry Pi is rebooted, this line rewrites the register queried above so that now the command should output: $ vcgencmd otp_dump | grep 17: 17:3020000a This enables the USB Mass Storage Device boot mode on that Raspberry Pi. From now on, that particular machine will boot either from SD card or USB MSD. }}
This command on my Pi Produced ...

[email protected]:~ $ vcgencmd
[email protected]:~ $ man vcgencmd
No manual entry for vcgencmd
See 'man 7 undocumented' for help when manual pages are not available.
[email protected]:~ $ vcgencmd otp_dump | grep 17:
17:1020000a
[email protected]:~ $

So, not smok'n anything and a bewildered-puzzled feeling in my grey-matter I hope someone will see this and make enough sense of it to give me some advice as to "WHAT?" next.



Thanks in advance for giving me the clues I need to proceed.
regards ...

PS -- got stuck in "Drafts" and could edit and save. By accident/Mystery I clicked, smiled, gave a "symbol" and I got back here. How do I gracefully exit drafts and get back here to preview and submit??? Now my internet connection is flaky so I have to submit. Hope I got all the corrections made ...

LTolledo
Posts: 533
Joined: Sat Mar 17, 2018 7:29 am

Re: SSD Boot Process

Sat Aug 18, 2018 9:10 pm

Seems strange that the OTP bit for a RPi3B+ is not factory set, as its widely known (and documented) as already set by default.

could you reconfirm to us what is the model of the RPi that you have.
when you boot from microSD run this command

Code: Select all

cat /proc/cpuinfo
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

fruitoftheloom
Posts: 17288
Joined: Tue Mar 25, 2014 12:40 pm

Re: SSD Boot Process

Sat Aug 18, 2018 9:47 pm

JPICentral wrote:
Sat Aug 18, 2018 8:58 pm
<r>20180818 (1254 TZ=P)The news from here in the colonies next to the Mojave! The SSD boot, of course, did "NOT" work. I tried two (2) drives (Transcend 1tb USB and Kingston 640gb SSD) both did nothing whether directly connected to the Pi or to a powered hub.<br/>
<br/>
Now the good news! The Pi still boots from the SD card ... ! Then there is another bit: Etcher actually prepared both drives without barfing some incomprehensible (to me) error and subsequently failing to finish!<br/>
<br/>
Steps:<br/>
2018-06-27 Raspbian-stretch.img<br/>
Kingston SUV 400 240 Gb SSD<br/>
Etcher

Then a collection of "stuff" from articles that may show clues to the knowledgable ... The "stuff" follows ...
<CODE><s>

Code: Select all

</s><i>
</i>[email protected]:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  4.9G   24G  18% /
devtmpfs        460M     0  460M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M   13M  452M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   22M   21M  52% /boot
tmpfs            93M     0   93M   0% /run/user/1000
/dev/sdf2       4.4G  3.9G  233M  95% /media/pi/rootfs
/dev/sdf1        43M   22M   21M  51% /media/pi/boot
/dev/sde1       932G   13G  919G   2% /media/pi/PI3_HD_2018
<e>
</e></CODE>

I found an article that indicated the use of dmesg would be suitable for viewing the boot sequence ...
<CODE><s>

Code: Select all

</s><i>
</i>[email protected]:~ $ dmesg | more
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.52-v7+ ([email protected]) (gcc version 4.9.3
 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1123 SMP Wed Jun 27 17:35:49 B
ST 2018
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio
n cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c85000, node_mem_map ba3a100
0
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] percpu: Embedded 17 pages/cpu @ba34a000 s38720 r8192 d22720 u6963
2
[    0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1824 bcm2
708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_si
ze=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTU
UID=c82d2f70-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet
 splash plymouth.ignore-serial-consoles
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940236K/970752K available (7168K kernel code, 575K rwdata
, 2072K rodata, 1024K init, 706K bss, 22324K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c8fef4   ( 576 kB)
                      .bss : 0x80c96f40 - 0x80d47874   ( 707 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 25258 entries in 75 pages
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles:
 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 43980
46511078ns
[    0.000019] Switching to timer-based delay loop, resolution 52ns
[    0.000268] Console: colour dummy device 80x30
[    0.000285] console [tty1] enabled
[    0.000310] Calibrating delay loop (skipped), value calculated using timer fr
equency.. 38.40 BogoMIPS (lpj=192000)
[    0.000325] pid_max: default: 32768 minimum: 301
[    0.000642] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000656] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001591] Disabling memory control group subsystem
[    0.001667] CPU: Testing write buffer coherency: ok
[    0.002059] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002438] Setting up static identity map for 0x100000 - 0x10003c
[    0.002555] Hierarchical SRCU implementation.
[    0.003188] smp: Bringing up secondary CPUs ...
[    0.003865] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.004612] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.005344] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.005447] smp: Brought up 1 node, 4 CPUs
[    0.005458] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.005463] CPU: All CPU(s) started in HYP mode.
[    0.005467] CPU: Virtualization extensions available.
[    0.006320] devtmpfs: initialized
[    0.016333] random: get_random_u32 called from bucket_table_alloc+0xfc/0x24c 
with crng_init=0
[    0.017088] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3
 rev 4
[    0.017306] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ma
x_idle_ns: 19112604462750000 ns
[    0.017324] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.017879] pinctrl core: initialized pinctrl subsystem
[    0.018621] NET: Registered protocol family 16
[    0.021338] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.026238] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint 
registers.
[    0.026246] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.026454] Serial: AMBA PL011 UART driver
[    0.028107] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.028566] uart-pl011 3f201000.serial: could not find pctldev for node /soc/
[email protected]/uart0_pins, deferring probe
[    0.060166] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb813000, dma
chans=0x1
[    0.061582] SCSI subsystem initialized
[    0.061799] usbcore: registered new interface driver usbfs
[    0.061852] usbcore: registered new interface driver hub
[    0.061941] usbcore: registered new device driver usb
[    0.070084] raspberrypi-firmware soc:firmware: Attached to firmware from 2018
-07-03 14:15
[    0.071492] clocksource: Switched to clocksource arch_sys_counter
[    0.147545] VFS: Disk quotas dquot_6.6.0
[    0.147633] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.147814] FS-Cache: Loaded
[    0.148014] CacheFiles: Loaded
[    0.156842] NET: Registered protocol family 2
[    0.157565] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.157674] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.157859] TCP: Hash tables configured (established 8192 bind 8192)
[    0.157989] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.158033] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.158259] NET: Registered protocol family 1
[    0.158709] RPC: Registered named UNIX socket transport module.
[    0.158715] RPC: Registered udp transport module.
[    0.158720] RPC: Registered tcp transport module.
[    0.158725] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.160301] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counter
s available
[    0.163028] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.170963] FS-Cache: Netfs 'nfs' registered for caching
[    0.171593] NFS: Registering the id_resolver key type
[    0.171625] Key type id_resolver registered
[    0.171630] Key type id_legacy registered
[    0.171645] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.173532] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2
51)
[    0.173655] io scheduler noop registered
[    0.173661] io scheduler deadline registered (default)
[    0.173935] io scheduler cfq registered
[    0.173942] io scheduler mq-deadline registered
[    0.173948] io scheduler kyber registered
[    0.176610] BCM2708FB: allocated DMA memory [email protected]:~ $ dmesg | more
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.52-v7+ ([email protected]) (gcc version 4.9.3
 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1123 SMP Wed Jun 27 17:35:49 B
ST 2018
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio
n cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c85000, node_mem_map ba3a100
0
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] percpu: Embedded 17 pages/cpu @ba34a000 s38720 r8192 d22720 u6963
2
[    0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1824 bcm2
708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_si
ze=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTU
UID=c82d2f70-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet
 splash plymouth.ignore-serial-consoles
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940236K/970752K available (7168K kernel code, 575K rwdata
, 2072K rodata, 1024K init, 706K bss, 22324K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c8fef4   ( 576 kB)
                      .bss : 0x80c96f40 - 0x80d47874   ( 707 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 25258 entries in 75 pages
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles:
 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 43980
46511078ns
[    0.000019] Switching to timer-based delay loop, resolution 52ns
[    0.000268] Console: colour dummy device 80x30
[    0.000285] console [tty1] enabled
[    0.000310] Calibrating delay loop (skipped), value calculated using timer fr
equency.. 38.40 BogoMIPS (lpj=192000)
[    0.000325] pid_max: default: 32768 minimum: 301
[    0.000642] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000656] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001591] Disabling memory control group subsystem

[    0.176636] BCM2708FB: allocated DMA channel 0 @ bb813000
[    0.226642] Console: switching to colour frame buffer device 228x61
[    0.256848] bcm2835-rng 3f104000.rng: hwrng registered
[    0.256979] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000
000(1024 MiB)
[    0.257464] vc-sm: Videocore shared memory driver
[    0.257732] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f2
00000
[    0.267405] brd: module loaded
[    0.276300] loop: module loaded
[    0.276314] Loading iSCSI transport class v2.0-870.
[    0.276978] libphy: Fixed MDIO Bus: probed
[    0.277085] usbcore: registered new interface driver lan78xx
[    0.277141] usbcore: registered new interface driver smsc95xx
[    0.277157] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.505271] Core Release: 2.80a
[    0.505280] Setting default values for core params
[    0.505310] Finished setting default values for core params
[    0.705559] Using Buffer DMA mode
[    0.705565] Periodic Transfer Interrupt Enhancement - disabled
[    0.705570] Multiprocessor Interrupt Enhancement - disabled
[    0.705577] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.705587] Dedicated Tx FIFOs mode
[    0.705925] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbad
04000 dma = 0xfad04000 len=9024
[    0.705952] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.705974] dwc_otg: Microframe scheduler enabled
[    0.706060] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805e7fa8
[    0.706072] WARN::hcd_init_fiq:460: FIQ ASM at 0x805e8310 length 36
[    0.706084] WARN::hcd_init_fiq:486: MPHI regs_base at 0xbb87e000
[    0.706141] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.706173] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number
 1
[    0.706205] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.706254] Init: Port Power? op_state=1
[    0.706259] Init: Power Port (0)
[    0.706462] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.706472] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=
1
[    0.706480] usb usb1: Product: DWC OTG Controller
[    0.706488] usb usb1: Manufacturer: Linux 4.14.52-v7+ dwc_otg_hcd
[    0.706496] usb usb1: SerialNumber: 3f980000.usb
[    0.707116] hub 1-0:1.0: USB hub found
[    0.707157] hub 1-0:1.0: 1 port detected
[    0.707700] dwc_otg: FIQ enabled
[    0.707706] dwc_otg: NAK holdoff enabled
[    0.707710] dwc_otg: FIQ split-transaction FSM enabled
[    0.707720] Module dwc_common_port init
[    0.707965] usbcore: registered new interface driver usb-storage
[    0.708131] mousedev: PS/2 mouse device common for all mice
[    0.708208] IR NEC protocol handler initialized
[    0.708213] IR RC5(x/sz) protocol handler initialized
[    0.708219] IR RC6 protocol handler initialized
[    0.708224] IR JVC protocol handler initialized
[    0.708229] IR Sony protocol handler initialized
[    0.708234] IR SANYO protocol handler initialized
[    0.708239] IR Sharp protocol handler initialized
[    0.708244] IR MCE Keyboard/mouse protocol handler initialized
[    0.708249] IR XMP protocol handler initialized
[    0.708923] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.709210] bcm2835-cpufreq: min=600000 max=1200000
[    0.709559] sdhci: Secure Digital Host Controller Interface driver
[    0.709565] sdhci: Copyright(c) Pierre Ossman
[    0.709913] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.710232] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    0.710324] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.711760] ledtrig-cpu: registered to indicate activity on CPUs
[    0.711948] hidraw: raw HID events driver (C) Jiri Kosina
[    0.712073] usbcore: registered new interface driver usbhid
[    0.712078] usbhid: USB HID core driver
[    0.712835] vchiq: vchiq_init_state: slot_zero = bad80000, is_master = 0
[    0.714341] [vc_sm_connected_init]: start
[    0.723768] [vc_sm_connected_init]: end - returning 0
[    0.724407] Initializing XFRM netlink socket
[    0.724430] NET: Registered protocol family 17
[    0.724525] Key type dns_resolver registered
[    0.725061] Registering SWP/SWPB emulation handler
[    0.725639] registered taskstats version 1
[    0.731600] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    0.731679] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud 
= 0) is a PL011 rev2
[    0.733452] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.733462] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    0.792111] sdhost: log_buf @ bad07000 (fad07000)
[    0.830974] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    0.832540] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.834090] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.836868] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    0.871512] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.872502] of_cfs_init
[    0.872591] of_cfs_init: OK
[    0.873169] Waiting for root device PARTUUID=c82d2f70-02...
[    0.914430] random: fast init done
[    0.921616] Indeed it is in host mode hprt0 = 00021501
[    0.988679] mmc0: host does not support reading read-only switch, assuming wr
ite-enable
[    0.991322] mmc0: new high speed SDHC card at address 0001
[    0.991868] mmcblk0: mmc0:0001 GB1QT 29.8 GiB
[    0.993283]  mmcblk0: p1 p2
[    1.014418] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. O
pts: (null)
[    1.014475] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.017880] mmc1: new high speed SDIO card at address 0001
[    1.023417] devtmpfs: mounted
[    1.026583] Freeing unused kernel memory: 1024K
[    1.131546] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.131688] Indeed it is in host mode hprt0 = 00001101
[    1.371815] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.371830] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.372472] hub 1-1:1.0: USB hub found
[    1.372568] hub 1-1:1.0: 5 ports detected
[    1.459292] systemd[1]: System time before build time, advancing clock.
[    1.588579] NET: Registered protocol family 10
[    1.589774] Segment Routing with IPv6
[    1.599892] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.619192] random: systemd: uninitialized urandom read (16 bytes read)
[    1.624440] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SEL
INUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +
XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    1.625036] systemd[1]: Detected architecture arm.
[    1.626069] systemd[1]: Set hostname to <raspberrypi>.
[    1.668176] random: systemd: uninitialized urandom read (16 bytes read)
[    1.691643] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.700696] random: systemd-cryptse: uninitialized urandom read (16 bytes rea
d)
[    1.821842] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    1.821857] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber
=0
[    1.824580] smsc95xx v1.0.6
[    1.925079] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-
1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:60:73:59
[    2.021550] usb 1-1.2: new high-speed USB device number 4 using dwc_otg
[    2.122428] systemd[1]: Listening on Syslog Socket.
[    2.122870] systemd[1]: Reached target Swap.
[    2.123654] systemd[1]: Created slice System Slice.
[    2.126431] systemd[1]: Mounting RPC Pipe File System...
[    2.126981] systemd[1]: Listening on udev Control Socket.
[    2.127545] systemd[1]: Started Forward Password Requests to Wall Directory W
atch.
[    2.127983] systemd[1]: Listening on Journal Socket.
[    2.153095] usb 1-1.2: New USB device found, idVendor=2109, idProduct=2812
[    2.153111] usb 1-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber
=0
[    2.153120] usb 1-1.2: Product: USB 2.0 HUB
                     
[    2.153923] hub 1-1.2:1.0: USB hub found
[    2.154138] hub 1-1.2:1.0: 4 ports detected
[    2.237140] i2c /dev entries driver
[    2.608888] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    2.730125] systemd-journald[93]: Received request to flush runtime journal f
rom PID 1
[    3.198309] snd_bcm2835: module is from the staging directory, the quality is
 unknown, you have been warned.
[    3.203333] bcm2835_alsa bcm2835_alsa: card created with 8 channels
[    3.338736] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    3.347851] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdi
o.bin for chip 0x00a9a6(43430) rev 0x000001
[    3.348149] usbcore: registered new interface driver brcmfmac
[    3.381656] usb 1-1.2.2: new high-speed USB device number 5 using dwc_otg
[    3.525782] usb 1-1.2.2: New USB device found, idVendor=0781, idProduct=b7b9
[    3.525802] usb 1-1.2.2: New USB device strings: Mfr=3, Product=4, SerialNumb
er=5
[    3.525810] usb 1-1.2.2: Product: SDDR-189
[    3.525819] usb 1-1.2.2: Manufacturer: SanDisk
[    3.525827] usb 1-1.2.2: SerialNumber: 2008081401127
[    3.527122] usb-storage 1-1.2.2:1.0: USB Mass Storage device detected
[    3.576718] scsi host0: usb-storage 1-1.2.2:1.0
[    3.584148] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2
017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[    3.585216] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.
11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data:
 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-10-23 03:47:1
4 
[    3.681591] usb 1-1.2.3: new high-speed USB device number 6 using dwc_otg
[    3.830059] usb 1-1.2.3: New USB device found, idVendor=174c, idProduct=5106
[    3.830079] usb 1-1.2.3: New USB device strings: Mfr=2, Product=3, SerialNumb
er=1
[    3.830087] usb 1-1.2.3: Product: StoreJet Transcend
[    3.830095] usb 1-1.2.3: Manufacturer: StoreJet Transcend
[    3.830105] usb 1-1.2.3: SerialNumber: S318J9AF640309      
[    3.830935] usb-storage 1-1.2.3:1.0: USB Mass Storage device detected
[    3.831352] scsi host1: usb-storage 1-1.2.3:1.0
[    3.941629] usb 1-1.2.4: new high-speed USB device number 7 using dwc_otg
[    4.083494] usb 1-1.2.4: New USB device found, idVendor=174c, idProduct=1351
[    4.083514] usb 1-1.2.4: New USB device strings: Mfr=2, Product=3, SerialNumb
er=1
[    4.083522] usb 1-1.2.4: Product: USB3.1 Device
[    4.083531] usb 1-1.2.4: Manufacturer: Generic
[    4.083539] usb 1-1.2.4: SerialNumber: 12345678912B
[    4.084525] usb-storage 1-1.2.4:1.0: USB Mass Storage device detected
[    4.086355] scsi host2: usb-storage 1-1.2.4:1.0
[    4.409495] usb 1-1.2: USB disconnect, device number 4
[    4.409518] usb 1-1.2.2: USB disconnect, device number 5
[    4.478897] usb 1-1.2.3: USB disconnect, device number 6
[    4.565003] usb 1-1.2.4: USB disconnect, device number 7
[    4.747470] uart-pl011 3f201000.serial: no DMA platform data
[    4.931631] usb 1-1.2: new high-speed USB device number 8 using dwc_otg
[    5.031563] usb 1-1.2: device descriptor read/64, error -71
[    5.292991] usb 1-1.2: New USB device found, idVendor=2109, idProduct=2812
[    5.293007] usb 1-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber
=0
[    5.293016] usb 1-1.2: Product: USB 2.0 HUB
                     
[    5.293824] hub 1-1.2:1.0: USB hub found
[    5.294021] hub 1-1.2:1.0: 4 ports detected
[    5.609131] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    5.609191] brcmfmac: power management disabled
[    5.631556] usb 1-1.2.2: new high-speed USB device number 9 using dwc_otg
[    5.758354] random: crng init done
[    5.758371] random: 7 urandom warning(s) missedFilesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  4.9G   24G  18% /
devtmpfs        460M     0  460M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M   13M  452M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   22M   21M  52% /boot
tmpfs            93M     0   93M   0% /run/user/1000
/dev/sdf2       4.4G  3.9G  233M  95% /media/pi/rootfs
/dev/sdf1        43M   22M   21M  51% /media/pi/boot
/dev/sde1       932G   13G  919G   2% /media/pi/PI3_HD_2018Filesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  4.9G   24G  18% /
devtmpfs        460M     0  460M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M   13M  452M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   22M   21M  52% /boot
tmpfs            93M     0   93M   0% /run/user/1000
/dev/sdf2       4.4G  3.9G  233M  95% /media/pi/rootfs
/dev/sdf1        43M   22M   21M  51% /media/pi/boot
/dev/sde1       932G   13G  919G   2% /media/pi/PI3_HD_2018 due to ratelimiting
[    5.775605] usb 1-1.2.2: New USB device found, idVendor=0781, idProduct=b7b9
[    5.775625] usb 1-1.2.2: New USB device strings: Mfr=3, Product=4, SerialNumb
er=5
[    5.775636] usb 1-1.2.2: Product: SDDR-189
[    5.775644] usb 1-1.2.2: Manufacturer: SanDisk
[    5.775653] usb 1-1.2.2: SerialNumber: 2008081401127
[    5.776833] usb-storage 1-1.2.2:1.0: USB Mass Storage device detected
[    5.777259] scsi host0: usb-storage 1-1.2.2:1.0
[    5.891559] usb 1-1.2.3: new high-speed USB device number 10 using dwc_otg
[    6.033433] usb 1-1.2.3: New USB device found, idVendor=174c, idProduct=5106
[    6.033452] usb 1-1.2.3: New USB device strings: Mfr=2, Product=3, SerialNumb
er=1
[    6.033462] usb 1-1.2.3: Product: StoreJet Transcend
[    6.033470] usb 1-1.2.3: Manufacturer: StoreJet Transcend
[    6.033479] usb 1-1.2.3: SerialNumber: S318J9AF640309      
[    6.034520] usb-storage 1-1.2.3:1.0: USB Mass Storage device detected
[    6.037715] scsi host1: usb-storage 1-1.2.3:1.0
[    6.151626] usb 1-1.2.4: new high-speed USB device number 11 using dwc_otg
[    6.293675] usb 1-1.2.4: New USB device found, idVendor=174c, idProduct=1351
[    6.293699] usb 1-1.2.4: New USB device strings: Mfr=2, Product=3, SerialNumb
er=1
[    6.293708] usb 1-1.2.4: Product: USB3.1 Device
[    6.293716] usb 1-1.2.4: Manufacturer: Generic
[    6.293724] usb 1-1.2.4: SerialNumber: 12345678912B
[    6.294940] usb-storage 1-1.2.4:1.0: USB Mass Storage device detected
[    6.302478] scsi host2: usb-storage 1-1.2.4:1.0
[    6.375507] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    6.375983] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.562125] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:1
02396k SSFS1020000a
[    6.792853] scsi 0:0:0:0: Direct-Access     SanDisk  mSD SDDR-189     1804 PQ
: 0 ANSI: 0
[    6.796021] scsi 0:0:0:1: Direct-Access     SanDisk  SD  SDDR-189     1804 PQ
: 0 ANSI: 0
[    6.797668] sd 0:0:0:1: [sdb] Attached SCSI removable disk
[    6.798677] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    6.800563] scsi 0:0:0:2: Direct-Access     SanDisk  MSxDSDDR-189     1804 PQ
: 0 ANSI: 0
[    6.802500] scsi 0:0:0:3: Direct-Access     SanDisk  CF  SDDR-189     1804 PQ
: 0 ANSI: 0
[    6.806362] sd 0:0:0:3: [sdd] Attached SCSI removable disk
[    6.807632] sd 0:0:0:2: [sdc] Attached SCSI removable disk
[    6.813533] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    6.813671] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    6.813795] sd 0:0:0:2: Attached scsi generic sg2 type 0
[    6.813937] sd 0:0:0:3: Attached scsi generic sg3 type 0
[    7.118476] scsi 1:0:0:0: Direct-Access     StoreJet Transcend        0    PQ
: 0 ANSI: 6
[    7.119478] sd 1:0:0:0: [sde] 1953525168 512-byte logical blocks: (1.00 TB/93
2 GiB)1020000a
[    7.119507] sd 1:0:0:0: Attached scsi generic sg4 type 01020000a
[    7.119920] sd 1:0:0:0: [sde] Write Protect is off
[    7.119932] sd 1:0:0:0: [sde] Mode Sense: 43 00 00 00
[    7.120384] sd 1:0:0:0: [sde] Write cache: enabled, read cache: enabled, does
n't support DPO or FUA
[    7.155440]  sde: sde1
[    7.157540] sd 1:0:0:0: [sde] Attached SCSI disk
[    7.352612] scsi 2:0:0:0: Direct-Access     KINGSTON  SUV400S37240G   0    PQ
: 0 ANSI: 6
[    7.353176] sd 2:0:0:0: Attached scsi generic sg5 type 0
[    7.353521] sd 2:0:0:0: [sdf] 468862128 512-byte logical blocks: (240 GB/224 
GiB)
[    7.353977] sd 2:0:0:0: [sdf] Write Protect is off
[    7.353983] sd 2:0:0:0: [sdf] Mode Sense: 43 00 00 00
[    7.354394] sd 2:0:0:0: [sdf] Write cache: enabled, read cache: enabled, does
n't support DPO or FUA
[    7.356243]  sdf: sdf1 sdf2
[    7.358029] sd 2:0:0:0: [sdf] Attached SCSI disk
[    9.282218] Bluetooth: Core ver 2.22
[    9.282313] NET: Registered protocol family 31
[    9.282320] Bluetooth: HCI device and connection manager initialized
[    9.282342] Bluetooth: HCI socket layer initialized
[    9.282356] Bluetooth: L2CAP socket layer initialized
[    9.282390] Bluetooth: SCO socket layer initialized
[    9.303527] Bluetooth: HCI UART driver ver 2.3
[    9.303543] Bluetooth: HCI UART protocol H4 registered
[    9.303551] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    9.303760] Bluetooth: HCI UART protocol Broadcom registered
[    9.478069] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.478080] Bluetooth: BNEP filters: protocol multicast
[    9.478100] Bluetooth: BNEP socket layer initialized
[    9.622640] Bluetooth: RFCOMM TTY layer initialized
[    9.622670] Bluetooth: RFCOMM socket layer initialized
[    9.622695] Bluetooth: RFCOMM ver 1.11
[   10.543219] fuse init (API version 7.26)
[   13.612073] EXT4-fs (sdf2): mounted filesystem with ordered data mode. Opts: 
(null)Filesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  4.9G   24G  18% /
devtmpfs        460M     0  460M   0% /dev
tmpfs           464M     0  464M   0% /dev/shm
tmpfs           464M   13M  452M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   22M   21M  52% /boot
tmpfs            93M     0   93M   0% /run/user/1000
/dev/sdf2       4.4G  3.9G  233M  95% /media/pi/rootfs
/dev/sdf1        43M   22M   21M  51% /media/pi/boot
/dev/sde1       932G   13G  919G   2% /media/pi/PI3_HD_2018
[   22.655879] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   22.655912] Bluetooth: HIDP socket layer initialized
[   22.659999] hid-generic 0005:045E:0700.0001: unknown main item tag 0x0
[   22.660420] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/platfo
rm/soc/3f201000.serial/tty/ttyAMA0/hci0/hci0:11/0005:045E:0700.0001/input/input0
[   22.664856] hid-generic 0005:045E:0700.0001: input,hidraw0: BLUETOOTH HID v1.
00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on b8:27:eb:ca:d9:f3
[   36.717023] hid-generic 0005:046D:B330.0002: unknown main item tag 0x0
[   36.717804] input: Logitech Keyboard K480 as /devices/platform/soc/3f201000.s
erial/tty/ttyAMA0/hci0/hci0:12/0005:046D:B330.0002/input/input1
[   36.720519] hid-generic 0005:046D:B330.0002: input,hidraw1: BLUETOOTH HID v28
.00 Keyboard [Logitech Keyboard K480] on b8:27:eb:ca:d9:f3

<e>
</e></CODE></r>
So the output from dmesg should give someone who knows what they are doing maybe half-a-clue what my Pi is doing and why it will not boot from the SSD?

NEXT:
An article gave the following tidbit that uses vcgencmd command that is undocumented on my Pi but produces output that may be meaningful to those who have been here before ...

Code: Select all

{{ $ vcgencmd otp_dump | grep 17: This queries the hardware registers for the boot mode. It will print a number other than 0x3020000a . Next, edit /boot/config.txt and at the end of the file insert this line: program_usb_boot_mode=1 When the Rapberry Pi is rebooted, this line rewrites the register queried above so that now the command should output: $ vcgencmd otp_dump | grep 17: 17:3020000a This enables the USB Mass Storage Device boot mode on that Raspberry Pi. From now on, that particular machine will boot either from SD card or USB MSD. }}
This command on my Pi Produced ...

[email protected]:~ $ vcgencmd
[email protected]:~ $ man vcgencmd
No manual entry for vcgencmd
See 'man 7 undocumented' for help when manual pages are not available.
[email protected]:~ $ vcgencmd otp_dump | grep 17:
17:1020000a
[email protected]:~ $

So, not smok'n anything and a bewildered-puzzled feeling in my grey-matter I hope someone will see this and make enough sense of it to give me some advice as to "WHAT?" next.



Thanks in advance for giving me the clues I need to proceed.
regards ...

PS -- got stuck in "Drafts" and could edit and save. By accident/Mystery I clicked, smiled, gave a "symbol" and I got back here. How do I gracefully exit drafts and get back here to preview and submit??? Now my internet connection is flaky so I have to submit. Hope I got all the corrections made ...

Please can you remove the erroneous HTML Tags you manually inseted, it makes your diatribes difficult to comprehend.


On hardware with x86 CPU Architecture either Windows NT or Mac OSX use Etcher to both unzip and create a bootable USB Hard Drive from the latest "Raspbian Stretch with Desktop" .zip download:

https://www.raspberrypi.org/downloads/raspbian/
Adieu

fbe
Posts: 325
Joined: Thu Aug 17, 2017 9:08 pm

Re: SSD Boot Process

Sat Aug 18, 2018 10:09 pm

JPICentral wrote:
Sat Aug 18, 2018 8:58 pm

Code: Select all

[email protected]:~ $ dmesg | more
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.52-v7+ ([email protected]9333) (gcc version 4.9.3
 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1123 SMP Wed Jun 27 17:35:49 B
ST 2018
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio
n cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
...
This indicates that you have a Raspberry Pi 3B. A Raspberry Pi 3B+ would appear with

Code: Select all

[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Follow these instructions: https://www.raspberrypi.org/documentati ... des/msd.md

JPICentral
Posts: 33
Joined: Wed Jul 18, 2018 3:22 am
Location: Almost in the Mojave Desert

Re: SSD Boot Process

Sun Aug 19, 2018 3:52 am

First and foremost, "What can I do? Can the 3B be altered to boot from a SSD? If so, how do I get this accomplished since I apparently do not have the luxury of the 3B+ I thought I bought."

For one person, ... Here it is ... Where are you looking in the output (line) that provides the answer you seek? I bought two (2) more Pi's that are supposed to also be 3B+. I would like to check them.

BTW, I acquire and collect stuff that should not be. Guess my pi is going to fit the mold. Shucks, I thought I might have escaped the destiny of this for once -- guess not!

For the other person ... It goes to prove there is a sucker born every minute that will fit the criteria with disposable $'s cause they are to dumb to know. So much for Canakit and their sales on amazon.com indicating it was a 3B+ -- I fit like a glove on this one!

For the person asking,"Please can you remove the erroneous HTML Tags you manually inserted, it makes your diatribes difficult to comprehend."

You are asking the person who could not gracefully exit "edit" to go back and fix something that I haven't a clue about. Let's be serious now -- I am a beginner posting in the Beginner Forum learning as I go. The chances of the improvement requested are far less than the chance of making a bigger mess especially with a flaky internet connection. Please accept my apology instead. I think we will both be much better off in the long run? BTW, I do know what, "diatribe" means - that wasn't very nice to say ...

Code: Select all

[email protected]:~ $ cat /proc/cpuinfo
processor	: 0
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 1
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 2
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv[/code]3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

Hardware : BCM2835
Revision : a02082
Serial : 0000000015607359
[email protected]:~ $ ^C
[email protected]:~ $ [/code]
[/code]

What can I do? Can the 3B be altered to boot from a SSD? If so, how do I get this accomplished since I apparently do not have the luxury of the 3B+ I thought I bought.

User avatar
rpdom
Posts: 12741
Joined: Sun May 06, 2012 5:17 am
Location: Ankh-Morpork

Re: SSD Boot Process

Sun Aug 19, 2018 5:24 am

JPICentral wrote:
Sun Aug 19, 2018 3:52 am
Can the 3B be altered to boot from a SSD?
Yes. That is documented in the official documentation
Basically you put the line

Code: Select all

program_usb_boot_mode=1
in /boot/config.txt on an SD card. You then need to boot from that card once only, and that sets the boot flag permanently the same as the 3B+ is by default. You don't even need to do a full Raspbian install, just bootcode.bin and config.txt on the card is enough to set the flag (ok, the rest of the boot will fail after that point, but its work here is finished).

LTolledo
Posts: 533
Joined: Sat Mar 17, 2018 7:29 am

Re: SSD Boot Process

Sun Aug 19, 2018 5:57 am

Oh, sorry I was not able to catch your RPi's model number from the dmesg output you posted. So it is actually a RPi3B. not a RPi3B+.

I second rpdom's recommendation on how to make your RPi3B boot from USB.
That same procedure is also what I used to make several of my RPi3Bs boot from USB Flash/SSD/HDD. I even got lucky with my one and only RPi2B.

Just take it easy and Good luck!
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

JPICentral
Posts: 33
Joined: Wed Jul 18, 2018 3:22 am
Location: Almost in the Mojave Desert

Re: SSD Boot Process

Sun Aug 19, 2018 6:21 am

The several suggestions: https://www.raspberrypi.org/documentati ... des/msd.md Was Excellent. Thanks.

Now to remember to remove the entry on the SDHC card ...

Lost internet connection and lost my posting. In brief ... Got a Segate USB drive working on the Pi B (fka the implied B+) when directly connected. It doesn't work, as desired, connected to the powered hub. The Kingston SSD is "sorta" seen and causes a cycle of berries and the message resized root file system rebooting in 5 sec which never happens -- the cycle continues until power is removed.

Might be the enclosure I bought at Fry's is lengthening the access time for the Pi to get to the SSD?

Now, about making the drive the size it can be: I am not acquainted with "doing" partitions. Then the next piece is which of the many articles is the one to use to get the results that work ! There is this one from a person in AZ that took a lot of time to detail partitioning steps ( see http://www.desert-home.com/ ) Is this what I should be doing? Suggestions would be appreciated.

Thank you!

User avatar
rpdom
Posts: 12741
Joined: Sun May 06, 2012 5:17 am
Location: Ankh-Morpork

Re: SSD Boot Process

Sun Aug 19, 2018 8:12 am

Booting more than once from the SD card will not break anything. The boot flag is already set, so the option has no effect.

fruitoftheloom
Posts: 17288
Joined: Tue Mar 25, 2014 12:40 pm

Re: SSD Boot Process

Sun Aug 19, 2018 9:31 am

JPICentral wrote:
Sun Aug 19, 2018 6:21 am
The several suggestions: https://www.raspberrypi.org/documentati ... des/msd.md Was Excellent. Thanks.

Now to remember to remove the entry on the SDHC card ...

Lost internet connection and lost my posting. In brief ... Got a Segate USB drive working on the Pi B (fka the implied B+) when directly connected. It doesn't work, as desired, connected to the powered hub. The Kingston SSD is "sorta" seen and causes a cycle of berries and the message resized root file system rebooting in 5 sec which never happens -- the cycle continues until power is removed.

Might be the enclosure I bought at Fry's is lengthening the access time for the Pi to get to the SSD?

Now, about making the drive the size it can be: I am not acquainted with "doing" partitions. Then the next piece is which of the many articles is the one to use to get the results that work ! There is this one from a person in AZ that took a lot of time to detail partitioning steps ( see http://www.desert-home.com/ ) Is this what I should be doing? Suggestions would be appreciated.

Thank you!

You appear to be over-complicating the situation, please try a USB Flash Drive first and foremost as that will remove the USB Hub & USB-SATA Adaptor from the situation.

The Canakit Kit should have a decent Power Supply which will be adequate for powering USB Flash Drive, USB Keyboard and USB Mouse plugged directly into your RPi 3B:

https://www.raspberrypi.org/documentati ... des/msd.md



If you can then successfully boot from USB Flash Drive you can introduce the USB-SATA Adaptor / SSD Drive and maybe the USB Hub to see if they are causing any issues.



Regards not getting the RPi model you paid for, would ask Amazon / Canakit for a replacement.......


.
Adieu

User avatar
HawaiianPi
Posts: 2659
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: SSD Boot Process

Mon Aug 20, 2018 12:52 am

The bootloader in the Raspberry Pi 3B(+) SoC is small and simple, due to limited space for the code. What that means is, it's not 100% compatible with all USB mass storage devices. It will work with many, but there will be some that just will not boot, and others that will partially work (boot okay, but not reboot). The bootloader in the newer 3B+ is improved over the 3B model, but still not 100% compatible.

Before we get into specific details, I'd just like to point out that booting from a USB device will be SLOWER than booting from a fast micro-SD card. I don't believe there is any way around that, because the Pi powers up and accesses the SD card slot before the USB ports (based on my observations). Once the system is booted, I/O operations can be faster from SSD, but the difference may not be noticeable compared to an "A1" rated micro-SD card. If you do heavy input/output (database, content creation, large code compiles) then you should see some performance boost due to higher IOPS and better random I/O performance from SSD.

However, if your storage needs are moderate, I suggest booting from an "A1" rated micro-SD card (they are fast, with no worries about compatibility, power, or time to get ready).

For those who need 128GB or more for storage, using an SSD is not only practical, it may even cost less than a comparably sized A1 micro-SD card (128GB seems to be the convergence point where A1 micro SD and SSD are close to the same price, and in larger sizes the SSD could cost significantly less).

Mechanical (spinning rust) hard drives are still the king of the price-per-GB hill, but due to their power requirements and long spin-up times they can be more trouble that they're worth as boot drives (it may be more practical to use them for storage after booting from SD card). It does work for some, but there are lots of posts here from others who have had nothing but trouble trying to go that route.

Now that we got all that out of the way...


USB boot from SSD
I have tried both my Pi3B and newer 3B+ with several SSD models and SATA-USB adapters, and in general I have had good luck.

Best inexpensive adapter I have found is the ELUTENG USB3 to SATA III Cable, which is currently selling for a mere $6.99 on Amazon (USA).
Image
(picture is link)

I like the short cable, and I have yet to find an SSD that will not boot with this adapter.
Image
One of my older Pi3B computers that boots from a Silicon power A55 128GB SSD with the ELUTENG adapter (in an open style JBTek case).

Another one I have had good luck with is the Sabrent USB 3.0 to SSD / 2.5-Inch SATA Hard Drive Adapter.
Image
(picture is link)

The Sabrent adapter has a longer cable and an activity LED, so if either or both of those are desirable features, this is the one to get. It's available in a few different versions now, but the one I use is the cheapest USB 3.0 model ($8.39 at post time).

SSD models I have tested:
  • MyDigitalSSD Super Boot 2 mSATA (128GB)
  • Silicon Power model A55 2.5 inch (128/256GB)
  • Samsung EVO850 mSATA (500GB)
  • I *think* I also tested a Crucial MX500 2.5 inch (500GB), but I don't have that in my notes, so not 100% sure :?
With the ELUTENG adapter all of those worked correctly (boot and reboot) when powered directly from my Pi3B(+) with a good PSU.

For the mSATA form-factor drives I also tested a tiny ELUTENG mSATA external enclosure, which worked great as well.
Image
My Pi3B+ in a Flirc aluminum alloy heatsink case booting from an mSATA SSD in the ELUTENG enclosure (picture is link).

The ELUTENG USB3-SATA3 2.5 inch SSD/HDD adapter cable uses the AS Media ASM1153 controller chip.
The ELUTENG USB 3.0 mSATA enclosure uses the JMicron JMS578 controller chip.

I also have a tiny PC Parts 239 USB 3.0 external mSATA enclosure that worked well, but that seems to be a discontinued model now. Too bad, because I made a ridiculously fast USB flash drive out of it and my Samsung EVO850 500GB mSATA SSD. Seriously, on a USB 3.0 port no conventional flash drive even comes close! It stomps my Patriot Supersonic Rage 2 Series flash drive, which is suppose to be one of the fastest.

Cheapest adapter I have tested is one from a vendor named Grandey, which was $5.75 at the time of my purchase. It has since gone up to over $7, so the ELUTENG is not only cheaper, it's also better (the Grandey adapter didn't like my Samsung SSD, but worked fine with others).
Last edited by HawaiianPi on Tue Aug 21, 2018 10:08 pm, edited 1 time in total.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

JPICentral
Posts: 33
Joined: Wed Jul 18, 2018 3:22 am
Location: Almost in the Mojave Desert

Re: SSD Boot Process

Tue Aug 21, 2018 10:02 am

20180821 at 0127 (TZ=P) Appreciate the responses and the helpful information. I wish I could return the Pi - It is beyond the number-of-day's limit for that. So, ... ! The adapters sound like much better choices than the case from Fry's in the junk box. I think it is good that I neither care about boot speed or exceptional processing speed - I can't type all that well; and, I do not read very fast either so my Pi-and-me are, at this time are "Good!"

Except for the Pi, the pieces and parts used are from a box of parts of various prior projects:

(USED) when Bluetooth is NOT working: HP USB Keyboard of unknown origin / Microsoft InteliMouse Optical USB and PS/2 Compatible

(USED) when Bluetooth IS working: Logitech K480 Bluetooth keyboard / Microsoft Bluetooth Notebook Mouse 5000

Note on the K480. I found when attempting to pair, an "ENTER" must follow the last number of the code ASAP to avoid timeout.

Pi 3B

Samsung EVO Select 32Gb micro SDHC Class 10 UH1 1FHD

Seagate 2tb Backup Plus Portable Slim (very inexpensive and obviously over-kill; however, it works )

Kingston 640Gb SSD (on sale at Fry's when obtained) (a better choice if I can get it working)

4-Port USB-3 Powered Hub (not impressed but stuck with it)

Transcend 1tb HD used to save all the information being collected that I am reading to learn about the Pi (It was old and hated FAT32 Format) (do'n what I need done but would like to remove it from the component list)

LG 24MP60QV Monitor (it worked once a wall-wart was located) eventually I'll downsize to something more Pi like when I find it.

BOOT cycle ...
Just the monitor and the Segate drive and I have "boot". Anything else and there is no "green" light after some 6 to 10 sec. both stay "red" and no boot

Once the boot cycle completes, the powered hub is inserted into the Pi. The hub handles powering a speaker system, a card reader/writer, and the Transcend drive.

The only problems I have had with this setup is shutdown. For the life of me I was unable to find how to eject the Transcend drive. Then I saw the booted-triangle in the upper right and clicked it for grins-and-giggles. I got my answer . The Transcend can now be ejected for shutdown and anytime I want to change peripheral configuration.

Another issue. The Bluetooth devices are powered by rechargeable cells which deplete at unexpected moments. The K480 keyboard begins inserting incorrect letters for the ones typed; and, at the extreme end-of-cell-depletion a letter will begin displaying in a long continuous row-after-row (I've not see that before).
I have been able to create SDHC card backups for all current and future screw-ups so I am well prepared for this eventuality? The back up of the Segate is of concern to me if I have a lot of material stored (I would eventually like to re-purpose the Transcend with the preferred Kingston SSD being both the boot and the store drive.

I am beginning to think the 2.5A wall wart provided in the kit may not be up to specs if the Pi 3B takes, per one article, a little over 1 amp and the Segate shows 1A on its tag. There should be some juice left. I'am looking for an Amp-meter to learn if maybe some of the strange things might be related to an inadequate power source?

I think my direction should be acquiring maybe one of the mentioned USB-to_SATA adapters from amazon that might allow me to incorporate the Kingston drive and move away from the Segate for boot and the Transcend for document storage?

Even more important is partitioning the Segate to make it less like an SDHC card and more like a HD that has a lot of space I think I need. Once I get the Kingston drive working, I will have more partitioning practice since it will need this done to it, too.

Here is my question: After looking at "man parted" I'm think'n that I am going to have a lot of research time to determine how to properly partition whatever device I use. So far, I have not located any article that is clear enough for me to continue at this moment. I have seen suggestions of ext4, FAT 16, FAT32 and no NTFS and probably other restrictions or partition-suggestions.

Would someone point me in the right direction that gives me how to word-the-search so that I can obtain proper information on the structure of the Pi's storage device and the type and ideal size (maybe percentage of available total space) of each partition by format.

I hope I have written the information correctly in the request?

Thank you.

JPICentral
Posts: 33
Joined: Wed Jul 18, 2018 3:22 am
Location: Almost in the Mojave Desert

Re: SSD Boot Process

Tue Aug 21, 2018 10:11 am

Thanks for taking the time to prepare this great information and the included pictures. How did you get the pictures included/inserted. I see them being very valuable when trying to explain/show what is being written. Again, great! Appreciated. Will take a look at amazon for the adapters. It will save me a few $'s and limit the trial and mistake approach I am sorta using with suggestion from those kind enough to help me. regards and thanks again ...
HawaiianPi wrote:
Mon Aug 20, 2018 12:52 am
The bootloader in the Raspberr Pi 3B(+) SoC is small and simple, due to limited space for the code. What that means is, it's not 100% compatible with all USB mass storage devices. It will work with many, but there will be some that just will not boot, and others that will partially work (boot okay, but not reboot). The bootloader in the newer 3B+ is improved over the 3B model, but still not 100% compatible.

Before we get into specific details, I'd just like to point out that booting from a USB device will be SLOWER than booting from a fast micro-SD card. I don't believe there is any way around that, because the Pi powers up and accesses the SD card slot before the USB ports (based on my observations). Once the system is booted, I/O operations can be faster from SSD, but the difference may not be noticeable compared to an "A1" rated micro-SD card. If you do heavy input/output (database, content creation, large code compiles) then you should see some performance boost due to higher IOPS and better random I/O performance from SSD.

However, if your storage needs are moderate, I suggest booting from an "A1" rated micro-SD card (they are fast, with no worries about compatibility, power, or time to get ready).

For those who need 128GB or more for storage, using an SSD is not only practical, it may even cost less than a comparably sized A1 micro-SD card (128GB seems to be the convergence point where A1 micro SD and SSD are close to the same price, and in larger sizes the SSD could cost significantly less).

Mechanical (spinning rust) hard drives are still the king of the price-per-GB hill, but due to their power requirements and long spin-up times they can be more trouble that they're worth as boot drives (it may be more practical to use them for storage after booting from SD card). It does work for some, but there are lots of posts here from others who have had nothing but trouble trying to go that route.

Now that we got all that out of the way...


USB boot from SSD
I have tried both my Pi3B and newer 3B+ with several SSD models and SATA-USB adapters, and in general I have had good luck.

Best inexpensive adapter I have found is the ELUTENG USB3 to SATA III Cable, which is currently selling for a mere $6.99 on Amazon (USA).
Image
(picture is link)

I like the short cable, and I have yet to find an SSD that will not boot with this adapter.
Image
One of my older Pi3B computers that boots from a Silicon power A55 128GB SSD with the ELUTENG adapter (in an open style JBTek case).

Another one I have had good luck with is the Sabrent USB 3.0 to SSD / 2.5-Inch SATA Hard Drive Adapter.
Image
(picture is link)

The Sabrent adapter has a longer cable and an activity LED, so if either or both of those are desirable features, this is the one to get. It's available in a few different versions now, but the one I use is the cheapest USB 3.0 model ($8.39 at post time).

SSD models I have tested:
  • MyDigitalSSD Super Boot 2 mSATA (128GB)
  • Silicon Power model A55 2.5 inch (128/256GB)
  • Samsung EVO850 mSATA (500GB)
  • I *think* I also tested a Crucial MX500 2.5 inch (500GB), but I don't have that in my notes, so not 100% sure :?
With the ELUTENG adapter all of those worked correctly (boot and reboot) when powered directly from my Pi3B(+) with a good PSU.

For the mSATA form-factor drives I also tested a tiny ELUTENG mSATA external enclosure, which worked great as well.
Image
My Pi3B+ in a Flirc aluminum alloy heatsink case booting from an mSATA SSD in the ELUTENG enclosure (picture is link).

The ELUTENG USB3-SATA3 2.5 inch SSD/HDD adapter cable uses the AS Media ASM1153 controller chip.
The ELUTENG USB 3.0 mSATA enclosure uses the JMicron JMS578 controller chip.

I also have a tiny PC Parts 239 USB 3.0 external mSATA enclosure that worked well, but that seems to be a discontinued model now. Too bad, because I made a ridiculously fast USB flash drive out of it and my Samsung EVO850 500GB mSATA SSD. Seriously, on a USB 3.0 port no conventional flash drive even comes close! It stomps my Patriot Supersonic Rage 2 Series flash drive, which is suppose to be one of the fastest.

Cheapest adapter I have tested is one from a vendor named Grandey, which was $5.75 at the time of my purchase. It has since gone up to over $7, so the ELUTENG is not only cheaper, it's also better (the Grandey adapter didn't like my Samsung SSD, but worked fine with others).

k-pi
Posts: 532
Joined: Sun Feb 12, 2017 1:46 pm
Location: Upper Hale, Surrey, UK.

Re: SSD Boot Process

Tue Aug 21, 2018 10:41 am

Sizing partitions, general, Linux systems.

I have always created a root/system partition the size of an installed distro plus a bit extra for any more programs that I might add, usually in the region of 5~8GB.

Add a swap partition, If you want, not always necessary - (on laptops it needs to be equal to the amount of ram, so that you can suspend/hibernate).

Then the rest is for your /home where all your personal files reside. (Not forgetting to back up the contents of this partition occasionally.)

Basically. that's all there is to it - however, the RPi copy program & installer will take over the whole disk. :o

You will probably have to create three partitions, a small dos one first for the RPi boot code, first on disk, then copy the boot code to it, then the system partition, copying all the files over onto the disk partition yourself, & finally your home partition - & you will likely need to alter the /etc/fstab file by hand so that each partition is mounted correctly.

Another option may be to install as normal, let it take over the whole disk, then shrink the partition, & add your own /home partition, but you will still have to alter the /etc/fstab manually.

User avatar
HawaiianPi
Posts: 2659
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: SSD Boot Process

Tue Aug 21, 2018 8:59 pm

JPICentral wrote:
Tue Aug 21, 2018 10:02 am
After looking at "man parted" I'm think'n that I am going to have a lot of research time to determine how to properly partition whatever device I use. So far, I have not located any article that is clear enough for me to continue at this moment. I have seen suggestions of ext4, FAT 16, FAT32 and no NTFS and probably other restrictions or partition-suggestions.
If you are using the Desktop version of Raspbian, install GParted for partitioning drives.

The following command in a terminal will install gparted and support for exFAT and NTFS (common Windows file systems).

Code: Select all

sudo apt update && sudo apt install gparted exfat-fuse exfat-utils ntfs-3g
GParted is a graphical user interface for parted.

If you only plan on using the HDD/SSD with your Pi, format them with the Linux ext4 file system. If you want to use the drives with both your Pi and a Windows computer, use NTFS or exFAT (NTFS is best for hard drive or SSD, while exFAT would be used for USB flash drives). For use as a storage drive you'll only need one partition.

Note that the adapters I recommended are for bare drives (just the drive with no protective enclosure). If you want an external enclosure, just about any one should work as a storage drive. If you want advice about an enclosure that works as a USB boot drive, let me know and I'll see if I have any I can recommend.

To insert pictures in a post click the little picture icon above the edit window (9th from the left).
insert-picture-icon.jpg
insert-picture-icon.jpg (8.12 KiB) Viewed 249 times
You'll also need to host your pictures somewhere online. There are a number of picture hosting web sites, but I don't know what the popular ones are now since I don't use them (I use other more complicated tricks).

You can also add a picture as an attachment to the post, but that can be a bit wonky sometimes.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

JPICentral
Posts: 33
Joined: Wed Jul 18, 2018 3:22 am
Location: Almost in the Mojave Desert

Re: SSD Boot Process

Fri Aug 24, 2018 4:34 am

20180823 2118(P) I'll start with the partitioning challenge before I get to the pictures.

I was thinking, maybe it would be a benefit, to summarize the steps and commands that everyone has shared so it would be in one place for another person to find all the information in a one-stop "read?" Then again, maybe Pi folks prefer the challenge of the hunt -- Just think'n outloud!

Now to work. I'm running low on connect time so I may not be able to do much or give replies to helpful posts until I can snag some "free" time or I wait until the cycle begins and my "cup of internet-time" refills! Such things of big inconvenience …

On the comment about the adapters. If the adapter will allow the SSD to connect, I'll use Velcro (sp?) to stick the drive to the Pi case (well, it sorta sounds like a plan since I have nothing better at the moment and I think I had best focus on the partitioning and get that working.)

Thanks for the tips/suggestions on the partitioning. I sense I will probably have a whole lot of fun with this activity (grin)! It is a good thing I am about out of bandwidth. I should probably go grab gparted before I am byte-less. I'll have to be exceptionally resourceful; or try to read the small font on my phone if it should choose to cooperate and connect me to this awesome website with tremendously helpful people!

Has anyone tried to get a full 2-terrabytes connected to a Pi with it working (well working correctly whatever that should mean?).

regards, and thanks again!

LTolledo
Posts: 533
Joined: Sat Mar 17, 2018 7:29 am

Re: SSD Boot Process

Fri Aug 24, 2018 9:22 am

JPICentral wrote:
Fri Aug 24, 2018 4:34 am
Has anyone tried to get a full 2-terrabytes connected to a Pi with it working (well working correctly whatever that should mean?).
For your reference I have a Raspberry Pi 1 Model B+ with
a. 16GB Sandisk CruzerFit USB Thumbdrive as boot
b. 2.5" 2TB Seagate Barracuda HDD, NTFS formatted single partition
c. 2.5" 1TB Marshall HDD, NTFS formatted single partition

Code: Select all

:~ $ lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda       8:0    1  14.6G  0 disk 
├─sda1    8:1    1  43.2M  0 part /boot
└─sda2    8:2    1  14.6G  0 part /
sdb       8:16   0   1.8T  0 disk 
└─sdb1    8:17   0   1.8T  0 part /media/pi/USB2TB
sdc       8:32   0 931.5G  0 disk 
└─sdc1    8:33   0 931.5G  0 part /media/pi/M1TB
mmcblk0 179:0    0   1.9G  0 disk /media/pi/BOOT
and its uptime as of this post is

Code: Select all

:~ $ uptime
 18:18:36 up 8 days, 12:50,  2 users,  load average: 3.22, 3.29, 2.00
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

Return to “Beginners”

Who is online

Users browsing this forum: Andyroo and 27 guests