Did a brick my v4?

[schn4rk]

$this->bbcode_second_pass_quote('lemwad', 'I') interpreted "top usb port" as the top port on the back. I guess I needed a big sticker on the device that says "Open here, Derp."
The fix worked fine. Thanks.

[WarheadsSE]

The real issue here is that the u-boot does not have access to the USB3.0 ports (blue), thus it is unusable.

[kmihelich]

I don't see how the instructions are anything but perfectly clear, as the SATA port is mentioned twice in the same line as "USB 2.0" in context with "top," in the context of "the device" as seen on the main page has no other possible meaning than the actual top of the device. The back is not, obviously, the top of the device. Also worth noting is that USB 3.0 ports are very much blue, which unless you're unfortunately colorblind, is a stark contrast to the black that has been seen for the last decade. There's a point to dumbing down instructions where we have to draw a line, and this would be one of them. We used to do things like use bold, change colors, fonts, italicize, and it has been proven that no matter how succinctly we describe an operation with any number of cosmetic enhancements to further emphasize, points will be missed.

The boot params were specifically set up, by myself, to accommodate any boot device configuration that was presented, whether the rootfs was on USB or SATA, and whether or not you had a regular data drive plugged into the other slot at boot. As U-Boot does not support booting from USB 3.0, drive assignments based on any drives that may or may not be present in those ports is obviously not included, because there is no way to check.

$this->bbcode_second_pass_quote('http://archlinuxarm.org/platforms/armv5/pogoplug-series-4', 'B')ooting into Arch Linux ARM is only supported from storage devices using either the SATA or USB 2.0 port on the top of the device. There is no U-Boot support for either SD or USB 3.0 booting.

$this->bbcode_second_pass_quote('WarheadsSE', 'T')he real issue here is that the u-boot does not have access to the USB3.0 ports (blue), thus it is unusable.

[kmihelich]

If the steps were followed correctly for creating the drive with the root filesystem using the USB3 ports, there's no reason it shouldn't boot when you move it to the USB2 port. I regularly re-image SATA drives using a SATA->USB cable, then unplug it from the cable and dock it into a SATA port. Nothing has changed with the drive, data is data.

[schn4rk]

$this->bbcode_second_pass_quote('kmihelich', 'I')f the steps were followed correctly for creating the drive with the root filesystem using the USB3 ports, there's no reason it shouldn't boot when you move it to the USB2 port. I regularly re-image SATA drives using a SATA->USB cable, then unplug it from the cable and dock it into a SATA port. Nothing has changed with the drive, data is data.

[kmihelich]

U-Boot only goes as far as loading the kernel. The kernel SCSI driver assigns those /dev/sd* devices. Drives don't care how they're connected. Like I said above, I frequently re-image using USB even though it ends up being plugged in as SATA. If the drive didn't work after it was set up when it was built through the USB3 port, either something in the stock firmware is screwing with things that I didn't catch, or it just wasn't set up right (the case more often than not, a minute detail skipped over).