Kobo Original N416 SD Card Image - Page 4

tonyyng · 03-19-2019, 07:01 PM

Thanks for the suggestions, here is the output after bootsd and trying those commands

Code:

# blkid
blkid: /dev/mtdb6: Input/output error
/dev/mmcblk0p1: LABEL="Kobo upgrade" UUID="09e01ee3-dfa3-4f10-95e8-098b2afd5084"
# umount /dev/mtdblock6
umount: can't umount /dev/mtdblock6: Invalid argument
# dd if=/dev/zero of=/dev/mtdblock6 bs=1M conv=fsync
dd: can't open '/dev/mtdblock6': No such device or address
# msdosfs -c -n SomeLabel -v /dev/mtdblock6
/bin/sh: msdosfs: not found

I've messed up my mtdblock4. Are there equivalent commands to rebuild the mtdblock4 partition?

I tried:

Code:

 dd if=/dev/zero of=/dev/mtdblock4 bs=1M conv=fsync
end_request: I/O error, dev mtdblock4, sector 298752
Buffer I/O error on device mtdblock4, logical block 37344
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298760
Buffer I/O error on device mtdblock4, logical block 37345
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298768
Buffer I/O error on device mtdblock4, logical block 37346
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298776
Buffer I/O error on device mtdblock4, logical block 37347
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298784
Buffer I/O error on device mtdblock4, logical block 37348
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298792
Buffer I/O error on device mtdblock4, logical block 37349
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298800
Buffer I/O error on device mtdblock4, logical block 37350
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298808
Buffer I/O error on device mtdblock4, logical block 37351
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298816
Buffer I/O error on device mtdblock4, logical block 37352
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298824
Buffer I/O error on device mtdblock4, logical block 37353
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298832
end_request: I/O error, dev mtdblock4, sector 298840
end_request: I/O error, dev mtdblock4, sector 298848
end_request: I/O error, dev mtdblock4, sector 298856
end_request: I/O error, dev mtdblock4, sector 298864
end_request: I/O error, dev mtdblock4, sector 298872
end_request: I/O error, dev mtdblock4, sector 298880
end_request: I/O error, dev mtdblock4, sector 298888
end_request: I/O error, dev mtdblock4, sector 298896
end_request: I/O error, dev mtdblock4, sector 298904
end_request: I/O error, dev mtdblock4, sector 298912
end_request: I/O error, dev mtdblock4, sector 298920
end_request: I/O error, dev mtdblock4, sector 298928
end_request: I/O error, dev mtdblock4, sector 298936
end_request: I/O error, dev mtdblock4, sector 298944
end_request: I/O error, dev mtdblock4, sector 298952
end_request: I/O error, dev mtdblock4, sector 298960
end_request: I/O error, dev mtdblock4, sector 298968
end_request: I/O error, dev mtdblock4, sector 298976
end_request: I/O error, dev mtdblock4, sector 298984
end_request: I/O error, dev mtdblock4, sector 298992
end_request: I/O error, dev mtdblock4, sector 299000
dd: /dev/mtdblock4: Input/output error

tonyyng · 03-19-2019, 08:17 PM

Some good news. My mtdblock4 partition is back to normal after using BloodRagg's 'dd if=/dev/zero' approach to reset it:

Here's the log:

Code:

# dd if=/dev/zero of=/dev/mtdblock4 bs=1M conv=fsync
end_request: I/O error, dev mtdblock4, sector 298752
Buffer I/O error on device mtdblock4, logical block 37344
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298760
Buffer I/O error on device mtdblock4, logical block 37345
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298768
Buffer I/O error on device mtdblock4, logical block 37346
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298776
Buffer I/O error on device mtdblock4, logical block 37347
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298784
Buffer I/O error on device mtdblock4, logical block 37348
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298792
Buffer I/O error on device mtdblock4, logical block 37349
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298800
Buffer I/O error on device mtdblock4, logical block 37350
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298808
Buffer I/O error on device mtdblock4, logical block 37351
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298816
Buffer I/O error on device mtdblock4, logical block 37352
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298824
Buffer I/O error on device mtdblock4, logical block 37353
lost page write due to I/O error on mtdblock4
end_request: I/O error, dev mtdblock4, sector 298832
end_request: I/O error, dev mtdblock4, sector 298840
end_request: I/O error, dev mtdblock4, sector 298848
end_request: I/O error, dev mtdblock4, sector 298856
end_request: I/O error, dev mtdblock4, sector 298864
end_request: I/O error, dev mtdblock4, sector 298872
end_request: I/O error, dev mtdblock4, sector 298880
end_request: I/O error, dev mtdblock4, sector 298888
end_request: I/O error, dev mtdblock4, sector 298896
end_request: I/O error, dev mtdblock4, sector 298904
end_request: I/O error, dev mtdblock4, sector 298912
end_request: I/O error, dev mtdblock4, sector 298920
end_request: I/O error, dev mtdblock4, sector 298928
end_request: I/O error, dev mtdblock4, sector 298936
end_request: I/O error, dev mtdblock4, sector 298944
end_request: I/O error, dev mtdblock4, sector 298952
end_request: I/O error, dev mtdblock4, sector 298960
end_request: I/O error, dev mtdblock4, sector 298968
end_request: I/O error, dev mtdblock4, sector 298976
end_request: I/O error, dev mtdblock4, sector 298984
end_request: I/O error, dev mtdblock4, sector 298992
end_request: I/O error, dev mtdblock4, sector 299000
dd: /dev/mtdblock4: Input/output error
# dd if=/dev/zero of=/dev/mtdblock4 bs=1K conv=fsync
end_request: I/O error, dev mtdblock4, sector 298752
dd: writing '/dev/mtdblock4': Input/output error
149377+0 records in
149376+0 records out
# mount /dev/mtdblock4 /mnt/mtd4/
yaffs: dev is 32505860 name is "mtdblock4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.4, "mtdblock4"
yaffs: auto selecting yaffs2
**>> Block 1279 retired
# ls -l /mnt/mtd4/
drw-rw-rw-    1 root     root         2048 Aug 31 03:48 lost+found
drwxr-xr-x    1 root     root         2048 Jan  1  1970 mnt
drwxr-xr-x    1 root     root         2048 Jan  1  1970 proc
drwxr-xr-x    1 root     root         2048 Jan  1  1970 sys
drwxr-xr-x    1 root     root         2048 Jan  1  1970 tmp
drwxr-xr-x    1 root     root         2048 Jan  1  1970 usr
drwxr-xr-x    1 root     root         2048 Jan  1  1970 var
# cd /mnt/mtd4/
# ls -ltr
drwxr-xr-x    1 root     root         2048 Jan  1  1970 usr
drwxr-xr-x    1 root     root         2048 Jan  1  1970 tmp
drwxr-xr-x    1 root     root         2048 Jan  1  1970 sys
drwxr-xr-x    1 root     root         2048 Jan  1  1970 proc
drwxr-xr-x    1 root     root         2048 Jan  1  1970 mnt
drwxr-xr-x    1 root     root         2048 Jan  1  1970 var
drw-rw-rw-    1 root     root         2048 Aug 31 03:48 lost+found
# rm -rf mnt
# rm -rf tmp
# rm -rf usr
# ls -ltr
drwxr-xr-x    1 root     root         2048 Jan  1  1970 sys
drwxr-xr-x    1 root     root         2048 Jan  1  1970 proc
drwxr-xr-x    1 root     root         2048 Jan  1  1970 var
drw-rw-rw-    1 root     root         2048 Aug 31 03:48 lost+found
# sync
# ls -ltr
drwxr-xr-x    1 root     root         2048 Jan  1  1970 sys
drwxr-xr-x    1 root     root         2048 Jan  1  1970 proc
drwxr-xr-x    1 root     root         2048 Jan  1  1970 var
drw-rw-rw-    1 root     root         2048 Aug 31 03:48 lost+found
# rm -rf proc
# rm -rf var
# sync
# ls -ltr
drwxr-xr-x    1 root     root         2048 Jan  1  1970 sys
drw-rw-rw-    1 root     root         2048 Aug 31 03:48 lost+found
# rm -rf sys
# sync
# ls -ltr
drw-rw-rw-    1 root     root         2048 Aug 31 03:48 lost+found
# rm -rf lost\+found/
**>> yaffs chunk 64 was not erased
**>> yaffs chunk 128 was not erased
**>> yaffs chunk 192 was not erased
**>> yaffs chunk 256 was not erased
**>> yaffs chunk 320 was not erased
<snip>
**>> yaffs chunk 74688 was not erased
**>> yaffs write required 1168 attempts
Unable to handle kernel NULL pointer dereference at virtual address 00000008
arch_reset: attempting watchdog reset

REBOOTED - had to gradually delete stuff from 'lost + found'

# mount /dev/mtdblock4
mount: can't find /dev/mtdblock4 in /etc/fstab
# mount /dev/mtdblock4 /mnt/mtd4/
yaffs: dev is 32505860 name is "mtdblock4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.4, "mtdblock4"
yaffs: auto selecting yaffs2
**>> Block 1279 retired
# cd /mnt/mtd4/
# ls -ltr
drw-rw-rw-    1 root     root         2048 Aug 31 03:58 lost+found
# ls -l lost\+found/
d---------    1 root     root         2048 Aug 31 03:58 obj1079
d---------    1 root     root         2048 Aug 31 03:58 obj1340
#

Was left with the previous two directories, which I couldn't delete

# cd /
# cp -P -r bin /mnt/mtd4
cp -P -r boot /mnt/mtd4
cp -P -r dev /mnt/mtd4
cp -P -r etc /mnt/mtd4
cp -P -r lib /mnt/mtd4
cp -P -r lost+found /mnt/mtd4
cp -P -r root /mnt/mtd4
cp -P -r sbin /mnt/mtd4
cp -P -r usr /mnt/mtd4
cp -P -r linuxrc /mnt/mtd4
mkdir /mnt/mtd4/mnt
mkdir /mnt/mtd4/mnt/onboard
mkdir# cp -P -r boot /mnt/mtd4
 /# cp -P -r dev /mnt/mtd4
mnt/mtcp: cannot stat 'dev/mtdb6': Input/output error
d4# cp -P -r etc /mnt/mtd4
/mnt/mtd4
mkdir /mnt/mtd4/proc
mkdir /mnt/mtd4/sys
mkdir /mnt/mtd4/tmp
mkdir /mnt/mtd4/var# cp -P -r lib /mnt/mtd4
# cp -P -r lost+found /mnt/mtd4
# cp -P -r root /mnt/mtd4
# cp -P -r sbin /mnt/mtd4
# cp -P -r usr /mnt/mtd4

# cp -P -r linuxrc /mnt/mtd4
# mkdir /mnt/mtd4/mnt
# mkdir /mnt/mtd4/mnt/onboard
# mkdir /mnt/mtd4/mnt/mtd4
# mkdir /mnt/mtd4/proc
# mkdir /mnt/mtd4/sys
# mkdir /mnt/mtd4/tmp
# mkdir /mnt/mtd4/var
#

Standard Reboot using filesystem on mtdblock4

Please press Enter to activate this console. hwclock: settimeofday() failed: Invalid argument

# ls -ltr
drwxr-xr-x   11 root     root            0 Jan  1  1970 sys
dr-xr-xr-x   36 root     root            0 Jan  1  1970 proc
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 bin
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 dev
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 boot
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 etc
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 lib
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 sbin
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 root
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 usr
drwxr-xr-x    1 root     root         2048 Aug 31 04:10 var
drwxr-xr-x    1 root     root         2048 Aug 31 04:10 mnt
lrwxrwxrwx    1 root     root           11 Aug 31 04:10 linuxrc -> bin/busybox
drw-rw-rw-    1 root     root         2048 Aug 31 04:11 lost+found
drwxrwxrwt    2 root     root           80 Aug 31 04:11 tmp
# cd lost\+found/
# ls -ltr
d---------    1 root     root         2048 Aug 31 04:11 obj1340
d---------    1 root     root         2048 Aug 31 04:11 obj1079
#
# cd obj1340/

Hmm.  This directory seems normal now.

# ls
Apia         Funafuti     Guadalcanal  Majuro       Noumea       Saipan
Chuuk        Galapagos    Johnston     Nauru        Palau        Truk
Fiji         Gambier      Kiritimati   Niue         Pohnpei
# ls -ltr
-rw-r--r--    2 root     root          624 Jan  1  1970 Truk
-rw-r--r--    1 root     root          709 Jan  1  1970 Saipan
-rw-r--r--    1 root     root          624 Jan  1  1970 Pohnpei
-rw-r--r--    1 root     root          780 Jan  1  1970 Noumea
-rw-r--r--    1 root     root          720 Jan  1  1970 Nauru
-rw-r--r--    1 root     root          651 Jan  1  1970 Majuro
-rw-r--r--    1 root     root          684 Jan  1  1970 Kiritimati
-rw-r--r--    1 root     root          599 Jan  1  1970 Johnston
-rw-r--r--    1 root     root          638 Jan  1  1970 Guadalcanal
-rw-r--r--    1 root     root          639 Jan  1  1970 Gambier
-rw-r--r--    1 root     root          677 Jan  1  1970 Galapagos
-rw-r--r--    1 root     root          776 Jan  1  1970 Fiji
-rw-r--r--    2 root     root          624 Jan  1  1970 Chuuk
-rw-r--r--    1 root     root          748 Jan  1  1970 Apia
-rw-r--r--    1 root     root          620 Jan  1  1970 Palau
-rw-r--r--    1 root     root          680 Jan  1  1970 Niue
-rw-r--r--    1 root     root          621 Jan  1  1970 Funafuti
# rm *
# cd ..
# rm -rf obj1340/
# cd obj1079/
# ls -ltr
-rw-r--r--    1 root     root         2774 Jan  1  1970 PST8PDT
-rw-r--r--    1 root     root          598 Jan  1  1970 MST
-rw-r--r--    1 root     root          599 Jan  1  1970 HST
-rw-r--r--    2 root     root          606 Aug 31 04:08 ROK
-rw-r--r--    2 root     root          607 Aug 31 04:08 PRC
-rw-r--r--    2 root     root          606 Aug 31 04:08 Iran
-rw-r--r--    2 root     root         2689 Aug 31 04:08 UTC
# rm *
# cd ..
# rm -rf obj1079/
# cd ..
# ls -ltr
drwxr-xr-x   11 root     root            0 Jan  1  1970 sys
dr-xr-xr-x   36 root     root            0 Jan  1  1970 proc
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 bin
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 dev
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 boot
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 etc
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 lib
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 sbin
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 root
drwxr-xr-x    1 root     root         2048 Aug 31 04:08 usr
drwxr-xr-x    1 root     root         2048 Aug 31 04:10 var
drwxr-xr-x    1 root     root         2048 Aug 31 04:10 mnt
lrwxrwxrwx    1 root     root           11 Aug 31 04:10 linuxrc -> bin/busybox
drw-rw-rw-    1 root     root         2048 Aug 31 04:11 lost+found
drwxrwxrwt    2 root     root           80 Aug 31 04:11 tmp

Back to normal

BloodRagg · 03-20-2019, 10:37 AM

Should not have deleted those files in lost+found, these are your markers where your flash is damaged.
Its like you removed the billboards that say: "beware quicksand". If the files are too big, you can clean out with a smaller bs=512, will take longer though.

Do you remote in over u-boot or linux ? the mkdosfs is in the tarball i sent you. (should be on your sdcard as well though)

Code:

cat /proc/mtd or cat /proc/mtdinfo .. cant remember which
cat /proc/partitions

#check sdcard files against mtd4 files:
find -type f / -exec sha256sum {} \; > /tmp/files.sha256sum
sed -i 's,^/,/mnt/mtd4/,' /tmp/files.sha256sum
# sha256sum -c /tmp/files.sha256sum, checks all files, below will show all failed.
sha256sum -c /tmp/files.sha256sum|grep -v "OK$"

#check udev devices
udevd --daemon
udevadm trigger --action=add
udevadm settle --timeout=2

#check for mtdblocks
find /dev -iname 'mtdblock*'

waiting on your output

tonyyng · 03-20-2019, 12:48 PM

Before responding to your latest post, I want to report some progress using the tarball you sent me and sha256sum. That procedure using sha256sum is quite neat and will be added to my toolbox.

I did find that after extracting your tarball, I had to also extract two additional tarballs inside it. These tarballs are extracted by /etc/init.d/rc5:

Code:

tony@tony-Vostro-2520:~/BloodRagg$ sudo tar xzf usr.tgz -C .
tony@tony-Vostro-2520:~/BloodRagg$ sudo tar xzf etc/tz.tgz -C etc
tony@tony-Vostro-2520:~/BloodRagg$ sudo rm usr.tgz
tony@tony-Vostro-2520:~/BloodRagg$ sudo rm etc/tz.tgz
tony@tony-Vostro-2520:~/BloodRagg$ sudo find . -type f -exec sha256sum {} \; > sha256sums.txt
tony@tony-Vostro-2520:~/BloodRagg$ cat sha256sums.txt | wc -l
1944

I copied the sha256sums.txt on my sd card, and from the kobo serial session did the comparison:

Code:

# cd /
# sha256sum -c /mnt/sd/fs/sha256sums.txt | grep -v "OK$"
./usr/local/Kobo/libnickel.so.1.0.0: FAILED
./usr/local/Kobo/dicthtml/zt.html: FAILED
./usr/local/Kobo/dicthtml/dn.html: FAILED
./usr/local/Kobo/dicthtml/mk.html: FAILED
./usr/local/Kobo/dicthtml/fw.html: FAILED
./usr/local/Kobo/dicthtml/ap.html: FAILED
./usr/local/Kobo/dicthtml/oy.html: FAILED
./usr/local/Kobo/dicthtml/ck.html: FAILED
./usr/local/Kobo/dicthtml/qp.html: FAILED
./usr/local/Kobo/dicthtml/sk.html: FAILED
./usr/local/Kobo/dicthtml/kh.html: FAILED
./usr/local/Kobo/dicthtml/iw.html: FAILED
./usr/local/Kobo/dicthtml/xc.html: FAILED
./usr/local/Kobo/dicthtml/ur.html: FAILED
./usr/local/Kobo/dicthtml/ab.html: FAILED
./usr/local/Kobo/dicthtml/dt.html: FAILED
./usr/local/Kobo/dicthtml/du.html: FAILED
./usr/local/Kobo/dicthtml/aa.html: FAILED
./usr/local/Kobo/dicthtml/wt.html: FAILED
./usr/local/Kobo/dicthtml/kw.html: FAILED
./usr/local/Kobo/dicthtml/in.html: FAILED
./usr/local/Kobo/dicthtml/cd.html: FAILED
./usr/local/Kobo/dicthtml/hf.html: FAILED
./usr/local/Kobo/dicthtml/tl.html: FAILED
./usr/local/Kobo/dicthtml/cq.html: FAILED
./usr/local/Kobo/dicthtml/rn.html: FAILED
./usr/local/Kobo/dicthtml/ua.html: FAILED
./usr/local/Kobo/dicthtml/sw.html: FAILED
./usr/local/Kobo/dicthtml/hu.html: FAILED
./usr/local/Kobo/dicthtml/fo.html: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtXmlPatterns.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtNetwork.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtGui.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtDBus.so.4.6.2: FAILED
./usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtScript.so.4.6.2: FAILED
./etc/zoneinfo-leaps/Mideast/Riyadh88: FAILED
./etc/zoneinfo-leaps/Europe/Nicosia: FAILED
./etc/zoneinfo-leaps/Europe/Istanbul: FAILED
./etc/zoneinfo-leaps/Turkey: FAILED
./etc/zoneinfo-leaps/Asia/Karachi: FAILED
./etc/zoneinfo-leaps/Asia/Novosibirsk: FAILED
./etc/zoneinfo-leaps/Asia/Kuching: FAILED
./etc/zoneinfo-leaps/Asia/Almaty: FAILED
./etc/zoneinfo-leaps/Asia/Brunei: FAILED
./etc/zoneinfo-leaps/Asia/Anadyr: FAILED
./etc/zoneinfo-leaps/Asia/Kuala_Lumpur: FAILED
./etc/zoneinfo-leaps/Asia/Kabul: FAILED
./etc/zoneinfo-leaps/Asia/Jayapura: FAILED
./etc/zoneinfo-leaps/Asia/Aqtau: FAILED
./etc/zoneinfo-leaps/Asia/Riyadh: FAILED
./etc/zoneinfo-leaps/Asia/Dubai: FAILED
./etc/zoneinfo-leaps/Asia/Riyadh88: FAILED
./etc/zoneinfo-leaps/Asia/Sakhalin: FAILED
./etc/zoneinfo-leaps/Asia/Pontianak: FAILED
./etc/zoneinfo-leaps/Asia/Vientiane: FAILED
./etc/zoneinfo-leaps/Asia/Nicosia: FAILED
./etc/zoneinfo-leaps/Asia/Istanbul: FAILED
./etc/zoneinfo-leaps/Asia/Kuwait: FAILED
./etc/zoneinfo-leaps/Asia/Jakarta: FAILED
./etc/zoneinfo-leaps/Asia/Novokuznetsk: FAILED
./etc/zoneinfo-leaps/Asia/Kamchatka: FAILED
./etc/zoneinfo-leaps/Asia/Bahrain: FAILED
./sha256sums.txt: FAILED
sha256sum: WARNING: 64 of 1944 computed checksums did NOT match

After fixing those problems (and getting a clean bill of health from sha256sums), my kobo now starts nickel without a segmentation fault.

It now boots and goes to a "BOOKS, BY TITLE" page on the Kobo!

I see the following in the serial session

Code:

init Flash Error !!!
fd_init Done !!!
insmod: can't insert '/lib/modules/module.ko': Operation not permitted
mount: mounting /dev/mtdblock6 on /mnt/onboard failed: No such device or address
hwclock: settimeofday() failed: Invalid argument
PORT: 4034920448 baud 115200 uart: ulcon = 0x00000003, ucon = 0x000003c5, ufcon = 0x00000051 ubrdiv 0x00000023 umcon 0x00000000

Please press Enter to activate this console. status != ButtonDev.StatusBYKeypad!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!#:.
****AP read ADC: ret 581
ret 581
IOCTL:READ 581
no usb connected, turn LED off
TZ= "NickelTime0"
CHECKING DB VERSION FOR MIGRATION
DESIRED VERSION:  12
CURRENT VERSION:  12
Writing `version` file for use by the desktop client
Setting current page:  1
s1d13521fb_ioctl() 0 params     cmd=0x4528
s1d13521fb_ioctl() 0 params     cmd=0x4529
s1d13521fb_ioctl() 0 params     cmd=0x4528
s1d13521fb_ioctl() 0 params     cmd=0x4529
s1d13521fb_ioctl() 0 params     cmd=0x4528
s1d13521fb_ioctl() 0 params     cmd=0x4529
s1d13521fb_ioctl() 0 params     cmd=0x4528
s1d13521fb_ioctl() 0 params     cmd=0x4529
*5 c=0x88 h=1 t=1*RealTimeClock::RealTimeClock(int) minutes == 15
E=E=E=E=E=E=E=E=freeze!!!!!!!!!!!!!!!!!!!!
E=E=E=E=

But it's not all good news. If I disconnect the kobo from the FTDI adapter and reboot, it doesn't get to the same page. It just sits there with the blue LED on, with none of the 7 black squares it normally puts up for progress.

If I then connect the FTDI adapter, I get a u-boot prompt

Code:

eBR-1A #
eBR-1A #

If I enter the boot command at the u-boot prompt, it boots as I described above.

One step forward, two steps back...

tonyyng · 03-20-2019, 12:55 PM

Quote:

Do you remote in over u-boot or linux ?

I use Tera Term on Windows 10, connecting to a COM port associated with an FTDI adapter. I can connect to u-boot (if I hit a key during the startup sequence) or to a bash shell once it boots to the file system.

Here's the output for those commands.

Code:

# pkill nickel
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "uboot"
mtd1: 001e0000 00020000 "kernel"
mtd2: 000c0000 00020000 "picture"
mtd3: 00020000 00020000 "parameters"
mtd4: 0a000000 00020000 "rootfs"
mtd5: 00100000 00020000 "app"
mtd6: 35b40000 00020000 "other"
# cat /proc/partitions
major minor  #blocks  name

  31     0        512 mtdblock0
  31     1       1920 mtdblock1
  31     2        768 mtdblock2
  31     3        128 mtdblock3
  31     4     163840 mtdblock4
  31     5       1024 mtdblock5
  31     6     879872 mtdblock6
# find /dev -iname mtdblock*
/dev/mtdblock5
/dev/mtdblock2
/dev/mtdblock3
/dev/mtdblock4
/dev/mtdblock6
/dev/mtdblock0
/dev/mtdblock1
# udevd --daemon
/bin/sh: udevd: not found
# udevadm
/bin/sh: udevadm: not found
# dd if=/dev/zero of=/dev/mtdblock6 bs=1M conv=fsync
**>> Block 534 retired
Block 534 is in state 9 after gc, should be erased
dd: can't open '/dev/mtdblock6': No such device or address
# dd if=/dev/zero of=/dev/mtdblock6 bs=512 conv=fsync
dd: can't open '/dev/mtdblock6': No such device or address

tonyyng · 03-20-2019, 01:21 PM

Forgot one command:

Code:

Please press Enter to activate this console. #
# pkill nickel
# blkid
# umount /dev/mtdblock6
umount: can't umount /dev/mtdblock6: Invalid argument
# dd if=/dev/zero of=/dev/mtdblock6 bs=512 conv=fsync
dd: can't open '/dev/mtdblock6': No such device or address
# mkdosfs -c -n SomeLabel -v /dev/mtdblock6
mkdosfs 3.0.6 (04 Oct 2009)
/dev/mtdblock6: No such device or address

BloodRagg · 03-20-2019, 02:07 PM

Quote:

Originally Posted by tonyyng

One step forward, two steps back...

Ahh thats a shame, i think you memory is unreliable, but like i said before: Do not delete the files, create a hidden folder .badblocks and move all files with errors there. These should occupy the bad blocks so they cannot be given out to others. You might run out of disk space though.

Reboot and run the checksum again, there is a good chance that chip is like quicksand.
You could have new errors.

On the /dev/mtdblock6 matter try adding "conv=noerror"
You could also use a new sdcard and mount that as /mnt/onboard in the rcS.

That would keep your books and database safe.

keep trying

If all fails, take some superglue and never remove that sdcard

tonyyng · 03-20-2019, 05:05 PM

I've rerun the sha256sum and it is still okay.

I wasn't sure whether you meant to replace the conv arg or add, so I tried it both ways.

Code:

# dd if=/dev/zero of=/dev/mtdblock6 bs=512 conv=noerror
dd: can't open '/dev/mtdblock6': No such device or address
# dd if=/dev/zero of=/dev/mtdblock6 bs=512 conv=fsync conv=noerror
dd: can't open '/dev/mtdblock6': No such device or address

I might just retire this device as opposed to use a workaround to make it work.
It was just something that peaked my interest, but that is quickly waning.

Thanks for your help (and all others that contributed).

BloodRagg · 03-21-2019, 06:01 AM

Great, that means it aint that bad
Last attempt to revive /dev/mtdblock6, try ddrescue

Code:

ddrescue --force /dev/zero /dev/mtdblock6 --log-events=log.txt

Then format it with:
options:
-c Check the device for bad blocks before creating the file system.
-n Volume-name
-v Verbose execution.

Code:

mkdosfs -c -n 0000-0000 -v /dev/mtdblock6

tonyyng · 03-21-2019, 10:55 AM

I wasn't able to run it.

On Ubuntu:

Code:

tony@tony-Vostro-2520:~$ cd /mnt/sd
tony@tony-Vostro-2520:/mnt/sd$ sudo unzip /home/tony/ddrescue.zip
Archive:  /home/tony/ddrescue.zip
  inflating: ddrescue
  inflating: ddrescuelog
tony@tony-Vostro-2520:/mnt/sd$ ls -ltr
total 252
drwxr-xr-x  2 root root   4096 Dec 31  1969 sys
drwxr-xr-x  2 root root   4096 Dec 31  1969 proc
drwxr-xr-x  7 root root   4096 Dec 31  1969 usr
drwxr-xr-x 10 root root   4096 Dec 31  1969 etc
drwx------  2 root root  16384 Feb 25 19:16 lost+found
drwxr-xr-x  2 root root   4096 Feb 25 19:16 boot
drwxr-xr-x  2 root root   4096 Feb 25 19:16 bin
drwxr-xr-x  6 root root   4096 Feb 25 19:16 lib
drwxr-xr-x  2 root root   4096 Feb 25 19:16 root
lrwxrwxrwx  1 root root     11 Feb 25 19:16 linuxrc -> bin/busybox
drwxr-xr-x  2 root root   4096 Feb 25 19:16 sbin
drwxr-xr-x  2 root root   4096 Feb 25 21:45 tmp
drwxr-xr-x  8 root root   4096 Mar 17 21:24 mtdutils-1.4.9
drwxr-xr-x  8 root root   4096 Mar 17 21:24 mtdutils-1.5.0
drwxr-xrwx  2 root root   4096 Mar 19 21:23 fs
-rwxrwxr-x  1 root root 107626 Mar 21 05:40 ddrescue
-rwxrwxr-x  1 root root  56948 Mar 21 05:40 ddrescuelog
drwxr-xr-x  5 root root   4096 Aug 29  2029 mnt
drwxr-xr-x  2 root root   4096 Aug 29  2029 dev
drwxr-xr-x  4 root root   4096 Aug 31  2029 var
tony@tony-Vostro-2520:/mnt/sd$ cd /
tony@tony-Vostro-2520:/$ sudo umount /dev/sdc1

On Kobo

Code:

# mount /dev/mmcblk0p1 /mnt/sd
kjournald starting.  Commit interval 5 seconds
EXT3 FS on mmcblk0p1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
# cd /mnt/sd
# ls -l
drwxr-xr-x    2 root     root         4096 Feb 26  2019 bin
drwxr-xr-x    2 root     root         4096 Feb 26  2019 boot
-rwxrwxr-x    1 root     root       107626 Mar 21  2019 ddrescue
-rwxrwxr-x    1 root     root        56948 Mar 21  2019 ddrescuelog
drwxr-xr-x    2 root     root         4096 Aug 29 13:07 dev
drwxr-xr-x   10 root     root         4096 Jan  1  1970 etc
drwxr-xrwx    2 root     root         4096 Mar 20  2019 fs
drwxr-xr-x    6 root     root         4096 Feb 26  2019 lib
lrwxrwxrwx    1 root     root           11 Feb 26  2019 linuxrc -> bin/busybox
drwx------    2 root     root        16384 Feb 26  2019 lost+found
drwxr-xr-x    5 root     root         4096 Aug 29 12:13 mnt
drwxr-xr-x    8 root     root         4096 Mar 18  2019 mtdutils-1.4.9
drwxr-xr-x    8 root     root         4096 Mar 18  2019 mtdutils-1.5.0
drwxr-xr-x    2 root     root         4096 Jan  1  1970 proc
drwxr-xr-x    2 root     root         4096 Feb 26  2019 root
drwxr-xr-x    2 root     root         4096 Feb 26  2019 sbin
drwxr-xr-x    2 root     root         4096 Jan  1  1970 sys
drwxr-xr-x    2 root     root         4096 Feb 26  2019 tmp
drwxr-xr-x    7 root     root         4096 Jan  1  1970 usr
drwxr-xr-x    4 root     root         4096 Aug 31 04:33 var
# ./ddrescue --force /dev/zero /dev/mtdblock6 --log-events=log.txt
./ddrescue: line 1: syntax error: unexpected word (expecting ")")
# ./ddrescue --help
./ddrescue: line 1: syntax error: unexpected word (expecting ")")

BloodRagg · 03-22-2019, 01:50 PM

My bad, im having some toolchain related problems
So i compiled some tools, to test it.

Hopefully they will work for you.

tonyyng · 03-22-2019, 02:38 PM

Was I supposed to try and recompile these for the Kobo OS? That's beyond my skill set.

I tried them by unzip/tar'ing them to the SD, but get the same error:

Code:

# pkill nickel
# cd /mnt/sd
# ls
# cd ..
# mount /dev/mmcblk0p1 /mnt/sd
kjournald starting.  Commit interval 5 seconds
EXT3 FS on mmcblk0p1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
# cd /mnt/sd/tools/
# cd ddrescue-1.24/
# ./ddrescue --force /dev/zero /dev/mtdblock6 --log-events=log.txt
./ddrescue: line 1: syntax error: unexpected word (expecting ")")

BloodRagg · 03-22-2019, 03:08 PM

No they are all compiled. Apparently beyond my skill set too

Are all packages broken ? I included mtdutils and some other tools too.
Otherwise i may have to use another toolchain

New toolchain: if it compains about libstdc++.so missing load with:
LD_LIBRARY_PATH=. ./ddrescue --help

Any experienced programmer feel free to jump in ..Im out of options after this

tonyyng · 03-22-2019, 03:20 PM

Quote:

Originally Posted by BloodRagg

No they are all compiled. Apparently beyond my skill set too

Are all packages broken ? I included mtdutils and some other tools too.
Otherwise i may have to use another toolchain

Yeah, I get the same error message with all the binaries.

Thanks for trying.

BloodRagg · 03-22-2019, 04:32 PM

Try this one

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Needing SD Card Image for Kobo Original N647	megaroo96	Kobo Developer's Corner	263	08-23-2023 12:11 PM
Glo Kobo Glo: Need SD card image	m0rh0ld	Kobo Developer's Corner	2360	08-23-2023 11:58 AM
Kobo Original N416 - Looking for r22907 1.8.3 Firmware	tonyyng	Kobo Reader	16	02-24-2019 02:56 PM
Want to update your Original Kobo to 1.8 via SD card?	3d0g	Kobo Reader	12	12-17-2010 12:38 AM

03-20-2019, 10:37 AM	#48
BloodRagg Zealot Posts: 128 Karma: 842196 Join Date: Feb 2019 Device: none	Should not have deleted those files in lost+found, these are your markers where your flash is damaged. Its like you removed the billboards that say: "beware quicksand". If the files are too big, you can clean out with a smaller bs=512, will take longer though. Do you remote in over u-boot or linux ? the mkdosfs is in the tarball i sent you. (should be on your sdcard as well though) Code: cat /proc/mtd or cat /proc/mtdinfo .. cant remember which cat /proc/partitions #check sdcard files against mtd4 files: find -type f / -exec sha256sum {} \; > /tmp/files.sha256sum sed -i 's,^/,/mnt/mtd4/,' /tmp/files.sha256sum # sha256sum -c /tmp/files.sha256sum, checks all files, below will show all failed. sha256sum -c /tmp/files.sha256sum\|grep -v "OK$" #check udev devices udevd --daemon udevadm trigger --action=add udevadm settle --timeout=2 #check for mtdblocks find /dev -iname 'mtdblock*' waiting on your output

03-20-2019, 05:05 PM	#53
tonyyng Enthusiast Posts: 46 Karma: 10 Join Date: Jan 2019 Device: none	I've rerun the sha256sum and it is still okay. I wasn't sure whether you meant to replace the conv arg or add, so I tried it both ways. Code: # dd if=/dev/zero of=/dev/mtdblock6 bs=512 conv=noerror dd: can't open '/dev/mtdblock6': No such device or address # dd if=/dev/zero of=/dev/mtdblock6 bs=512 conv=fsync conv=noerror dd: can't open '/dev/mtdblock6': No such device or address I might just retire this device as opposed to use a workaround to make it work. It was just something that peaked my interest, but that is quickly waning. Thanks for your help (and all others that contributed).

Advert

Advert