I was trying to do a backup on my sgh-t989 with clockworkmod and it kept locking up so went into the shell over adb to look at dmesg. This is what turned up:
<4>[ 71.804931] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 71.808410] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 71.808746] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts:
<2>[ 75.416381] EXT4-fs error (device mmcblk0p24): ext4_init_inode_table:1296: comm ext4lazyinit: Something is wrong with group 0
<2>[ 75.416412] Used itable blocks: 479itable unused count: 0
<2>[ 75.416442]
<3>[ 75.848297] Aborting journal on device mmcblk0p24-8.
<2>[ 75.862945] EXT4-fs (mmcblk0p24): Remounting filesystem read-only
<6>[ 157.712677] zcache: destroyed pool id=1, cli_id=65535
<4>[ 200.051544] adbd (152): /proc/152/oom_adj is deprecated, please use /proc/152/oom_score_adj instead.
<3>[ 240.546386] INFO: task jbd2/mmcblk0p24:139 blocked for more than 120 seconds.
<3>[ 240.546844] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 240.547302] jbd2/mmcblk0p24 D c078a2d8 0 139 2 0x00000000
<4>[ 240.548065] [<c078a2d8>] (__schedule+0x600/0x6e4) from [<c02d3780>] (jbd2_journal_commit_transaction+0x24c/0x14b0)
<4>[ 240.548583] [<c02d3780>] (jbd2_journal_commit_transaction+0x24c/0x14b0) from [<c02d8490>] (kjournald2+0xa4/0x204)
<4>[ 240.549102] [<c02d8490>] (kjournald2+0xa4/0x204) from [<c01a75f8>] (kthread+0x7c/0x84)
<4>[ 240.549560] [<c01a75f8>] (kthread+0x7c/0x84) from [<c0105a78>] (kernel_thread_exit+0x0/0x8)
Click to expand...
Click to collapse
So, I proceeded to turn e2fsck on it, but there are many, many, many problems:
~ # e2fsck -n /dev/block/mmcblk0p24
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p24 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 15288 was part of the orphaned inode list. IGNORED.
Inode 15288 is in use, but has dtime set. Fix? no
Inode 15288 has a extra size (3715) which is invalid
Fix? no
Special (device/socket/fifo) inode 15288 has non-zero size. Fix? no
Inode 15289 is in use, but has dtime set. Fix? no
Inode 15289 has imagic flag set. Clear? no
Inode 15289 has a extra size (14485) which is invalid
Fix? no
Inode 15290 is in use, but has dtime set. Fix? no
Inode 15290 has imagic flag set. Clear? no
Inode 15290 has a extra size (15464) which is invalid
Fix? no
Inode 15291 is in use, but has dtime set. Fix? no
Inode 15291 has imagic flag set. Clear? no
Inode 15291 has a extra size (16965) which is invalid
Fix? no
Inode 15292 is in use, but has dtime set. Fix? no
Inode 15292 has a extra size (18435) which is invalid
Fix? no
Inode 15293 is in use, but has dtime set. Fix? no
Inode 15293 has a extra size (19452) which is invalid
Fix? no
Inode 15294 is in use, but has dtime set. Fix? no
Inode 15294 has a extra size (20347) which is invalid
Fix? no
Inode 15295 is in use, but has dtime set. Fix? no
Inode 15295 has a extra size (21139) which is invalid
Fix? no
Inode 15296 is in use, but has dtime set. Fix? no
Inode 15296 has a extra size (23218) which is invalid
Fix? no
Inode 15297 is in use, but has dtime set. Fix? no
Inode 15297 has imagic flag set. Clear? no
Inode 15297 has a extra size (25720) which is invalid
Fix? no
Inode 15298 is in use, but has dtime set. Fix? no
Inode 15298 has imagic flag set. Clear? no
Inode 15298 has a extra size (29073) which is invalid
Fix? no
Inode 15299 is in use, but has dtime set. Fix? no
Inode 15299 has imagic flag set. Clear? no
Inode 15299 has a extra size (33375) which is invalid
Fix? no
Inode 15300 is in use, but has dtime set. Fix? no
Inode 15300 has a extra size (38067) which is invalid
Fix? no
Inode 15301 is in use, but has dtime set. Fix? no
Inode 15301 has a extra size (41538) which is invalid
Fix? no
Inode 15302 is in use, but has dtime set. Fix? no
Inode 15302 has imagic flag set. Clear? no
Inode 15302 has a extra size (43632) which is invalid
Fix? no
Inode 15303 is in use, but has dtime set. Fix? no
Inode 15303 has imagic flag set. Clear? no
Inode 15303 has a extra size (44940) which is invalid
Fix? no
Inode 15304 is in use, but has dtime set. Fix? no
Inode 15304 has imagic flag set. Clear? no
Inode 15304 has a extra size (46293) which is invalid
Fix? no
Inode 15305 is in use, but has dtime set. Fix? no
Inode 15305 has imagic flag set. Clear? no
Inode 15305 has a extra size (47549) which is invalid
Fix? no
Inode 15306 is in use, but has dtime set. Fix? no
Inode 15306 has imagic flag set. Clear? no
Inode 15306 has a extra size (49411) which is invalid
Fix? no
Inode 15307 is in use, but has dtime set. Fix? no
Inode 15307 has a extra size (51383) which is invalid
Fix? no
Special (device/socket/fifo) inode 15307 has non-zero size. Fix? no
Inode 15308 is in use, but has dtime set. Fix? no
Inode 15308 has a extra size (53012) which is invalid
Fix? no
Special (device/socket/fifo) inode 15308 has non-zero size. Fix? no
Inode 15309 is in use, but has dtime set. Fix? no
Inode 15309 has a extra size (53685) which is invalid
Fix? no
Inode 15310 is in use, but has dtime set. Fix? no
Inode 15310 has a extra size (54672) which is invalid
Fix? no
Inode 15288, i_size is 103938212115248, should be 0. Fix? no
Inode 15288, i_blocks is 54520, should be 0. Fix? no
Inode 15289 has compression flag set on filesystem without compression support. Clear? no
Inode 15289 has INDEX_FL flag set but is not a directory.
Clear HTree index? no
Inode 15289 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
HTREE directory inode 15289 has an invalid root node.
Clear HTree index? no
Inode 15289, i_size is 1469282542499554, should be 0. Fix? no
Inode 15289, i_blocks is 341837, should be 0. Fix? no
Inode 15290 has compression flag set on filesystem without compression support. Clear? no
Inode 15290 has INDEX_FL flag set but is not a directory.
Clear HTree index? no
Inode 15290 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
HTREE directory inode 15290 has an invalid root node.
Clear HTree index? no
Inode 15290, i_size is 1473401416137182, should be 0. Fix? no
Inode 15290, i_blocks is 342625, should be 0. Fix? no
Inode 15291 has compression flag set on filesystem without compression support. Clear? no
Inode 15291 has INDEX_FL flag set but is not a directory.
Clear HTree index? no
Inode 15291 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
HTREE directory inode 15291 has an invalid root node.
Clear HTree index? no
Inode 15291, i_size is 1479702133161773, should be 0. Fix? no
Inode 15291, i_blocks is 343944, should be 0. Fix? no
Inode 15292 has illegal block(s). Clear? no
Illegal block #0 (345615) in inode 15292. IGNORED.
Illegal block #1 (345628) in inode 15292. IGNORED.
Illegal block #2 (345728) in inode 15292. IGNORED.
Illegal block #3 (345756) in inode 15292. IGNORED.
Illegal block #4 (345789) in inode 15292. IGNORED.
Illegal block #5 (345808) in inode 15292. IGNORED.
Illegal block #6 (345826) in inode 15292. IGNORED.
Illegal block #7 (345841) in inode 15292. IGNORED.
Illegal block #8 (345857) in inode 15292. IGNORED.
Illegal block #9 (345874) in inode 15292. IGNORED.
Illegal block #10 (345887) in inode 15292. IGNORED.
Too many illegal blocks in inode 15292.
Clear inode? no
Suppress messages? no
Illegal block #11 (345904) in inode 15292. IGNORED.
Illegal indirect block (345923) in inode 15292. IGNORED.
Illegal double indirect block (345932) in inode 15292. IGNORED.
Illegal triple indirect block (345946) in inode 15292. IGNORED.
Error while iterating over blocks in inode 15292: Illegal triply indirect block found
e2fsck: aborted
~ #
Click to expand...
Click to collapse
Not sure if I should allow fsck to fix these. Usually, on Linux, this many errors mean a format of the partition. I don't know for sure what the parition is but it looks like Samsung system (Gingerbread) stuff:
~ # mount /dev/block/mmcblk0p24 /mnt -o ro
~ # ls mnt
CSCFiles.txt build.prop lost+found
CSCVersion.txt csc media
SW_Configuration.xml etc tts
T9DB fonts usr
app framework vsc
bin lib xbin
Click to expand...
Click to collapse
Any thoughts on next steps? If I format the partition I'm pretty much out of an OS. I was not able to flash CM 10.1 nor CM 9.1 as they would boot loop. Suspecting the partition problems, but not sure. It could be a much deeper promlem with underlying media. Is this parition on the removable CF card, or internal to the phone?
Thanks,Sorry so long. Trying to be thorough.
Go grab twrp 2.6.0.4, its 4.3 compatible and won't give u any issues like cwm does, plus its easier to use, if u need help with it pm me
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Go grab twrp 2.6.0.4, its 4.3 compatible and won't give u any issues like cwm does, plus its easier to use, if u need help with it pm me
Click to expand...
Click to collapse
The same thing seems to be happening with TWRP 2.6.0.4. It never finishes backing up. The twirly bar at the bottom just keeps going and going.. dmesg has similar errors as I was getting with CWM:
Code:
<6>[ 338.231903] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 338.237457] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 338.245483] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
<6>[ 338.266418] zcache: destroyed pool id=1, cli_id=65535
<6>[ 338.312561] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 338.318054] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 338.337127] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
<6>[ 338.343261] zcache: destroyed pool id=1, cli_id=65535
<4>[ 338.400177] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 338.413269] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 338.418823] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 338.426849] SELinux: initialized (dev mmcblk0p24, type ext4), uses xattr
<6>[ 338.447357] zcache: destroyed pool id=1, cli_id=65535
<6>[ 338.498107] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 338.503784] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 338.512145] SELinux: initialized (dev mmcblk0p27, type ext4), uses xattr
<6>[ 338.518615] zcache: destroyed pool id=1, cli_id=65535
<6>[ 339.817138] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 339.822662] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 339.847167] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
<4>[ 349.649108] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 349.682159] zcache: created ephemeral tmem pool, id=2, client=65535
<6>[ 349.687835] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 349.695648] SELinux: initialized (dev mmcblk0p24, type ext4), uses xattr
<2>[ 353.107177] EXT4-fs error (device mmcblk0p24): ext4_init_inode_table:1296: comm ext4lazyinit: Something is wrong with group 0
<2>[ 353.107238] Used itable blocks: 479itable unused count: 0
<2>[ 353.107269]
<3>[ 353.655029] Aborting journal on device mmcblk0p24-8.
<2>[ 353.696502] EXT4-fs (mmcblk0p24): Remounting filesystem read-only
<3>[ 362.501586] [TSP] Calibration End!!!!!!
<3>[ 362.504302] [TSP] Clearing unused slots
<3>[ 362.509887] [TSP] Calibration!!!!!!
<3>[ 362.515777] [TSP] Calibration End!!!!!!
<3>[ 362.518707] [TSP] Clearing unused slots
<6>[ 370.498046] max17040_set_property: charger full state!
<6>[ 410.588012] max17040_set_property: charger full state!
<6>[ 450.668121] max17040_set_property: charger full state!
<6>[ 450.672363] max17040_adjust_fullsoc : full_soc = 9641
<6>[ 456.575805] zcache: created ephemeral tmem pool, id=3, client=65535
<6>[ 456.581359] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 456.607147] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
<6>[ 456.613250] zcache: destroyed pool id=3, cli_id=65535
<6>[ 456.689239] zcache: created ephemeral tmem pool, id=3, client=65535
<6>[ 456.694732] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: (null)
<7>[ 456.710479] SELinux: initialized (dev mmcblk0p27, type ext4), uses xattr
<6>[ 456.716491] zcache: destroyed pool id=3, cli_id=65535
<6>[ 456.817138] zcache: destroyed pool id=2, cli_id=65535
<3>[ 480.577301] INFO: task jbd2/mmcblk0p24:205 blocked for more than 120 seconds.
<3>[ 480.583831] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 480.607147] jbd2/mmcblk0p24 D c07b1dc8 0 205 2 0x00000000
<4>[ 480.612762] [<c07b1dc8>] (__schedule+0x5cc/0x788) from [<c02d9c10>] (jbd2_journal_commit_transaction+0x1e0/0x1484)
<4>[ 480.637969] [<c02d9c10>] (jbd2_journal_commit_transaction+0x1e0/0x1484) from [<c02de7dc>] (kjournald2+0xa4/0x204)
<4>[ 480.657165] [<c02de7dc>] (kjournald2+0xa4/0x204) from [<c01a8234>] (kthread+0x7c/0x88)
<4>[ 480.664306] [<c01a8234>] (kthread+0x7c/0x88) from [<c0105e80>] (kernel_thread_exit+0x0/0x8)
<6>[ 490.748779] max17040_set_property: charger full state!
<6>[ 530.879364] max17040_set_property: charger full state!
<6>[ 530.883728] max17040_adjust_fullsoc : full_soc = 9630
<6>[ 570.908752] max17040_set_property: charger full state!
Something seems messed up with the filesystem or underlying media on mmcblk0p24. Any other ideas?
UPDATE: Thought I'd make a tar file of the contents of p24 so if I format it, I can untar everything back to the partition. tar failed with an error on file csc/sales_code.dat so I added a --exclude for that file and it seems to work. That's no guarantee the contents of all the files aren't screwed up but it's better than nothing. Question is, how to I format the partition? It mounts as ext4 but there is no mkfs.ext4 utility in the recovery boot. I could format the partition and try to flash CM-10x but not sure if that makes sense.
eris170 said:
The same thing seems to be happening with TWRP 2.6.0.4. It never finishes backing up. The twirly bar at the bottom just keeps going and going.. dmesg has similar errors as I was getting with CWM:
Code:
[ 338.231903] zcache: created ephemeral tmem pool, id=1, client=65535
[ 338.237457] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: (null)
[ 338.245483] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
[ 338.266418] zcache: destroyed pool id=1, cli_id=65535
[ 338.312561] zcache: created ephemeral tmem pool, id=1, client=65535
[ 338.318054] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
[ 338.337127] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
[ 338.343261] zcache: destroyed pool id=1, cli_id=65535
[ 338.400177] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
[ 338.413269] zcache: created ephemeral tmem pool, id=1, client=65535
[ 338.418823] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts: (null)
[ 338.426849] SELinux: initialized (dev mmcblk0p24, type ext4), uses xattr
[ 338.447357] zcache: destroyed pool id=1, cli_id=65535
[ 338.498107] zcache: created ephemeral tmem pool, id=1, client=65535
[ 338.503784] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: (null)
[ 338.512145] SELinux: initialized (dev mmcblk0p27, type ext4), uses xattr
[ 338.518615] zcache: destroyed pool id=1, cli_id=65535
[ 339.817138] zcache: created ephemeral tmem pool, id=1, client=65535
[ 339.822662] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
[ 339.847167] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
[ 349.649108] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
[ 349.682159] zcache: created ephemeral tmem pool, id=2, client=65535
[ 349.687835] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts: (null)
[ 349.695648] SELinux: initialized (dev mmcblk0p24, type ext4), uses xattr
[ 353.107177] EXT4-fs error (device mmcblk0p24): ext4_init_inode_table:1296: comm ext4lazyinit: Something is wrong with group 0
[ 353.107238] Used itable blocks: 479itable unused count: 0
[ 353.107269]
[ 353.655029] Aborting journal on device mmcblk0p24-8.
[ 353.696502] EXT4-fs (mmcblk0p24): Remounting filesystem read-only
[ 362.501586] [TSP] Calibration End!!!!!!
[ 362.504302] [TSP] Clearing unused slots
[ 362.509887] [TSP] Calibration!!!!!!
[ 362.515777] [TSP] Calibration End!!!!!!
[ 362.518707] [TSP] Clearing unused slots
[ 370.498046] max17040_set_property: charger full state!
[ 410.588012] max17040_set_property: charger full state!
[ 450.668121] max17040_set_property: charger full state!
[ 450.672363] max17040_adjust_fullsoc : full_soc = 9641
[ 456.575805] zcache: created ephemeral tmem pool, id=3, client=65535
[ 456.581359] EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: (null)
[ 456.607147] SELinux: initialized (dev mmcblk0p21, type ext4), uses xattr
[ 456.613250] zcache: destroyed pool id=3, cli_id=65535
[ 456.689239] zcache: created ephemeral tmem pool, id=3, client=65535
[ 456.694732] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: (null)
[ 456.710479] SELinux: initialized (dev mmcblk0p27, type ext4), uses xattr
[ 456.716491] zcache: destroyed pool id=3, cli_id=65535
[ 456.817138] zcache: destroyed pool id=2, cli_id=65535
[ 480.577301] INFO: task jbd2/mmcblk0p24:205 blocked for more than 120 seconds.
[ 480.583831] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 480.607147] jbd2/mmcblk0p24 D c07b1dc8 0 205 2 0x00000000
[ 480.612762] [] (__schedule+0x5cc/0x788) from [] (jbd2_journal_commit_transaction+0x1e0/0x1484)
[ 480.637969] [] (jbd2_journal_commit_transaction+0x1e0/0x1484) from [] (kjournald2+0xa4/0x204)
[ 480.657165] [] (kjournald2+0xa4/0x204) from [] (kthread+0x7c/0x88)
[ 480.664306] [] (kthread+0x7c/0x88) from [] (kernel_thread_exit+0x0/0x8)
[ 490.748779] max17040_set_property: charger full state!
[ 530.879364] max17040_set_property: charger full state!
[ 530.883728] max17040_adjust_fullsoc : full_soc = 9630
[ 570.908752] max17040_set_property: charger full state!
Something seems messed up with the filesystem or underlying media on mmcblk0p24. Any other ideas?
UPDATE: Thought I'd make a tar file of the contents of p24 so if I format it, I can untar everything back to the partition. tar failed with an error on file csc/sales_code.dat so I added a --exclude for that file and it seems to work. That's no guarantee the contents of all the files aren't screwed up but it's better than nothing. Question is, how to I format the partition? It mounts as ext4 but there is no mkfs.ext4 utility in the recovery boot. I could format the partition and try to flash CM-10x but not sure if that makes sense.
Click to expand...
Click to collapse
Try using a program like titanium backup ( I use Pro ) and save your apps+ data + system data ( messages / Bookmarks / wifi aps etc ) to an external card. Then, Odin the stock Image which will reformat and repair things. Afterwards, Odin twrp ( not cwm as it likely corrupted partitions to begin with) and reflash your rom. After the rom is good to go, restore all non system apps and data along with the titanium backed up settings / messages. If you have the pro version, it's executed as a batch and restores it all without pushing a single button after selecting what you want to restore. The whole process to restore only takes about 5 minutes. I always clean flash all roms and restore with titanium. It ensures no issues are brought along from the old rom
Sent from my SGH-T889 using xda app-developers app
pyraxiate;45142866 Afterwards said:
Jeezes what happened to CWM? It didn't always suck. ... installing Titanium.. will report back later.
Thanks for the reply.
Click to expand...
Click to collapse
What's the difference between flashing the stock ROM and just using CM-10.x? Also, does it matter which stock ROM should I use? UVLDE, UVLE1, UVLH1 ??? My Baseband version is T989 UVLDH right now (Android 2.3.6)
Ended up tarring up the files on the partition, formatting it with mke2fs and then using tune2fs to get the FS features worked out. Once it was mounting as ext4, I untarred the files back and all good now.
eris170 said:
Ended up tarring up the files on the partition, formatting it with mke2fs and then using tune2fs to get the FS features worked out. Once it was mounting as ext4, I untarred the files back and all good now.
Click to expand...
Click to collapse
Glad to hear you are back up and running ! I used to be an avid cwm user but fit the last 4 devices I've stuck with twrp. Cwm had too many issues restoring backups for me, along with not letting me restore backups I made using earlier versions after upgrading cwm. Twrp hasn't given me any issues at all changing between versions. On my note 2, I'm constantly swapping between 2 different roms depending on whether I need wifi calling at the time or not.
Sent from my SGH-T889 using xda app-developers app
Related
After installing a couple apps from the market, my Incredible rebooted itself and is now stuck in a boot loop with issues reading/writing the internal partitions.
The following output from dmesg seems like it's indicating damaged internal storage:
Code:
<3>[ 6.975494] mmcblk0: error -110 transferring data, sector 1557560, nr 12, card status 0x4000d00
<3>[ 6.975646] end_request: I/O error, dev mmcblk0, sector 1557560
<3>[ 6.975860] end_request: I/O error, dev mmcblk0, sector 1557562
<3>[ 6.975982] end_request: I/O error, dev mmcblk0, sector 1557564
<3>[ 6.976196] end_request: I/O error, dev mmcblk0, sector 1557566
<3>[ 6.976318] end_request: I/O error, dev mmcblk0, sector 1557568
<3>[ 6.976501] end_request: I/O error, dev mmcblk0, sector 1557570
<3>[ 6.976684] Aborting journal on device mmcblk0p2.
<0>[ 6.977142] journal commit I/O error
Anyone else run into this and successfully recover from it?
CWM won't format the partition and e2fsck is unsuccessful as well. I've updated with RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe, without much effect.
Code:
~ # e2fsck /dev/block/mmcblk0p1
e2fsck /dev/block/mmcblk0p1
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p1: recovering journal
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p1
~ # mke2fs -n /dev/block/mmcblk0p1
mke2fs -n /dev/block/mmcblk0p1
mke2fs 1.40.8 (13-Mar-2008)
Warning: 256-byte inodes not usable on older systems
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
48672 inodes, 194560 blocks
9728 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=201326592
6 block groups
32768 blocks per group, 32768 fragments per group
8112 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
~ # e2fsck -b 32768 /dev/block/mmcblk0p1
e2fsck -b 32768 /dev/block/mmcblk0p1
e2fsck 1.41.6 (30-May-2009)
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/block/mmcblk0p1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p1
Sigh... bricked for good?
Brian
Hey everyone,
I am having a strange problem with my sd-ext (ext4) partition for some time now.
The ROM I am using is ICS for Desire by Sandvold (Amarullz and a2sd), but I don't know whether this is strictly ROM related or not.
I have been getting some mass FCs over and over again, across different versions flashed after full wipes.
Today I found out that the problem is that the sd-ext partition is not properly mounted (read-only), but here is the weird part: it is properly mounted (read-write) using the recovery and is also properly mounted before I unlock the sim-card.
When I unlock the sim-card or otherwise change the connectivity (WLAN, mobile data, airplane mode) it remounts sd-ext as read-only.
I have already tried reformatting and repartioning the sd-card.
Any idea why the system is doing that or how I can prevent that from happening?
Thanks
\Update1:
Here is a part of dmesg, showing the error when I unlock the sim-card after a fresh reboot:
Code:
<6>[ 182.512451] active wake lock PowerManagerService
<6>[ 182.512481] active wake lock vbus_present
<6>[ 182.512481] active wake lock SMD_DS, time left 35
<6>[ 182.512481] [R] early_suspend end
<6>[ 190.756866] batt: 74%, 3884 mV, 290 mA (210 avg), 29.8 C, 1008 mAh
<3>[ 191.665740] mmc1: Data CRC error
<3>[ 191.665954] msmsdcc_data_err: opcode 0x00000019
<3>[ 191.666168] msmsdcc_data_err: blksz 512, blocks 16
<3>[ 191.666595] mmc1: DMA channel flushed (0x80000004)
<3>[ 191.666839] Flush data: 0000c003 3b2d8018 00000000 00400040 00370035 00008003
<6>[ 191.667266] mmc1: Controller has been re-initialiazed
<3>[ 191.672515] mmcblk0: error -84 transferring data, sector 6710376, nr 16, card status 0x900
<3>[ 191.672973] mmc1: Data timeout
<6>[ 191.673217] mmc1: Controller has been re-initialiazed
<3>[ 191.673797] end_request: I/O error, dev mmcblk0, sector 6710376
<3>[ 191.674041] end_request: I/O error, dev mmcblk0, sector 6710384
<3>[ 191.679138] Aborting journal on device mmcblk0p2-8.
<0>[ 191.687255] journal commit I/O error
<2>[ 191.726745] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:276: Detected aborted journal
<2>[ 191.727478] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
<3>[ 191.984802] binder: 1268: binder_alloc_buf, no vma
<6>[ 191.985046] binder: 206:339 transaction failed 29201, size 4-0
<6>[ 191.985412] binder: send failed reply for transaction 79996 to 1268:1268
The weird thing is that I have been running the phone without any problem in airplane mode + WLAN for a whole day, until I tried to reactivate mobile connection again and do some tests with it.
It seems that the system only has a problem with the journal when it uses the mobile connection.
\Update2:
Here the dmesg message before I unlock the sim-card. No error message for sd-ext:
Code:
<6>[ 13.084991] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
4EXT is also unable to find any errors with the sd-ext partition (I have used the recovery to format and partition the sd-card).
\Update3:
Ok I just reformatted and repartitioned the sdcard again using gparted and reflashed the ROM with a full wipe.
I am getting the same error again.
Anyone else have a problem with USB host mode and copying big files?
If so, can we fix this?
I have tried formatting my drive in FAT32,NTFS, and ext2. But the result is always the same, the drive dies if I copy a file bigger than 30 or 40 MB. I have tried stock, Faux123, and francoKernel as well.
The drive doesn't die at a specific MB each time, but it is generally around 30 MB but sometimes makes it to 80 or even 140 MB one time. I am trying to off-load some 700MB movies.
Here is the kernel message error:
<6>[ 1920.842529] max17040 4-0036: online = 1 vcell = 3547500 soc = 22 status = 3 health = 1 temp = 370 charger status = 0
<3>[ 1926.574005] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.594299] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.649810] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1927.740753] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
<6>[ 1927.773895] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
<6>[ 1927.938781] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
<3>[ 1968.389251] L3 CUSTOM SRESP error with SOURCEMM2 info=0x84
<4>[ 1968.389434] ------------[ cut here ]------------
<4>[ 1968.389739] WARNING: at arch/arm/mach-omap2/omap_l3_noc.c:130 l3_interrupt_handler+0x31c/0x360()
<4>[ 1968.390045] L3 custom sresp error
<4>[ 1968.390197] Modules linked in:
<4>[ 1968.390686] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 1968.390991] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 1968.391326] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0074898>] (l3_interrupt_handler+0x31c/0x360)
<4>[ 1968.391632] [<c0074898>] (l3_interrupt_handler+0x31c/0x360) from [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178)
<4>[ 1968.391967] [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178) from [<c00d4760>] (handle_irq_event+0x3c/0x5c)
<4>[ 1968.392150] [<c00d4760>] (handle_irq_event+0x3c/0x5c) from [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164)
<4>[ 1968.392456] [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164) from [<c00d3f50>] (generic_handle_irq+0x2c/0x40)
<4>[ 1968.392791] [<c00d3f50>] (generic_handle_irq+0x2c/0x40) from [<c004904c>] (asm_do_IRQ+0x4c/0xac)
<4>[ 1968.393096] [<c004904c>] (asm_do_IRQ+0x4c/0xac) from [<c004eb08>] (__irq_svc+0x48/0xe4)
<4>[ 1968.393402] Exception stack(0xc0799f28 to 0xc0799f70)
<4>[ 1968.393554] 9f20: c0799f70 3b9aca00 4c534d85 000001ca 4c4bda2c 000001ca
<4>[ 1968.393859] 9f40: 000003ff c1192210 8000406a 412fc09a 00000000 00000000 00000000 c0799f70
<4>[ 1968.394042] 9f60: c007c690 c0068380 00000013 ffffffff
<4>[ 1968.394348] [<c004eb08>] (__irq_svc+0x48/0xe4) from [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4)
<4>[ 1968.394683] [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4) from [<c03af838>] (cpuidle_idle_call+0x94/0x118)
<4>[ 1968.394989] [<c03af838>] (cpuidle_idle_call+0x94/0x118) from [<c0050538>] (cpu_idle+0xbc/0xfc)
<4>[ 1968.395172] [<c0050538>] (cpu_idle+0xbc/0xfc) from [<c00088ac>] (start_kernel+0x298/0x2e8)
<4>[ 1968.395477] [<c00088ac>] (start_kernel+0x298/0x2e8) from [<80008040>] (0x80008040)
<4>[ 1968.395782] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 1968.396087] ---[ end trace 33de6ebe35ad56b6 ]---
<6>[ 1970.874023] max17040 4-0036: online = 1 vcell = 3532500 soc = 22 status = 3 health = 1 temp = 380 charger status = 0
<6>[ 1993.138793] usb 1-1: reset high speed USB device number 2 using musb-hdrc
<6>[ 2000.347503] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<6>[ 2000.347717] usb 1-1: USB disconnect, device number 2
<4>[ 2000.350708] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2000.351989] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2001.361236] max17040 4-0036: online = 1 vcell = 3585000 soc = 21 status = 2 health = 1 temp = 380 charger status = 0
<6>[ 2003.287322] sd 0:0:0:0: Device offlined - not ready after error recovery
<6>[ 2003.287597] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287628] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287658] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.287689] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 00 3f 00 00 08 00
<3>[ 2003.287719] end_request: I/O error, dev sda, sector 63
<3>[ 2003.287750] Buffer I/O error on device sda1, logical block 0
<4>[ 2003.287780] lost page write due to I/O error on sda1
<6>[ 2003.289154] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.289459] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 21 e7 00 00 08 00
<3>[ 2003.291625] end_request: I/O error, dev sda, sector 8679
<3>[ 2003.291778] Buffer I/O error on device sda1, logical block 1077
<4>[ 2003.292114] EXT4-fs warning (device sda1): ext4_end_bio:258: I/O error writing to inode 13 (offset 217088 size 4096 starting block 1085)
<3>[ 2003.297576] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.297851] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.299560] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.299743] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.300415] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.300720] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301116] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.301391] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301727] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.302032] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.302398] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.302703] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.303802] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.304168] EXT4-fs error (device sda1): ext4_free_branches:4377: inode #13: block 536: comm libestool.so: Read failure
<3>[ 2003.305358] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.305755] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.306365] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.306518] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.336242] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.336364] EXT4-fs error (device sda1): ext4_find_entry:934: inode #2: comm libestool.so: reading directory lblock 0
<3>[ 2003.411834] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.412017] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm ngs.android.pop: unable to read itable block
<2>[ 2003.412414] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.412567] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2008.311859] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.312194] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm bdi-default: unable to read itable block
<3>[ 2008.313110] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.313415] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm bdi-default: unable to read itable block
<6>[ 2025.582702] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2026.233337] usb 1-1: new high speed USB device number 3 using musb-hdrc
<3>[ 2026.388244] usb 1-1: device v090c p6200 is not supported
<6>[ 2026.388427] usb 1-1: New USB device found, idVendor=090c, idProduct=6200
<6>[ 2026.388763] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 2026.389068] usb 1-1: Product: Generic USB2.0 card
<6>[ 2026.389221] usb 1-1: Manufacturer: Silicon Motion, Inc.
<6>[ 2026.389373] usb 1-1: SerialNumber: 12345678901234567890
<6>[ 2026.392089] scsi1 : usb-storage 1-1:1.0
<6>[ 2030.177124] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2030.180053] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2030.181335] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2031.197509] max17040 4-0036: online = 1 vcell = 3600000 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<6>[ 2034.948303] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2035.182495] usb 1-1: USB disconnect, device number 3
<6>[ 2045.606109] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2045.609100] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2045.610321] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2046.627288] max17040 4-0036: online = 1 vcell = 3602500 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<4>[ 2048.832824] ------------[ cut here ]------------
<4>[ 2048.832916] WARNING: at drivers/usb/musb/musb_host.c:125 musb_h_tx_flush_fifo+0x78/0x84()
<4>[ 2048.833068] Could not flush host TX2 fifo: csr: 2003
<4>[ 2048.833160] Modules linked in:
<4>[ 2048.833404] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 2048.833526] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 2048.833679] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84)
<4>[ 2048.833862] [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84) from [<c0367724>] (musb_cleanup_urb+0xb0/0xd4)
<4>[ 2048.834014] [<c0367724>] (musb_cleanup_urb+0xb0/0xd4) from [<c0367990>] (musb_urb_dequeue+0xfc/0x13c)
<4>[ 2048.834167] [<c0367990>] (musb_urb_dequeue+0xfc/0x13c) from [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac)
<4>[ 2048.834350] [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac) from [<c035d938>] (usb_stor_stop_transport+0x48/0x60)
<4>[ 2048.834442] [<c035d938>] (usb_stor_stop_transport+0x48/0x60) from [<c035c36c>] (command_abort+0x80/0x84)
<4>[ 2048.834564] [<c035c36c>] (command_abort+0x80/0x84) from [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c)
<4>[ 2048.834716] [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c) from [<c00b227c>] (kthread+0x80/0x88)
<4>[ 2048.834899] [<c00b227c>] (kthread+0x80/0x88) from [<c0050148>] (kernel_thread_exit+0x0/0x8)
<4>[ 2048.835052] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 2048.835144] ---[ end trace 33de6ebe35ad56b7 ]---
<6>[ 2048.837768] scsi 1:0:0:0: Device offlined - not ready after error recovery
I found a thread on TI site for the OMAP4460 that discusses an error like mine but the signature is not the same, seems there they were having a problem with the the TCP/IP stack becoming corrupted because the processor was allocating memory too fast. Something like that is happening here. All I really know is it has to do with the handling of the L3 cache.
I think this may have to do with the cpu trying to idle when it should not.
What kind of drive are you using? If its a portable usb hard drive then this could be a power issue.
It's not a portable HD, just usb sd card reader.
With further investigation I have found that the problem might stem from the x-loader being mismatched to the kernel, which is part of the bootloader.
I tried different bootloaders, but none made a difference.
Finally, I tried a different USB OTG cable, a slightly more expensive one, and it worked.
Hi. I have Nexus 7 2013 WiFi 32Gb. FLO 04.02 bootloader. Stock 4.4.2 android with root and teamwin.
Recently, I start download file and after that my nexus 7 rebooted. And it stuck on Google boot screen. I try to run teamwin, but it also stuck on Teamwin logo.
In fastboot mode i get:
Code:
> sudo fastboot -u format cache
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 89.945s
> sudo fastboot -w
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.015s
> sudo fastboot flash bootloader bootloader-flo-flo-04.02.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.068s
e2fsck:
Code:
e2fsck /dev/block/mmcblk0
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0
Filesystem mounted or opened exclusively by another program?
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p30
Filesystem mounted or opened exclusively by another program?
mount:
Code:
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
dmesg: pastebin. com/j4hnHkwg
PS. Can't insert links, and can't insert dmesg here, message are too long... =(
Some other logs:
Code:
<4>[ 1013.807952] ------------[ cut here ]------------
<4>[ 1013.807952] WARNING: at drivers/mmc/host/msm_sdcc.c:3538 msmsdcc_disable+0x84/0x10c()
<4>[ 1013.807952] mmc0: msmsdcc_disable: failed with error -22
<4>[ 1013.807983] [<c010cbc8>] (unwind_backtrace+0x0/0x11c) from [<c01730e8>] (warn_slowpath_common+0x48/0x60)
<4>[ 1013.807983] [<c01730e8>] (warn_slowpath_common+0x48/0x60) from [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 1013.807983] [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0659b18>] (msmsdcc_disable+0x84/0x10c)
<4>[ 1013.808013] [<c0659b18>] (msmsdcc_disable+0x84/0x10c) from [<c0646130>] (mmc_release_host+0x4c/0xb0)
<4>[ 1013.808013] [<c0646130>] (mmc_release_host+0x4c/0xb0) from [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0)
<4>[ 1013.808044] [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0) from [<c0657648>] (mmc_queue_thread+0xd4/0x19c)
<4>[ 1013.808044] [<c0657648>] (mmc_queue_thread+0xd4/0x19c) from [<c018f804>] (kthread+0x84/0x90)
<4>[ 1013.808044] [<c018f804>] (kthread+0x84/0x90) from [<c0107228>] (kernel_thread_exit+0x0/0x8)
<4>[ 1013.808074] ---[ end trace c0d52a61d7a24c7c ]---
<6>[ 1013.808074] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1013.808074] mmc0: RPM: runtime_status=0, usage_count=0, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<4>[ 1013.901123] ------------[ cut here ]------------
<4>[ 1013.901245] WARNING: at drivers/mmc/host/msm_sdcc.c:3510 msmsdcc_enable+0x108/0x144()
<4>[ 1013.901306] mmc0: msmsdcc_enable: failed with error -22
<4>[ 1013.901397] [<c010cbc8>] (unwind_backtrace+0x0/0x11c) from [<c01730e8>] (warn_slowpath_common+0x48/0x60)
<4>[ 1013.901519] [<c01730e8>] (warn_slowpath_common+0x48/0x60) from [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 1013.901580] [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c) from [<c065db64>] (msmsdcc_enable+0x108/0x144)
<4>[ 1013.901702] [<c065db64>] (msmsdcc_enable+0x108/0x144) from [<c0646018>] (__mmc_claim_host+0x170/0x180)
<4>[ 1013.901824] [<c0646018>] (__mmc_claim_host+0x170/0x180) from [<c0656d54>] (mmc_blk_issue_rq+0x34/0x4c0)
<4>[ 1013.901916] [<c0656d54>] (mmc_blk_issue_rq+0x34/0x4c0) from [<c0657648>] (mmc_queue_thread+0xd4/0x19c)
<4>[ 1013.902038] [<c0657648>] (mmc_queue_thread+0xd4/0x19c) from [<c018f804>] (kthread+0x84/0x90)
<4>[ 1013.902130] [<c018f804>] (kthread+0x84/0x90) from [<c0107228>] (kernel_thread_exit+0x0/0x8)
<4>[ 1013.902221] ---[ end trace c0d52a61d7a24c7d ]---
<6>[ 1013.902343] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1013.902404] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<6>[ 1013.903350] sps:BAM 0x12402000 enabled: ver:0x5, number of pipes:6
<3>[ 1013.908935] mmcblk0: error -110 sending status command, retrying
<3>[ 1013.914428] mmcblk0: error -110 sending status command, retrying
<3>[ 1013.919891] mmcblk0: error -110 sending status command, aborting
<3>[ 1013.919982] end_request: I/O error, dev mmcblk0, sector 4718594
<3>[ 1013.920104] EXT4-fs (mmcblk0p30): unable to read superblock
<4>[ 1013.920104] ------------[ cut here ]------------
<4>[ 1013.920135] WARNING: at drivers/mmc/host/msm_sdcc.c:3538 msmsdcc_disable+0x84/0x10c()
<4>[ 1013.920135] mmc0: msmsdcc_disable: failed with error -22
<4>[ 1013.920135] [<c010cbc8>] (unwind_backtrace+0x0/0x11c) from [<c01730e8>] (warn_slowpath_common+0x48/0x60)
<4>[ 1013.920166] [<c01730e8>] (warn_slowpath_common+0x48/0x60) from [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 1013.920166] [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0659b18>] (msmsdcc_disable+0x84/0x10c)
<4>[ 1013.920166] [<c0659b18>] (msmsdcc_disable+0x84/0x10c) from [<c0646130>] (mmc_release_host+0x4c/0xb0)
<4>[ 1013.920196] [<c0646130>] (mmc_release_host+0x4c/0xb0) from [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0)
<4>[ 1013.920196] [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0) from [<c0657648>] (mmc_queue_thread+0xd4/0x19c)
<4>[ 1013.920227] [<c0657648>] (mmc_queue_thread+0xd4/0x19c) from [<c018f804>] (kthread+0x84/0x90)
<4>[ 1013.920227] [<c018f804>] (kthread+0x84/0x90) from [<c0107228>] (kernel_thread_exit+0x0/0x8)
<4>[ 1013.920227] ---[ end trace c0d52a61d7a24c7e ]---
<6>[ 1013.920227] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1013.920257] mmc0: RPM: runtime_status=0, usage_count=0, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<3>[ 703.888671] EXT4-fs (mmcblk0p30): unable to read superblock
<3>[ 7.323852] mmcblk0: error -110 sending stop command, original cmd response 0x940, card status 0x2400e40
umount: can't umount /dev/block/mmcblk0: Invalid argument
mmc0: msmsdcc_enable: failed with error -22
<3>[ 757.383453] end_request: I/O error, dev mmcblk0, sector 4718592
<6>[ 1364.750000] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1364.750091] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<6>[ 1364.751068] sps:BAM 0x12402000 enabled: ver:0x5, number of pipes:6
<3>[ 1364.756591] mmcblk0: error -110 sending status command, retrying
<3>[ 1364.762145] mmcblk0: error -110 sending status command, retrying
<3>[ 1364.767608] mmcblk0: error -110 sending status command, aborting
<3>[ 1364.767700] end_request: I/O error, dev mmcblk0, sector 4718592
<3>[ 1364.767791] end_request: I/O error, dev mmcblk0, sector 4718593
<3>[ 1364.767852] end_request: I/O error, dev mmcblk0, sector 4718594
<3>[ 1364.767974] end_request: I/O error, dev mmcblk0, sector 4718595
<3>[ 1364.768035] end_request: I/O error, dev mmcblk0, sector 4718596
<3>[ 1364.768127] end_request: I/O error, dev mmcblk0, sector 4718597
<3>[ 1364.768218] end_request: I/O error, dev mmcblk0, sector 4718598
<3>[ 1364.768310] end_request: I/O error, dev mmcblk0, sector 4718599
I have exactly the same problem. I wasn't doing anything - I just lifted the cover the other morning to find it sitting at the Google logo. Can it really be hosed? Are we SOL for warranty repair?
eecummings said:
I have exactly the same problem. I wasn't doing anything - I just lifted the cover the other morning to find it sitting at the Google logo. Can it really be hosed? Are we SOL for warranty repair?
Click to expand...
Click to collapse
Have you guys test the nexus root tool kit?
it's a wonderful piece of software..
it does helped alot my nexus 4 when it's half bricked...
Try flashing system images and see what happens?
Sent from my XT1032 using XDA Premium 4 mobile app
Hi, I've the exact same problem too.
Did you manage to solve it or did you have to send it back for repair?
Thanks,
Alessandro
I believe this is the same problem I have: Not being able to format my corrupted cache partition.
Since my tablet was not unlocked or rooted I can't seem to flash a ROM either, even stock.
1c3_5n0w said:
Try flashing system images and see what happens?
Click to expand...
Click to collapse
I can't flash or erase or format any partition. I get the same error after some period of timeout.
Hi All,
Anybody could help me coz got a bit of problem here.
Rom: stock GB 2.3.5 I8150XXKI8
It seems that everything is read-only except the external SD. After reboot, revert back to previous state.
Unable to go to recovery mode.
Done many success flashing in download mode ( flash stock,recovery) though and nothing. it just revert back to the previous state
Reformat usb storage also does not work.
Alot of apps force close.
Long pause at the samsung w logo.
mmcblk0p17 and mmcblk0p27 seems to have an error from below dmesg output.
Needs to confirm with anyone.
Thanks.
<3>[ 3.161895] init: MOUNT NAME /dev/block/mmcblk0p15
<3>[ 3.161925] init: SEC_DEVENC ***[/dev/block/mmcblk0p15][0]
<6>[ 3.181334] EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1
<3>[ 3.181395] init: MOUNT NAME /dev/block/mmcblk0p12
<3>[ 3.181426] init: SEC_DEVENC ***[/dev/block/mmcblk0p12][0]
<6>[ 3.186003] EXT4-fs (mmcblk0p12): barriers disabled
<6>[ 3.202056] EXT4-fs (mmcblk0p12): recovery complete
<6>[ 3.202697] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode. Opts: barrier=0
<3>[ 3.202758] init: MOUNT NAME /dev/block/mmcblk0p16
<3>[ 3.202758] init: SEC_DEVENC ***[/dev/block/mmcblk0p16][0]
<6>[ 3.205413] EXT4-fs (mmcblk0p16): barriers disabled
<3>[ 3.215056] init: [boot time] finish coldboot
<6>[ 3.216735] EXT4-fs (mmcblk0p16): recovery complete
<6>[ 3.217314] EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: barrier=0
<4>[ 3.220519] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.221129] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.238127] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.238738] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.248168] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.249205] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.258544] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.259154] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.271483] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 3.271514] mmc2: new high speed SDHC card at address 1234
<6>[ 3.271605] sdio_al mmc2:1234: Probing..
<6>[ 3.271605] sdio_al mmc2:1234: Not an SDIO card
<6>[ 3.271941] mmcblk1: mmc2:1234 SA16G 14.6 GiB
<6>[ 3.272124] mmcblk1: p1
<4>[ 3.276579] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.277220] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<3>[ 3.278319] init: [disk_config] :::: /dev/block/mmcblk0p27 (ext4)(opt (null)):::::
<3>[ 3.278349] init: internal_storage : ext_identify open
<3>[ 3.278380] init: internal_storage : ext_identify lseek
<3>[ 3.279234] init: internal_storage : ext_identify open
<3>[ 3.279265] init: internal_storage : ext_identify lseek
<3>[ 3.279295] init: MOUNT NAME /dev/block/mmcblk0p27
<3>[ 3.279326] init: SEC_DEVENC ***[/dev/block/mmcblk0p27][0]
<3>[ 3.279357] init: failed that mount s:'/dev/block/mmcblk0p27', t:'/efs', f:ext4 ,op null) (Device or resource busy)
<3>[ 3.279418] init: [disk_config] :::: /dev/block/mmcblk0p17 (ext4)(opt (null)):::::
<3>[ 3.279448] init: internal_storage : ext_identify open
<3>[ 3.279479] init: internal_storage : ext_identify lseek
<3>[ 3.280852] init: internal_storage : ext_identify open
<3>[ 3.280882] init: internal_storage : ext_identify lseek
<3>[ 3.282439] init: [disk_config] :::: fsck -> /dev/block/mmcblk0p17 (ext4):::::
<3>[ 3.282836] init: [disk_config] DEVENC : not mormal [0]
<3>[ 3.282836] init: [disk_config] DEVENC : fs_check with original dev_path
<3>[ 3.644621] mmc1 data status (0x8)
<3>[ 3.644652] mmc1: Data timeout opcode = 0x12
<3>[ 3.644682] mmc1: DMA channel flushed (0x80000004)
<3>[ 3.644682] Flush data: 0000c003 4f713000 00000000 00200040 00290028 00002003
<4>[ 3.645018] mmcblk0: retrying using single block read
<3>[ 4.017912] init: SEC_DEVENC check crypt status
<3>[ 4.017973] init: MOUNT NAME /dev/block/mmcblk0p17
<3>[ 4.017973] init: SEC_DEVENC ***[/dev/block/mmcblk0p17][1]
<3>[ 4.017973] init: SEC_DEVENC checkCrypt main
<3>[ 4.316953] mmc1 data status (0x8)
<3>[ 4.316953] mmc1: Data timeout opcode = 0x12
<3>[ 4.316984] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.316984] Flush data: 0000c003 4f713000 00000000 00200040 05b905b8 00002003
<4>[ 4.317320] mmcblk0: retrying using single block read
<3>[ 4.519804] mmc1 data status (0x8)
<3>[ 4.519834] mmc1: Data timeout opcode = 0x12
<3>[ 4.519865] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.519865] Flush data: 0000c003 4f713000 00000000 00200040 05b905b8 00002003
<4>[ 4.520170] mmcblk0: retrying using single block read
<3>[ 4.727903] mmc1 data status (0x8)
<3>[ 4.727903] mmc1: Data timeout opcode = 0x12
<3>[ 4.727934] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.727934] Flush data: 0000c003 4f713000 00000000 00200040 04690468 00002003
<4>[ 4.728300] mmcblk0: retrying using single block read
<3>[ 5.135984] mmc1 data status (0x8)
<3>[ 5.136015] mmc1: Data timeout opcode = 0x12
<3>[ 5.136045] mmc1: DMA channel flushed (0x80000004)
<3>[ 5.136045] Flush data: 0000c003 4f713000 00000000 00200040 00b900b8 00002003
<4>[ 5.136381] mmcblk0: retrying using single block read
<4>[ 5.233640] EXT4-fs (mmcblk0p17): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 5.234983] EXT4-fs (mmcblk0p17): recovery complete
<6>[ 5.235959] EXT4-fs (mmcblk0p17): mounted filesystem with ordered data mode. Opts: errors=continue
<3>[ 5.236020] init: SEC_DEVENC uncrypted parition mounted
<4>[ 5.237577] param_init !
<3>[ 5.237729] init: [boot time] processing action 0x3b6d8 (post-fs)
<3>[ 5.237760] init: [disk_config] :::: /dev/block/mmcblk0p28 (vfat)(opt (null)):::::
<3>[ 5.240323] init: oem_name (android )
<3>[ 5.244382] init: oem_name (android )
<3>[ 5.244474] init: [disk_config] :::: fsck -> /dev/block/mmcblk0p28 (vfat):::::
<3>[ 5.244901] init: [disk_config] DEVENC : not mormal [0]
<3>[ 5.244932] init: [disk_config] DEVENC : fs_check with original dev_path
<3>[ 5.599302] mmc1 data status (0x8)
<3>[ 5.599302] mmc1: Data timeout opcode = 0x12
<3>[ 5.599332] mmc1: DMA channel flushed (0x80000004)
<3>[ 5.599332] Flush data: 0000c003 4f713000 00000000 00200040 02690268 00002003
<4>[ 5.599698] mmcblk0: retrying using single block read
<3>[ 6.010587] mmc1 data status (0x8)
<3>[ 6.010587] mmc1: Data timeout opcode = 0x12
<3>[ 6.010617] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.010617] Flush data: 0000c003 4f713000 00000000 00200040 02790278 00002003
<4>[ 6.010984] mmcblk0: retrying using single block read
<3>[ 6.435544] mmc1 data status (0x8)
<3>[ 6.435544] mmc1: Data timeout opcode = 0x12
<3>[ 6.435574] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.435574] Flush data: 0000c003 4f713000 00000000 00200040 01b901b8 00002003
<4>[ 6.435910] mmcblk0: retrying using single block read
<3>[ 6.638852] mmc1 data status (0x8)
<3>[ 6.638883] mmc1: Data timeout opcode = 0x12
<3>[ 6.638883] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.638913] Flush data: 0000c003 4f713000 00000000 00200040 00b900b8 00002003
<4>[ 6.639249] mmcblk0: retrying using single block read
my internal memory was damaged. I flashed stock rom, entered it's recovery and formatted the internal memory. then installed cwm and installed custom rom. now everything is perfect.
ozgurakman said:
my internal memory was damaged. I flashed stock rom, entered it's recovery and formatted the internal memory. then installed cwm and installed custom rom. now everything is perfect.
Click to expand...
Click to collapse
Hi,
Thanks for the reply and good for you ozgurakman coz able to go to recovery mode. But I'm unable to go to recovery mode to repair the system though. Press the 3 recovery buttons. and just a screen flicker. It seem that my recovery corrupt also. Even after I reflash the recovery block only, still nada.
It seem that I'm running out options though. Anybody?
Did you tried to install cwm?
ozgurakman said:
Did you tried to install cwm?
Click to expand...
Click to collapse
yup also trying that one. also using the dd command in case the odin not working.
If dd command works, everything is fine. if dd command not working +Odin is not working, flashing via jtag is the only way.
ozgurakman said:
If dd command works, everything is fine. if dd command not working +Odin is not working, flashing via jtag is the only way.
Click to expand...
Click to collapse
the weird is that both dd and odin works. Also when i try to reboot it shutdown instead.
Will try to find shop that can do jtag. thanks
zaffrullah said:
the weird is that both dd and odin works. Also when i try to reboot it shutdown instead.
Will try to find shop that can do jtag. thanks
Click to expand...
Click to collapse
If I helped you, please press to thanks button
Last advise: try to different Odin version, different ops, different Rom.
Select to wipe everything.