Odroid will not boot after trying new image [Solved]

[mich04]

Hello, I was trying out a new image to see if I could get a network card to work. Now the xu4 will not boot. I was working on getting a newer kernel here is the image I tried

https://github.com/archfan/xu4-linux/releases/tag/v4.4

Here are the steps I took to install it.
1. sudo dd if=arch_linux_mainline.img of=/dev/sdb bs=4M && sync
2. mkdir root
3. sudo mount /dev/sdb1 root
4. cd root/boot
5. sudo sh sd_fusing.sh /dev/sdb
6. cd ../..
7. sudo umount root

The image was working fine until I ran out of space. So I fired up gparted on my main System resized the partition and than rebooted the xu4. It would boot but for some reason it had some file corruption. It would not pull an ip nor would it let me login even as root when I hooked up the hdmi. So I decided to follow the steps outlined here to bring it back to where I originally had it.

https://archlinuxarm.org/platforms/armv ... odroid-xu4

But now the unit will turn on flash the blue light for a moment and than just sit there with the fan on and no blue light. I also noted the remark on step 6 "Download and extract the root filesystem (as root, not via sudo):" I am stumped now because I have tried both install methods the official one and the unofficial image I tried. I have also tried 2 different micro sd cards as well as using 2 different adapters.

I can mount and see the files on the sd cards and it says that U-boot is successful when I do that step....I am not sure what to try now. I think that I need to wipe the drive clean but I feel like steps in the official instructions outline that.

*I just noticed these messages in dmesg on my main machine. maybe they can help?

$this->bbcode_second_pass_code('', '
210.479186] scsi 2:0:0:0: Direct-Access TS-RDF5 SD Transcend TS37 PQ: 0 ANSI: 6
[ 210.783227] sd 2:0:0:0: [sdb] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB)
[ 210.784039] sd 2:0:0:0: [sdb] Write Protect is off
[ 210.784047] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 210.785649] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 210.803541] sdb: sdb1
[ 210.808356] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 284.439344] sdb: sdb1
[ 284.444444] sdb: sdb1
[ 458.951788] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 691.073957] usb 1-2.3: USB disconnect, device number 8
[ 691.079158] sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 691.079168] sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 03 0b fb a0 00 00 c8 00
[ 691.079172] blk_update_request: I/O error, dev sdb, sector 51116960
[ 691.079179] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592278 (offset 0 size 8192 starting block 6389622)
[ 691.079185] Buffer I/O error on device sdb1, logical block 6389364
[ 691.079194] Buffer I/O error on device sdb1, logical block 6389365
[ 691.079202] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592279 (offset 0 size 12288 starting block 6389625)
[ 691.079205] Buffer I/O error on device sdb1, logical block 6389366
[ 691.079209] Buffer I/O error on device sdb1, logical block 6389367
[ 691.079212] Buffer I/O error on device sdb1, logical block 6389368
[ 691.079218] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592280 (offset 0 size 12288 starting block 6389628)
[ 691.079221] Buffer I/O error on device sdb1, logical block 6389369
[ 691.079224] Buffer I/O error on device sdb1, logical block 6389370
[ 691.079228] Buffer I/O error on device sdb1, logical block 6389371
[ 691.079233] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592281 (offset 0 size 8192 starting block 6389630)
[ 691.079236] Buffer I/O error on device sdb1, logical block 6389372
[ 691.079240] Buffer I/O error on device sdb1, logical block 6389373
[ 691.079245] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592289 (offset 0 size 8192 starting block 6389632)
[ 691.079252] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592283 (offset 0 size 32768 starting block 6389640)
[ 691.079262] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592284 (offset 0 size 20480 starting block 6389645)
[ 691.079380] sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 691.079386] sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 03 0b fc 68 00 00 90 00
[ 691.079389] blk_update_request: I/O error, dev sdb, sector 51117160
[ 691.079393] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592287 (offset 0 size 12288 starting block 6389648)
[ 691.079402] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592285 (offset 0 size 16384 starting block 6389652)
[ 691.079410] EXT4-fs warning (device sdb1): ext4_end_bio:315: I/O error -5 writing to inode 1592286 (offset 0 size 45056 starting block 6389663)
[ 691.085209] JBD2: Detected IO errors while flushing file data on sdb1-8
[ 691.085261] Aborting journal on device sdb1-8.
[ 691.085450] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[ 691.085457] EXT4-fs error (device sdb1): ext4_journal_check_start:56: Detected aborted journal
[ 691.085460] EXT4-fs (sdb1): Remounting filesystem read-only
[ 691.085463] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 691.085496] EXT4-fs (sdb1): ext4_writepages: jbd2_start: 9223372036854775806 pages, ino 1592331; err -30
[ 691.085540] JBD2: Detected IO errors while flushing file data on sdb1-8
[ 691.166065] EXT4-fs error (device sdb1): ext4_wait_block_bitmap:500: comm umount: Cannot read block bitmap - block_group = 1, block_bitmap = 1030
[ 691.166075] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 691.166107] EXT4-fs error (device sdb1): ext4_discard_preallocations:4036: comm umount: Error -5 reading block bitmap for 1
[ 691.166112] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 691.394490] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 691.394571] EXT4-fs error (device sdb1): ext4_put_super:837: Couldn't clean up the journal
[ 691.401373] EXT4-fs (sdb1): unable to read superblock
[ 1377.667899] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 1377.686930] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 1377.687358] scsi host2: usb-storage 2-1:1.0
[ 1378.694513] scsi 2:0:0:0: Direct-Access TS-RDF5 SD Transcend TS37 PQ: 0 ANSI: 6
[ 1379.074279] sd 2:0:0:0: [sdb] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB)
[ 1379.074958] sd 2:0:0:0: [sdb] Write Protect is off
[ 1379.074963] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 1379.075664] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1379.084525] sdb: sdb1
[ 1379.087044] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 1385.640857] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
')

[mich04]

I figured it out. I just ended up using gparted to create and format the partitions and the errors went away in dmesg. The system is up and running smoothly again. I think that gparted uses some different switches I will have to instigate that. Anyways I love Arch! thanks for all your hard work guys!

[chippey5]

Hello mich04, I am receiving the exact same issue as you were right now. When you say that you made the partitions yourselves, what does the partition table look like?