[Solved] Issue creating image of Revolution Pi Connect+

Topics about the Hardware of Revolution Pi
Post Reply
aconite33
Posts: 0
Joined: 01 Nov 2020, 23:08
Answers: 0

[Solved] Issue creating image of Revolution Pi Connect+

Post by aconite33 »

Hello,

I recently picked up a Revolution Pi Connect+ and I'm following along in the tutorials. I've been able to get a successful bootup and DHCP, along with connecting to the device. However, when I am trying to create an image, I've encountered some problems.

I first tried doing it with Windows, following the directions, but I am now trying to do it with Linux and I'm experiencing the same issue. The Connect+ seems to disconnect about every minute, which interrupts the process of creating an image. I'm not sure if there is something additional I need to do to make sure the device stays stable.

Logs from dmesg:

Code: Select all

[ 1545.840851] usb 1-2: USB disconnect, device number 12
[ 1545.840950] sd 6:0:0:0: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 1545.840951] sd 6:0:0:0: [sdf] tag#0 CDB: Read(10) 28 00 00 0e ff 08 00 00 f0 00
[ 1545.840953] blk_update_request: I/O error, dev sdf, sector 982792 op 0x0:(READ) flags 0x84700 phys_seg 2 prio class 0
[ 1545.840969] blk_update_request: I/O error, dev sdf, sector 983032 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1545.841000] blk_update_request: I/O error, dev sdf, sector 983048 op 0x0:(READ) flags 0x84700 phys_seg 2 prio class 0
[ 1545.841004] blk_update_request: I/O error, dev sdf, sector 983288 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1545.841016] blk_update_request: I/O error, dev sdf, sector 982792 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1545.841017] Buffer I/O error on dev sdf2, logical block 110561, async page read
[ 1545.841106] blk_update_request: I/O error, dev sdf, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[ 1545.846020] blk_update_request: I/O error, dev sdf, sector 982792 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1545.846023] Buffer I/O error on dev sdf2, logical block 110561, async page read
[ 1545.868848] sd 6:0:0:0: [sdf] Synchronizing SCSI cache
[ 1545.868874] sd 6:0:0:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 1545.872256] Buffer I/O error on dev sdf2, logical block 360448, lost sync page write
[ 1545.872260] JBD2: Error -5 detected when updating journal superblock for sdf2-8.
[ 1545.872261] Aborting journal on device sdf2-8.
[ 1545.872262] Buffer I/O error on dev sdf2, logical block 360448, lost sync page write
[ 1545.872263] JBD2: Error -5 detected when updating journal superblock for sdf2-8.
[ 1545.897026] FAT-fs (sdf1): unable to read boot sector to mark fs as dirty
[ 1552.931639] usb 1-2: new high-speed USB device number 13 using xhci_hcd
[ 1553.079828] usb 1-2: config index 0 descriptor too short (expected 55, got 32)
[ 1553.080065] usb 1-2: New USB device found, idVendor=0a5c, idProduct=2764, bcdDevice= 0.00
[ 1553.080066] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1553.080068] usb 1-2: Product: BCM2710 Boot
[ 1553.080068] usb 1-2: Manufacturer: Broadcom
Here is my DD command:

Code: Select all

sudo dd if=/dev/sdf2 of=~/Downloads/revpi_original.img bs=8M status=progress
I grabbed the usbboot git and I've ran rpiboot using sudo.

Any ideas what might be causing this?


Edit - Updated

Figured it out. RTFM, needed to plug back the 'Watch Dog' hardwire. Now I know why it was restarting every 5 minutes :)
Last edited by aconite33 on 02 Nov 2020, 00:04, edited 1 time in total.
Post Reply