HI!!!
Please tell me how can I fix this error when I am going to boot linux on my blueangle?
"Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)"
Ramtin Madani said:
"Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)"
Click to expand...
Click to collapse
Are you using the files from
http://gnulinux.biz ?
Yes; all of my files are from handhelds....
Related
This is my first attempt, which ended with:
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (junk in compressed archive); looks like an initrd
....
RAMDISK: Couldn't find valid RAM disk image starting at 0.
VFS: Cannot open root device "<NULL>" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Hello. At first I want to ask if any of you working on Gingerbread experienced "Force Close" loop on restart for many applications (for repair required format /data backup or restore via CWM)?
I spent a lot of time to get to the source of the problem, because even though the system version of JB's okay, it's GB is more stable and does not eat much RAM, moreover is much better for multitasking in the current situation.
Get to the point. The problem appears to be that from time to time, as in any filesystem, in the user partition (/ data) errors may occur that normally are repaired at boot time by e2fsck program. Moreover, in the case of my own and yet another piece of Samsung I8160 e2fsck is unable to complete repairs due to an error related to the library supports file systems.
When I connect ADB in recovery mode, umount /data and issue the command "e2fsck -y -f /dev/block/mmcblk0p5" the mass of errors are discovered, and repairing starts, but of course does not end well:
Code:
"FILESYSTEM WAS MODIFIED,
invalid argument passed to ext2 library while rewriting block and inode bitmaps "
...which tells that filesystem was modified, but the wrong argument was passed to the filesystem library and the correct structure not been written completely, resulting in an even greater massacre on the partition. It is not difficult to guess that the system will not boot normally (/data mounted in read only mode), and applications will start the "Force close" loop .
The story is not only on my phone, but also in other arts. After formatting it for a few weeks until you see the error and restart. After restoring a backup via CWM has usually only until the next reboot.
Has anyone experienced this? Is anyone able to solve this problem?
I tried stock ROM and kernel, reflashing, substitution of e2fsck binaries and libext2fs libraries. Chip does not have bad blocks, checked by dd command and calculated CRCs.
Please don't reply "do full wipe," not considering myself an Android noob, I want to solve the problem.
Have you ever tried to do filesystem check on Gingerbread and did it work for you? "e2fsck -y -f /dev/block/mmcblk0p5" ?
Can you restart the phone without problem?
Can you try if it works now?
Part of the log with dmesg at boot:
Code:
<4> [10.306152] EXT4-fs warning (device mmcblk0p5): ext4_clear_journal_err: Filesystem error recorded from previous mount: IO failure
<4> [10.306213] EXT4-fs warning (device mmcblk0p5): ext4_clear_journal_err: Marking fs in need of filesystem check.
<4> [10.331756] EXT4-fs (mmcblk0p5): warning: mounting fs with errors, running e2fsck is recommended
You can try
1.Boot in recovery mode(NEED CWM-Based Recovery).
2.Select "mounts and storage".
3.Select"mount /data".
4.Reboot.
But It's not really solve the problem because you need do these step when you boot your phone everytime, but this is the only solution(as I know) until who have better solution......
Sorry for my poor English......OTL
This is not possible...
Sent from my GT-I8160 using xda app-developers app
Maybe reflash your fw with odin you can download your fw at sammobile
I tried this, flashing JB and GB back. It seems that CWM 5 formatting procedure is buggy. When I format thru my own binary mke2fs this error is gone. So...
Sent from my GT-I8160 using xda app-developers app
First, sorry for my first thread.
I'm making custom kernel with f2fs support.
All things fine except first booting.
When booting with my f2fs kernel that has mount option in fstab, the booting time is so long.
And when I checked kernel log by dmesg command. The log says.
f2fs.fsck: Assertion error!
I have two f2fs partiion /cache and /userdata.
There are no error log with /cache partition. Only occured in /userdata partition.
Is it problem with my kernel source or data corruption..?
Hello everybody,
I think only an expert can help me !
LG G3 is ater few minute to fastboot mode.
1- no download mode, only fastboot.
2- the system, data, cache is in read only, cannot remount with rw permission, get error messege:
Invalid argument and E: Unable to mount '/system , '/cache , '/data and storage.
cannot flash via fastboot or adb.
when I run:
1- dmesg | grep mmc0 i get i/o error about logical block 0,1,2 and 3, buffer i/o error.
2- fsck_msdos dmesg I get i/o error.
some how it can install via srk tool 2.1 twrp recovery and I try to repair the system or format or change partitin type with twrp.
HI
I have a HTC one M9 hima. Lastly, it has suddenly rebooted. I have not use it.
But it have not stuck in boot. It has boot to the withe Logo screen then go off and boot again, again and again.
If i push power + vol down, the Black screen with e HTC logo comes and the loop go faster.
The only way to come to the bootloader ist to push power + vol down + vol up.
From there i come to the recovery or download Mode. I have twrp installed.
In twrp i discovered that some Partitions can not mount:
mount: mounting /dev/block/mmcblk0p65 on /cache failed: Invalid argument
mount: mounting /dev/block/mmcblk0p67 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p36 on /devlog failed: Invalid argument
mount: mounting /dev/block/mmcblk0p50 on /carrier failed: Invalid argument
mount: mounting /dev/block/mmcblk0p69 on /cota failed: Invalid argument
mount: mounting /dev/block/mmcblk0p68 on /preload failed: Invalid argument
mount: mounting /usb_otg on vfat failed: No such file or directory
mount: mounting /sd-ext on ext4 failed: No such file or directory
I tried:
- wipe Data --> mount error
- formate Data --> mount error
- flash new rom --> mount error
- install new Firmware --> requiret new start then loop
- mount manuel over adb --> invalied argument
- e2fsck /dev/block/mmcblk0p* --> bad magic number in super-block
- flash rom with fastboot --> invalid zip file
- new recovery --> after flash and boot to recover: exist old recovery <-- with dd, twrp and with fastboot
- twrp repair or change File System --> mount error
- twrp resize File System --> end with ERROR: 8
- twrp Change File System --> ERROR: 8
pls help me!!
sorry for my bad English
anyone here who knows the solution for above errors please? coz it did happen to me also. Thanks XDA for your help.
my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".
Radianer said:
my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".
Click to expand...
Click to collapse
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"
kmx0101 said:
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"
Click to expand...
Click to collapse
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.
shivasrage said:
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.
Click to expand...
Click to collapse
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?
kmx0101 said:
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?
Click to expand...
Click to collapse
https://forum.xda-developers.com/one-m9/help/download-modepossible-fix-t3555678