All the kernels support this, can we format /system, /data and everything else to ext4 and get more speed out of the file system on this phone and if so, how?
The official ROM with 2.6.35 kernel, is already using ext4 for /system /data and /cache partitions.
Code:
$ busybox mount|grep ext4
/dev/block/mmcblk0p12 on /system type ext4 (ro,relatime,barrier=1,nodelalloc,data=ordered)
/dev/block/mmcblk0p13 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p6 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered)
Maybe it is time to get over my fear of the 2.6.35 kernel with its atmel problems and its wifi reboots and update.
Related
Hi,
There are a couple of threads asking this, but as far as I can see the problems are different on the DHD.
I use Linux pretty-much everywhere so have no need to read fat filesystems.
From what I can see by doing a mount, ext3 support is builtin
Code:
$mount | grep ext
/dev/block/mmcblk0p25 /system ext3 ro,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p27 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p28 /devlog ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0
So no custom kernel should be needed.
I tried re-creating the filesystem as ext3, but the phone wouldn't mount the partition. As there's no /etc/fstab in Android, I'm guessing the filesystems are listed somewhere else. Can anyone say where?
Second question: Journalling will write to the card more than I'd like, but I'm guessing ext3 or 4 with the journalling moved to the internal memory would be faster than ext2??
Anyone know of any drawbacks? What about ext4 support on the DHD, anyone know if it's there?
Hoping someone from the dev thread
reads this. Only reason I can't post there is I am "new".
I'm running into an issue booting using the alternate boot option.
My primary boot is Stock rooted 6.3
My alternate is Pure AOKP ICS with Hashcode 3.0 Kerne
This is my partition table.
Code:
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB splash
9 312MB 849MB 537MB ext4 system
10 849MB 2241MB 1392MB ext4 userdata
11 2241MB 2369MB 128MB ext4 cache
12 2369MB 5750MB 3381MB fat32 media msftres
13 5750MB 5761MB 11.0MB boot2
14 5761MB 6298MB 537MB ext4 system2
15 6298MB 7690MB 1392MB ext4 userdata2
16 7690MB 7818MB 128MB ext4 cache2
This is from my init.omap4430.rc file
Code:
on fs
log "== init.omap4430.rc: on fs ------------------------"
mount ext4 /dev/block/mmcblk0p14 /system wait ro
mount ext4 /dev/block/mmcblk0p15 /data wait noatime nosuid nodev errors=continue
mount ext4 /dev/block/mmcblk0p16 /cache wait noatime nosuid nodev errors=continue
mount ext4 /dev/block/mmcblk0p8 /dropbox wait noatime nosuid nodev errors=continue
And this is my update-script
Code:
format("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/system2", "0");
mount("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/system2", "/system");
......
package_extract_file("boot.img", "/dev/block/platform/mmci-omap-hs.1/by-name/boot2");
The install works fine, and everything seems to go to its correct place. But when I select the alternate boot option it sits indefinitely on the selection screen.
What recovery are you using? Many people are reporting that ClockworkMod seems to have trouble with ROMs using the 3.0 kernel, making them unbootable even on a stock boot layout. TWRP doesn't have issues with it, so I would try that if you're currently using CWM.
If that's not the issue, then try using the "/dev/block/mmcblk0p#" style to specify the partitions in the updater-script. I had some difficulty getting it to play nicely with the "by-name" style for whatever reason, especially with the boot images (I'm not really sure why, though).
eldarerathis said:
What recovery are you using? Many people are reporting that ClockworkMod seems to have trouble with ROMs using the 3.0 kernel, making them unbootable even on a stock boot layout. TWRP doesn't have issues with it, so I would try that if you're currently using CWM.
If that's not the issue, then try using the "/dev/block/mmcblk0p#" style to specify the partitions in the updater-script. I had some difficulty getting it to play nicely with the "by-name" style for whatever reason, especially with the boot images (I'm not really sure why, though).
Click to expand...
Click to collapse
I'm used TWRP 2.0 and 2.1, neither "worked".
The rom installed, that doesn't seem to be the issue, unless I am completely off base.
I was unable to install gapps because moding its install script to goto the mmcblk0p14 caused it to fail, I think it was because it was signed, and I modded it making the md5 invalid. I need to work on that, but that shouldn't cause an issue with booting.
The only thing I can think of is that your boot2 is on p16 while mine is on p13?? would that be the issue?
Changed to
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p14");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
.......
package_extract_file("boot.img", "/dev/block/mmcblk0p13");
and
Code:
on fs
mount ext4 /dev/block/mmcblk0p14 /system wait ro
mount ext4 /dev/block/mmcblk0p15 /data wait noatime nosuid nodev errors=continue
# mount ext4 /dev/block/platform/mmci-omap-hs.1/by-name/cache /cache wait noatime nosuid nodev errors=contin$
mount ext4 /dev/block/mmcblk0p8 /dropbox wait noatime nosuid nodev errors=continue
This time I am trying to put the 6.3 rooted version on the alternate.
The install occurs with no issue. It just gets stuck at the Alternate Boot menu.
I'm using 0.1, not sure if there is another version of the loader.
Has anybody got a default, empty, Nook compatible .zip I can work with?
By this I mean an updater.script with all the mounting block commands etc that I can modify.
Im working on a few things at the mo and struggle with little things like mounting commands
Once /system, /data and /sdcard are mounted properly Im ok with the scripting.
Or, alternatively, once rooted with NookManager, is busybox installed? I can work with busybox
Bear with me Im a NookNoob and still reading, NookST arrived yesterday and dived right in
:edit:
Ok, so Ive found these so far:
0 /tmp ramdisk (null) (null)
1 /boot vfat /dev/block/mmcblk0p1 (null)
2 /system ext2 /dev/block/mmcblk0p5 (null)
3 /cache ext3 /dev/block/mmcblk0p7 (null)
4 /data ext3 /dev/block/mmcblk0p8 (null)
5 /emmc vfat /dev/block/mmcblk0p6 (null)
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
7 /sd-ext ext3 /dev/block/mmcblk1p2 (null)
Could someone confirm they are right?
after formatting with f2fs, need to change some sort files "fstab" to mount the partitions with this file system?
>adb shell
#umount /system
#umount /data
#mkfs.f2fs /dev/block/mmcblk0p16
#mkfs.f2fs /dev/block/mmcblk0p13
#mkfs.f2fs /dev/block/mmcblk0p12
#mount /system
#mount /data
My kernel is AGNi with f2fs support ..
Tks
nothing ?
mpsnet said:
nothing ?
Click to expand...
Click to collapse
if the rom doesnt handle the changes for u then u will need to change it yourself
Hi guys, I'm a new poster but long time reader of these boards, which helped me a lot since I got my A500 and an Android phone years ago. So far I've always found a ready solution for my 'droid needs and wants here but this time I think I've hit a bricked (tablet) wall! :laugh::crying:
My A500 has Skrilax_CZ's bootloader v9 with CWM v6.0.4.5 on the secondary partition and for more than a year has been running HenrikE's Android 4.4.4 (OmniROM unofficial) from this thread: http://forum.xda-developers.com/showthread.php?t=2705989 The ROM has been going fine apart from a few random freezes but overall I like it.
Yesterday I was using the tablet to read a book and it started running Play store auto updates, I went to look at the store app to check which apps etc, then switched back to my book and the tablet froze. Normally I'd just long press the power button and then press it again to turn it on, so I did, only this time the ROM would not boot anymore and the tablet got stuck at the bootloader screen. I went into recovery and wiped cache and dalvik, no change. I went back to recovery and then I realized the partitions aren't mounting nor can be formatted! /system, /data, /cache, nothing:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
Without much hope I reinstalled the ROM with a data/factory reset and that of course didn't fix it. Tried to erase userdata and cache with fastboot, no change. It looks like either my internal SD card is broken/not found or my partitions are horribly corrupted? mmcblk0 isn't showing on /dev, see below from adb shell:
/dev/block # ls
loop0 loop2 loop4 loop6 mmcblk0p5 zram0
loop1 loop3 loop5 loop7 vold
/dev/block # fdisk /dev/block/mmcblk0
fdisk: can't open '/dev/block/mmcblk0'
/dev/block # parted
Error: No device found
Retry/Cancel? c
c
/dev/block #
/etc # cat fstab
/dev/block/mmcblk0p4 /cache ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p3 /system ext4 rw
/etc # mount -t ext4 /dev/block/mmcblk0p8 /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: No such file or directory
/etc #
Looking at other threads I guess the next step would be to try an APX reinstall however I use Linux and don't have a Windows machine around. While I can certainly spend my Easter break setting up a Windows Virtualbox :crying: do you guys think this is a hardware fault or something that can be fixed? Many thanks for any input. Oh and yeah I do have the tablet's SBK number.
Edit:
I forgot to paste this:
/etc # cat recovery.fstab
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p3 /system ext4 ro,noatime wait
/dev/block/mmcblk0p4 /cache ext4 noatime,nosuid,nodev,errors=panic wait,check
/dev/block/mmcblk0p8 /data ext4 noatime,nosuid,nodev,errors=panic,discard,noauto_da_alloc wait,check
/dev/block/mmcblk0p2 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p1 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p5 /misc emmc defaults recoveryonly
/dev/block/mmcblk0p3 /system ext4 defaults recoveryonly
/dev/block/mmcblk0p4 /cache ext4 defaults recoveryonly
/dev/block/mmcblk0p6 /flexrom ext4 defaults recoveryonly
/dev/block/mmcblk0p8 /data auto defaults recoveryonly
/dev/block/mmcblk1p1 /mnt/sdcard vfat defaults recoveryonly
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 auto defaults voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.2 /storage/usbdisk0 auto defaults voldmanaged=sda:auto
/etc #
Hi all, I've narrowed it down to a bad sector on the tablet's internal storage and posted on this older thread about the same problem http://forum.xda-developers.com/showthread.php?t=1691729&page=5