Pogoplug Pro: Two drive bootup issue

Hi all,

TL;DR I can’t boot with 2 drives, one is the system drive, and one is a 2.5” in an enclosure.

I’m back with a different problem than last time. bodhi was gracious enough to assist last time and the help was much appreciated.

My new issue is that I am now working with a Pogoplug Pro. I have installed Debian and its working fine. The WiFi works, if I wanted to use it, but I have it wired for now. I have it hooked up to be a LMS client / server.

However, and here is where the problem begins, I am unable to boot with two USB drives on the plug. When I do attempt to boot up, I get one of two different situations. I’ll explain below.

Let me first explain what I’ve tired. I’ve attempted to follow the following threads:

http://forum.doozan.com/read.php?2,5233,5957

& http://forum.doozan.com/read.php?2,7185

I have used a regular mounting, the LABEL mounting (where in I label a drive and use that label in the fstab file) and I’ve also tried to use the UUID method for identifying a drive as well.

I thought that the issue was that I was using a USB 3.0 enclosure for a 2.5” drive to hold the music that I wanted to auto mount on boot. When I used that enclosure, and I rebooted the plug, I was also pinging my plug from a Windows machine. It would alternate between these two responses when I attempted to boot:

Request timed out.
Reply from 192.168.1.35: Destination host unreachable.

The green LED would occasionally flash when I was in the boot process. But the Pogoplug never came up no matter how long I waited.

I’ve heard there can be issues with 3.0 devices, so I went out and bought a 2.0 enclosure. I might add, my system drive is a Sandisk Cruiser Fit (USB 2.0)

So after I had installed the drive into the 2.0 enclosure, I was getting a different issue. Now all I got was

Reply from 192.168.1.35: Destination host unreachable.

Over and over. Also, not only did the greed LED flash, an amber one would flash. I counted the Amber one and it flashed 6 times, before going out and green came back.

Again, I’m thankful to anyone who might want to assist me in my discovery of a solution.

I know that with either enclosure, the drive was getting enough power, At least I assume so. I say that because I was able to mount it normally and then travel through the directory path and see the files I’d copied over.

I’m open to suggestion as to what I might try next. Thanks again!

mxhdrm,

> I have used a regular mounting, the LABEL mounting
> (where in I label a drive and use that label in
> the fstab file) and I’ve also tried to use the
> UUID method for identifying a drive as well.

fstab is not a good way to ensure booting the correct drive. The foolproof way is using kernel parameters, which we specify in u-boot envs.


> Over and over. Also, not only did the greed LED
> flash, an amber one would flash. I counted the
> Amber one and it flashed 6 times, before going out
> and green came back.

The amber color flashing indicated that u-boot could not find one of the kernel files (uImage, uInitrd, or DTB).

Boot with only the system drive. Once you are inside Debian, it is much easier to see what went wrong and setting it up correctly. After logging in, get these info:

e2label /dev/sda1
mount
fw_printenv

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello bodhi,

When I originally started to look for what drive boots at boot up, I had (incorrectly) assumed I should do it through fstab.

But anyway, contained below is the output for the specified commands.




Output for :

e2label /dev/sda1 :

ROOTFS

mount :

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=14958,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=12180k,mode=755)
/dev/sda1 on / type ext3 (rw,noatime,errors=continue,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=24340k)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)

fw_printenv : 

autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootdelay=10
console=console=ttyS0,115200n8
ethact=mii0
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
stderr=serial
stdin=serial
stdout=serial
usb_device=0:1
if_netconsole=ping $serverip
preboot_nc=run if_netconsole start_netconsole
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
uinitrd_addr=0x60e00000
uimage_addr=0x60500000
dtb_addr=0x62c00000
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
bootcmd=run dt_bootcmd_usb
ethaddr=00:25:31:01:c6:2a
dt_load_dtb=ext2load usb 0:1 $dtb_addr $fdt_file
preboot=run preboot_nc
ipaddr=192.168.1.12
serverip=192.168.1.11
fdt_file=/boot/dts/ox820-pogoplug-pro.dtb
usb_init=run usb_scan ; setenv usb_root LABEL=ROOTFS

And thanks for the additional help bodhi.

mxhdrm Wrote:
-------------------------------------------------------
> Hello bodhi,
>
> When I originally started to look for what drive
> boots at boot up, I had (incorrectly) assumed I
> should do it through fstab.
>
> But anyway, contained below is the output for the
> specified commands.
>
>
>
>
> Output for :
>
>

> e2label /dev/sda1 :
> 
> ROOTFS
>

>
>
>

> mount :
> 
> sysfs on /sys type sysfs
> (rw,nosuid,nodev,noexec,relatime)
> proc on /proc type proc
> (rw,nosuid,nodev,noexec,relatime)
> udev on /dev type devtmpfs
> (rw,relatime,size=10240k,nr_inodes=14958,mode=755)
> 
> devpts on /dev/pts type devpts
> (rw,nosuid,noexec,relatime,gid=5,mode=620)
> tmpfs on /run type tmpfs
> (rw,nosuid,noexec,relatime,size=12180k,mode=755)
> /dev/sda1 on / type ext3
> (rw,noatime,errors=continue,barrier=1,data=ordered
> )
> tmpfs on /run/lock type tmpfs
> (rw,nosuid,nodev,noexec,relatime,size=5120k)
> tmpfs on /run/shm type tmpfs
> (rw,nosuid,nodev,noexec,relatime,size=24340k)
> tmpfs on /tmp type tmpfs (rw,relatime)
> rpc_pipefs on /var/lib/nfs/rpc_pipefs type
> rpc_pipefs (rw,relatime)
>

>
>
>

> fw_printenv : 
> 
> autoload=no
> baudrate=115200
> bootargs=console=ttyS0,115200n8
> bootdelay=10
> console=console=ttyS0,115200n8
> ethact=mii0
> mtdids=nand0=41000000.nand
> mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
> stderr=serial
> stdin=serial
> stdout=serial
> usb_device=0:1
> if_netconsole=ping $serverip
> preboot_nc=run if_netconsole start_netconsole
> start_netconsole=setenv ncip $serverip; setenv
> bootdelay 10; setenv stdin nc; setenv stdout nc;
> setenv stderr nc; version
> usb_set_bootargs=setenv bootargs
> console=ttyS0,115200 root=/dev/sda1 rootdelay=10
> uinitrd_addr=0x60e00000
> uimage_addr=0x60500000
> dtb_addr=0x62c00000
> dt_load_initrd=ext2load usb 0:1 $uinitrd_addr
> /boot/uInitrd
> dt_load_uimage=ext2load usb 0:1 $uimage_addr
> /boot/uImage
> dt_bootm=bootm $uimage_addr $uinitrd_addr
> $dtb_addr
> dt_usb_boot=run dt_load_uimage; run
> dt_load_initrd; run dt_load_dtb; run dt_bootm
> dt_usb_bootcmd=run usb_set_bootargs; run
> dt_usb_boot
> dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb
> stop; reset
> bootcmd=run dt_bootcmd_usb
> ethaddr=00:25:31:01:c6:2a
> dt_load_dtb=ext2load usb 0:1 $dtb_addr $fdt_file
> preboot=run preboot_nc
> ipaddr=192.168.1.12
> serverip=192.168.1.11
> fdt_file=/boot/dts/ox820-pogoplug-pro.dtb
> usb_init=run usb_scan ; setenv usb_root
> LABEL=ROOTFS
>

>
> And thanks for the additional help bodhi.

You need a scan disk logic so that the uImage can be loaded from the correct partition:
http://forum.doozan.com/read.php?3,19093

Take a look at the explanation, and if you'd like, list the commands you about to run here so I can look it over.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> You need a scan disk logic so that the uImage can
> be loaded from the correct partition:
> http://forum.doozan.com/read.php?3,19093
>
> Take a look at the explanation, and if you'd like,
> list the commands you about to run here so I can
> look it over.


Hi bodhi,

Alright, so if I’m following correctly, I’ll need to scan the drives to look for the one drive with a uImage on it. I just checked with my Pogoplug (because I wanted to make sure I wasn’t getting it wrong) and yes there is a /boot directory on the boot drive. I also have to make sure I don’t place another “/boot” folder on the other, secondary drive. That’s easy enough.

I also took a look to see the directions that I initially used to get me to where I am today. That being I was here:

http://blog.qnology.com/2015/04/hacking-pogoplug-v3oxnas-proclassic.html

I’ve followed Qui’s guides before, but I note here that the uboot file that he is using (Which I used) is that of 2013.10-tld-4. I know this is beyond the scope of my original question, but do I (or should I, and can I) change the uboot that I was using to be that of the new one? I mean, for security purposes, I wouldn’t mind updating, if there’s any more security to be gained, or if it allows me to use the secondary instructions on the scan. But along the lines of, “If it’s not broke, don’t fix it” I’m comfortable using it the ways it is.

That aside, I see Section “A.1” I’m under the impression that I should install those environment variables into the fw_setenv command?

I follow along for the “A.2” and I read this section :

fw_setenv devices 'usb ide mmc'
fw_setenv device '0:1'
fw_setenv disks '0 1 2 3'
fw_setenv bootdev usb

As telling me that the only devices that may be connected here that are storage drives fall under the category of either a USB drive, and IDE drive or an MMC drive. So my first question is, do I explicitly need the “IDE” section or the “MMC” ones, as they will only be booting with a USB flash drive or USB HD in an enclosure? I’m assuming those are in for other types of devices that use IDE and MMC storage.

The second line I see as what disk / partition the “/boot” folder was found at.
The third being how many disks are there total.
And the fourth being the boot device is a USB drive(?)

That I can understand and can input as well.

My other question turns to the latter portion of “A.2” Which is the scanning script itself. I see the large “scan_disk” command and get that, but it’s the following line that I’m not sure of what to put for the names of “xxx” are. Hopefully it’s just because I’m just slightly confused and not missing the mark entirely.
So what would be an example of valid input for this line:

fw_setenv bootcmd 'run scan_disk; run set_bootargs_xxx; run bootcmd_xxx, reset'

Thanks again!

mxhdrm,

You got everything pretty much figured out already. I'll annotate a few points.

> I’ve followed Qui’s guides before, but I note
> here that the uboot file that he is using (Which I
> used) is that of 2013.10-tld-4. I know this is
> beyond the scope of my original question, but do I
> (or should I, and can I) change the uboot that I
> was using to be that of the new one? I mean, for
> security purposes, I wouldn’t mind updating, if
> there’s any more security to be gained, or if it
> allows me to use the secondary instructions on the
> scan. But along the lines of, “If it’s not
> broke, don’t fix it” I’m comfortable using
> it the ways it is.

Yes Qui's guide was old, so it used my 2013 u-boot release. I've since released 2015 u-boot. The main thing you would gain is the uEnv.txt capability (where you can temporarily modify u-boot envs during boot). And the new default envs image automatically takes care of multiple drives booting problem (which you are having now).


> That aside, I see Section “A.1” I’m under
> the impression that I should install those
> environment variables into the fw_setenv command?
>

Yes, using fw_setenv command to modify envs.

>
> I follow along for the “A.2” and I read this
> section :
>
>

> fw_setenv devices 'usb ide mmc'
> fw_setenv device '0:1'
> fw_setenv disks '0 1 2 3'
> fw_setenv bootdev usb
>

>
> As telling me that the only devices that may be
> connected here that are storage drives fall under
> the category of either a USB drive, and IDE drive
> or an MMC drive. So my first question is, do I
> explicitly need the “IDE” section or the
> “MMC” ones, as they will only be booting with
> a USB flash drive or USB HD in an enclosure? I’m
> assuming those are in for other types of devices
> that use IDE and MMC storage.

Exactly, you only need

fw_setenv devices 'usb'

>
> The second line I see as what disk / partition the
> “/boot” folder was found at.
> The third being how many disks are there total.
> And the fourth being the boot device is a USB
> drive(?)
>
> That I can understand and can input as well.

Yes. So number of disks should be changed if you ever have 6 partitions:

fw_setenv disks '0 1 2 3 4 5'

> My other question turns to the latter portion of
> “A.2” Which is the scanning script itself. I
> see the large “scan_disk” command and get
> that, but it’s the following line that I’m not
> sure of what to put for the names of “xxx”
> are. Hopefully it’s just because I’m just
> slightly confused and not missing the mark
> entirely.
> So what would be an example of valid input for
> this line:
>
>

> fw_setenv bootcmd 'run scan_disk; run
> set_bootargs_xxx; run bootcmd_xxx, reset'
>

>

Since your boot command is

bootcmd=run dt_bootcmd_usb

so you modified bootcmd should be

fw_setenv bootcmd 'run scan_disk; run dt_bootcmd_usb; reset'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> mxhdrm,
> > That aside, I see Section “A.1” I’m under
> > the impression that I should install those
> > environment variables into the fw_setenv
> command?
> >
>
> Yes, using fw_setenv command to modify envs.

So I understand what I need to do now, at least on how to make the multi-drive boot work. However, I'm wondering if I'm installing the environment variables wrong. I've used the fw_setenv command on those individual lines in section A.1 . But I believe I'm missing something important because the shell comes back with, for example, an error that states that "ext2load" is not found. Since I'm not the most familiar with using the fw_setenv, I'm wondering if I've not used the command properly, or if I don't have the correct programs on this device.

What I did was simply place the fw_setenv in front of the first command in section A.1 and that's one of the errors I've received. Am I missing something? Sorry for being so dense, but it's not immediately apparent as to what I've done wrong.


Thanks.

mxhdrm,

> What I did was simply place the fw_setenv in front
> of the first command in section A.1 and that's one
> of the errors I've received. Am I missing
> something?

Note these syntax. There is no equal sign in setting the variable, and the content is placed inside single quotes (in it, there might be embdded equal sign, but it means different thing).

In Linux shell:

fw_setenv bootcmd 'run scan_disk; run dt_bootcmd_usb; reset'

In serial or netconsole at u-boot prompt:

setenv bootcmd 'run scan_disk; run dt_bootcmd_usb; reset'

To see the content of an env.

In Linux shell

fw_printenv bootcmd

And at u-boot prompt

printenv bootcmd

in both cases the output is

bootcmd=run scan_disk; run dt_bootcmd_usb; reset

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

I didn't realize that the A.1 section was an output rather than a strict input for the fw_setenv.

So what I've done is installed the sections and I've attempted to reboot, but I still get the same error, with the amber LED.

I'm pasting in my environmental printout in the hopes that I've entered in something incorrectly.

And I apologize for the delay in updating this issue.

autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootdelay=10
console=console=ttyS0,115200n8
ethact=mii0
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
stderr=serial
stdin=serial
stdout=serial
if_netconsole=ping $serverip
preboot_nc=run if_netconsole start_netconsole
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
uinitrd_addr=0x60e00000
uimage_addr=0x60500000
dtb_addr=0x62c00000
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
ethaddr=00:25:31:01:c6:2a
dt_load_dtb=ext2load usb 0:1 $dtb_addr $fdt_file
preboot=run preboot_nc
ipaddr=192.168.1.12
serverip=192.168.1.11
fdt_file=/boot/dts/ox820-pogoplug-pro.dtb
bootcmd=run scan_disk; run dt_bootcmd_usb; reset
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
devices=usb
device=0:1
disks=0 1 2 3
bootdev=usb
scan_disk=scan_done=0; setenv scan_usb "usb start";  for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if ext2load $dev $disknum:1 0x800000 /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
usb_root=/dev/sda1
usb_init=usb start; setenv usb_root LABEL=rootfs

I do have one question, but I'm sure if it matters though, does the section that says :

disks=0 1 2 3

and this section:

usb_scan_list=1 2 3 4

Are they interrelated in terms of the numbers? As in can they have to be the same numbers, or are they separate sets?

Thanks.

1. My recommendation in general. Your netconsole has already been set up for these IPs:

ipaddr=192.168.1.12
serverip=192.168.1.11

Have you tried to connect netconsole for another Linux box? If you could it would be much easier for you to see the real problem. Of course it is easiest if you have serial console connected. For the Pogo V3, all you need is to have a serial module converter such as the CP2102 we talked about this thread.

2. Problem

usb_scan_list and disks are not related. These are from 2 different approaches list in the instruction (A.1 and A.2). A.1 was Jeff's implementation for the old u-boot. A.2 is what I wrote while developing new u-boots.

Note the scandisk

scan_disk=scan_done=0; setenv scan_usb "usb start";  for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if ext2load $dev $disknum:1 0x800000 /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done

The scandisk detects bootdev and disknum. So the code below msut be changed to use that.

dt_load_initrd=ext2load $bootdev  $device $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load $bootdev $device $uimage_addr /boot/uImage
dt_load_dtb=ext2load $bootdev  $device $dtb_addr $fdt_file

3. I know usually it's wise not upgrading to newer u-boot if not necessary. However, this is the case where if you had upgraded to new u-boot (and therefore the new default envs) then you would not have this mutidrive booting problem! But,... unbrick the Pogo V3 from a bad flash is cumbersome (need to connect SATA), so I would let you decide which is best.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> 1. My recommendation in general. Your netconsole
> has already been set up for these IPs:
>

> ipaddr=192.168.1.12
> serverip=192.168.1.11
>

That is true, I had set them up on those addresses, but I changed the troubled Pogoplug to be a different one and then I ran the netconsole and received this output from it:

U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS                       0
Scan device usb
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... ERROR: Invalid USB EP length (9)
ERROR: Invalid USB EP length (9)
5 USB Device(s) found
       scanning usb for storage devices... 2 Storage Device(s) found
device usb 0:1
** No partition table - usb 0 **
device usb 1:1
1 bytes read in 177 ms (0 Bytes/s)
Found bootable drive on usb 1
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... ERROR: Invalid USB EP length (9)
ERROR: Invalid USB EP length (9)
5 USB Device(s) found
       scanning usb for storage devices... 2 Storage Device(s) found
4170064 bytes read in 301 ms (13.2 MiB/s)
1973699 bytes read in 298 ms (6.3 MiB/s)
7029 bytes read in 204 ms (33.2 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   Linux-3.18.5-oxnas-tld-1
   Created:      2015-08-29  22:20:00 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4170000 Bytes = 4 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
   Image Name:   initramfs-3.18.5-oxnas-tld-1
   Created:      2015-08-29  22:20:14 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    1973635 Bytes = 1.9 MiB
   Load Address: 60000000
   Entry Point:  60000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
   Booting using the fdt blob at 0x62c00000


Starting kernel ...

It looks like it's doing what I want, and I ran the netconsole with and without the hard disk attached. I received the same "Invalid USB EP length" error both times. However, without the drive, I was able to get into the plug, with it attached, all I get from a ping from Windows is this :

Reply from 192.168.1.35: Destination host unreachable.

And I don't have a serial module converter, currently.


> 2. Problem
>
> usb_scan_list and disks are not related. These are
> from 2 different approaches list in the
> instruction (A.1 and A.2). A.1 was Jeff's
> implementation for the old u-boot. A.2 is what I
> wrote while developing new u-boots.

I've altered my environment variables with what you've suggested, which is what allowed me to get to the point where it's somewhat up.



> 3. I know usually it's wise not upgrading to newer
> u-boot if not necessary. However, this is the case
> where if you had upgraded to new u-boot (and
> therefore the new default envs) then you would not
> have this mutidrive booting problem! But,...
> unbrick the Pogo V3 from a bad flash is cumbersome
> (need to connect SATA), so I would let you decide
> which is best.

Well, I didn't look to see how complicated it would be to do the upgrade. I'm assuming someone's asked how to do it before me? If so, I'll give it a shot. I have other Pro's that I would convert as well. And if it fixes the issue, then it might be worthwhile to convert them all. What would be the easiest thing to explain? Because I would rather not get into a situation where it is bricked.

Thanks.

1. Let's get the USB SSD disk info after you plugged in.

dmesg | tail -30
fdisk -l
mount
e2label /dev/sdb1

and then mount the SSD and get

mount
df -h

We might see something here, so no need to install new u-boot yet.


2. To install new u-boot, read the first post of the u-boot thread:

http://forum.doozan.com/read.php?3,16017

Ignore the preamble. You've already run the new u-boot series. You only need to this section to install newer u-boot version:

Quote

Updated 22 Nov 2015

And like I've suggested, to be extra careful, you can preprare your commands as you about to do and I'll take a look.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 06/04/2016 07:28PM by bodhi.

bodhi Wrote:
-------------------------------------------------------
> 1. Let's get the USB SSD disk info after you
> plugged in.

Alright, so here it is.

dmesg | tail -30 

[    4.171783] sd 1:0:0:0: [sda] 15630336 512-byte logical blocks: (8.00 GB/7.45 GiB)
[    4.181071] sd 1:0:0:0: [sda] Write Protect is off
[    4.186109] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00
[    4.187164] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    4.205611]  sda: sda1
[    4.213166] sd 1:0:0:0: [sda] Attached SCSI removable disk
[   12.760663] EXT3-fs (sda1): mounted filesystem with ordered data mode
[   12.769815] kjournald starting.  Commit interval 5 seconds
[   14.506833] udevd[270]: starting version 175
[   15.663795] usbcore: registered new interface driver snd-usb-audio
[   17.049625] random: nonblocking pool is initialized
[   17.897400] EXT3-fs (sda1): using internal journal
[   30.560734] stmmaceth 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[  718.080568] usb 1-1.1: new high-speed USB device number 5 using oxnas-ehci
[  718.271941] usb 1-1.1: New USB device found, idVendor=152d, idProduct=1561
[  718.278794] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  718.286484] usb 1-1.1: Product: JMicron
[  718.290360] usb 1-1.1: Manufacturer: JMicron
[  718.294615] usb 1-1.1: SerialNumber: DB987654321EF
[  718.303536] scsi host2: uas
[  718.308354] scsi 2:0:0:0: Direct-Access     JMicron                   0223 PQ: 0 ANSI: 6
[  718.320826] sd 2:0:0:0: [sdb] Spinning up disk...
[  719.340720] ..ready
[  720.352104] sd 2:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[  720.359557] sd 2:0:0:0: [sdb] 4096-byte physical blocks
[  720.366837] sd 2:0:0:0: [sdb] Write Protect is off
[  720.371655] sd 2:0:0:0: [sdb] Mode Sense: 53 00 00 08
[  720.372459] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  720.403010]  sdb: unknown partition table
[  720.416596] sd 2:0:0:0: [sdb] Attached SCSI disk

fdisk -l

Disk /dev/mtdblock0: 14 MB, 14680064 bytes
171 heads, 42 sectors/track, 3 cylinders, total 28672 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xaaaaaaaa

This doesn't look like a partition table
Probably you selected the wrong device.

          Device Boot      Start         End      Blocks   Id  System
/dev/mtdblock0p1   ?  2863311530  1431655763  1431655765   aa  Unknown
/dev/mtdblock0p2   ?  2863311530  1431655763  1431655765   aa  Unknown
/dev/mtdblock0p3   ?  2863311530       21843   715838805   aa  Unknown
/dev/mtdblock0p4   ?  2863311530  1426085203  1428870485   aa  Unknown

Disk /dev/mtdblock1: 119 MB, 119537664 bytes
255 heads, 63 sectors/track, 14 cylinders, total 233472 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/sda: 8002 MB, 8002732032 bytes
241 heads, 36 sectors/track, 1801 cylinders, total 15630336 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              36    15625475     7812720   83  Linux

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table

mount 


sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=14958,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=12180k,mode=755)
/dev/sda1 on / type ext3 (rw,noatime,errors=continue,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=24340k)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)

e2label /dev/sdb1

e2label: No such file or directory while trying to open /dev/sdb1
Couldn't find valid filesystem superblock.

df -h

Filesystem      Size  Used Avail Use% Mounted on
rootfs          7.3G  1.4G  5.6G  20% /
udev             10M     0   10M   0% /dev
tmpfs            12M  296K   12M   3% /run
/dev/sda1       7.3G  1.4G  5.6G  20% /
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            24M     0   24M   0% /run/shm
tmpfs            60M     0   60M   0% /tmp

From what I gather, I've got an issue with my USB HD formatting. I'm not opposed to reformatting the disk, as the only thing that's on there is some music that I do already have somewhere else. So if that's what I need to do, I'm all for it. I won't be losing anything.

> 2. To install new u-boot, read the first post of
> the u-boot thread:
>
> http://forum.doozan.com/read.php?3,16017
>
> Ignore the preamble. You've already run the new
> u-boot series. You only need to this section to
> install newer u-boot version:
>
>

Quote

Updated 22 Nov 2015

>
> And like I've suggested, to be extra careful, you
> can preprare your commands as you about to do and
> I'll take a look.

I looked it over and it does look do able. I did the check for the bad block in the mtd0 area and it looks like(at least on this pro) that I'm alright. I could do it. I have a few Pogoplug Pro's. So it might be a good idea to upgrade them all. And I do have a sata cable and HD if I need to open them up. but you're also suggesting I pick up a serial cable? I can do that. I'll go back to the other link you've sent and see about getting one.

Thanks again!

mxhdrm,

> From what I gather, I've got an issue with my USB
> HD formatting. I'm not opposed to reformatting
> the disk, as the only thing that's on there is
> some music that I do already have somewhere else.
> So if that's what I need to do, I'm all for it. I
> won't be losing anything.

Yes I think it is best to reformat it from scratch.

> but you're also suggesting I pick
> up a serial cable? I can do that. I'll go back to
> the other link you've sent and see about getting
> one.

The SATA is of course for a fastest disk, and also to use for recovevery purpose. The Pogo V3 does not have UART booting like the Kirkwood boxes, so unbricking must be done with SATA.

Serial console is to really see what's going on during boot. It's the must have tool for hacking/learning Linux.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------

> Yes I think it is best to reformat it from
> scratch.

I did that and set things up properly with the formatting. So that's all fine now. But I'm still getting the problem with booting up with the two drives, so I figure I should bite the bullet and upgrade the u-boot.


> The SATA is of course for a fastest disk, and
> also to use for recovevery purpose. The Pogo V3
> does not have
>
> UART booting like the Kirkwood boxes, so
> unbricking must be done with SATA.
>
> Serial console is to really see what's going on
> during boot. It's the must have tool for
> hacking/learning Linux.

I'm going to see if I have the requisite supplies around the house for the serial console. I have some of the stuff here, but I may need some other parts.

I guess I'll have to fully digest the set up for the upgraded u-boot. And if that works, then I'll probably do them to all of the other plugs I have, just to keep things consistent.

mxhdrm,

> I'm going to see if I have the requisite supplies
> around the house for the serial console. I have
> some of the stuff here, but I may need some other
> parts.
>
> I guess I'll have to fully digest the set up for
> the upgraded u-boot. And if that works, then I'll
> probably do them to all of the other plugs I have,
> just to keep things consistent.

If you have serial console, then there is no urgency to upgrade u-boot. This can be solved easily. The older u-boot should be fine, we just need to see the booting activities a little more closely.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

That sounds good. I may have the USB serial adapter. I have to look. As for the CD-ROM sound card cable, I'll have to check the discarded computers at work. One of them will likely have what I'm looking for.

Thanks.

Hi all,

So I have the serial adapter and the cable that I should need. I opened up the pogoplug and I'll be connecting the serial cable in a few days. I have some time off from work, so I'll be able to devote some more time to this then. Thanks for all the help so fer, bodhi, and anyone else who would like to help as well.

Thanks.