How many mmcblk devices is normal?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
1
down vote
favorite
Why so many mmcblk devices?
/dev/block/mmcblk0
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk0p1
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p16
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p2
/dev/block/mmcblk0p20
/dev/block/mmcblk0p21
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
/dev/block/mmcblk0p5
/dev/block/mmcblk0p6
/dev/block/mmcblk0p7
/dev/block/mmcblk0p8
/dev/block/mmcblk0p9
/dev/block/mmcblk0rpmb
What is the normal amount of mmcblk
devices? I'm having problems booting and I'm wondering if this kind of formatting is normal or not?
When I boot up under TWRP, and adb in. After I run mount -a
, I get
/dev/block/mmcblk0p19 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p21 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p20 on /system type ext4 (rw,seclabel,relatime)
/dev/block/mmcblk0p16 on /preload type ext4 (rw,seclabel,relatime,data=ordered)
That only explains four of them though.
samsung partitions
add a comment |
up vote
1
down vote
favorite
Why so many mmcblk devices?
/dev/block/mmcblk0
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk0p1
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p16
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p2
/dev/block/mmcblk0p20
/dev/block/mmcblk0p21
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
/dev/block/mmcblk0p5
/dev/block/mmcblk0p6
/dev/block/mmcblk0p7
/dev/block/mmcblk0p8
/dev/block/mmcblk0p9
/dev/block/mmcblk0rpmb
What is the normal amount of mmcblk
devices? I'm having problems booting and I'm wondering if this kind of formatting is normal or not?
When I boot up under TWRP, and adb in. After I run mount -a
, I get
/dev/block/mmcblk0p19 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p21 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p20 on /system type ext4 (rw,seclabel,relatime)
/dev/block/mmcblk0p16 on /preload type ext4 (rw,seclabel,relatime,data=ordered)
That only explains four of them though.
samsung partitions
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Why so many mmcblk devices?
/dev/block/mmcblk0
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk0p1
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p16
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p2
/dev/block/mmcblk0p20
/dev/block/mmcblk0p21
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
/dev/block/mmcblk0p5
/dev/block/mmcblk0p6
/dev/block/mmcblk0p7
/dev/block/mmcblk0p8
/dev/block/mmcblk0p9
/dev/block/mmcblk0rpmb
What is the normal amount of mmcblk
devices? I'm having problems booting and I'm wondering if this kind of formatting is normal or not?
When I boot up under TWRP, and adb in. After I run mount -a
, I get
/dev/block/mmcblk0p19 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p21 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p20 on /system type ext4 (rw,seclabel,relatime)
/dev/block/mmcblk0p16 on /preload type ext4 (rw,seclabel,relatime,data=ordered)
That only explains four of them though.
samsung partitions
Why so many mmcblk devices?
/dev/block/mmcblk0
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk0p1
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p16
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p2
/dev/block/mmcblk0p20
/dev/block/mmcblk0p21
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
/dev/block/mmcblk0p5
/dev/block/mmcblk0p6
/dev/block/mmcblk0p7
/dev/block/mmcblk0p8
/dev/block/mmcblk0p9
/dev/block/mmcblk0rpmb
What is the normal amount of mmcblk
devices? I'm having problems booting and I'm wondering if this kind of formatting is normal or not?
When I boot up under TWRP, and adb in. After I run mount -a
, I get
/dev/block/mmcblk0p19 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p21 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p20 on /system type ext4 (rw,seclabel,relatime)
/dev/block/mmcblk0p16 on /preload type ext4 (rw,seclabel,relatime,data=ordered)
That only explains four of them though.
samsung partitions
samsung partitions
edited 51 mins ago
asked 56 mins ago
Evan Carroll
1,816112857
1,816112857
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
There is nothing abnormal in this case. They is only one device in the first preformatted text, which is /dev/block/mmcblk0 (just like /dev/sda in Linux distros). The rest are the partitions within that device (akin to /dev/sda1, /dev/sda2 and so on).
There is no normal limit, not that I came across, for how many partitions a device can have. It depends upon how developers want to design and provide a functionality. E.g. earlier, there used to be one system and boot partition. But recent Android versions started a new normal of setting up additional boot and system partitions for fail-safe measures.
Also, mount command only shows the partition which are mounted under /. Some partitions are never needed to be mounted, such as ones concerning bootloader, so you won't see them in mount's output.
Great answer, I'll keep digging.
– Evan Carroll
34 mins ago
@EvanCarroll thanks! I think you would find this Q&A helpful. See android.stackexchange.com/q/92565/96277
– Firelord♦
31 mins ago
2
+1. My device mia1 reports 64!
– beeshyams♦
28 mins ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
There is nothing abnormal in this case. They is only one device in the first preformatted text, which is /dev/block/mmcblk0 (just like /dev/sda in Linux distros). The rest are the partitions within that device (akin to /dev/sda1, /dev/sda2 and so on).
There is no normal limit, not that I came across, for how many partitions a device can have. It depends upon how developers want to design and provide a functionality. E.g. earlier, there used to be one system and boot partition. But recent Android versions started a new normal of setting up additional boot and system partitions for fail-safe measures.
Also, mount command only shows the partition which are mounted under /. Some partitions are never needed to be mounted, such as ones concerning bootloader, so you won't see them in mount's output.
Great answer, I'll keep digging.
– Evan Carroll
34 mins ago
@EvanCarroll thanks! I think you would find this Q&A helpful. See android.stackexchange.com/q/92565/96277
– Firelord♦
31 mins ago
2
+1. My device mia1 reports 64!
– beeshyams♦
28 mins ago
add a comment |
up vote
2
down vote
accepted
There is nothing abnormal in this case. They is only one device in the first preformatted text, which is /dev/block/mmcblk0 (just like /dev/sda in Linux distros). The rest are the partitions within that device (akin to /dev/sda1, /dev/sda2 and so on).
There is no normal limit, not that I came across, for how many partitions a device can have. It depends upon how developers want to design and provide a functionality. E.g. earlier, there used to be one system and boot partition. But recent Android versions started a new normal of setting up additional boot and system partitions for fail-safe measures.
Also, mount command only shows the partition which are mounted under /. Some partitions are never needed to be mounted, such as ones concerning bootloader, so you won't see them in mount's output.
Great answer, I'll keep digging.
– Evan Carroll
34 mins ago
@EvanCarroll thanks! I think you would find this Q&A helpful. See android.stackexchange.com/q/92565/96277
– Firelord♦
31 mins ago
2
+1. My device mia1 reports 64!
– beeshyams♦
28 mins ago
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
There is nothing abnormal in this case. They is only one device in the first preformatted text, which is /dev/block/mmcblk0 (just like /dev/sda in Linux distros). The rest are the partitions within that device (akin to /dev/sda1, /dev/sda2 and so on).
There is no normal limit, not that I came across, for how many partitions a device can have. It depends upon how developers want to design and provide a functionality. E.g. earlier, there used to be one system and boot partition. But recent Android versions started a new normal of setting up additional boot and system partitions for fail-safe measures.
Also, mount command only shows the partition which are mounted under /. Some partitions are never needed to be mounted, such as ones concerning bootloader, so you won't see them in mount's output.
There is nothing abnormal in this case. They is only one device in the first preformatted text, which is /dev/block/mmcblk0 (just like /dev/sda in Linux distros). The rest are the partitions within that device (akin to /dev/sda1, /dev/sda2 and so on).
There is no normal limit, not that I came across, for how many partitions a device can have. It depends upon how developers want to design and provide a functionality. E.g. earlier, there used to be one system and boot partition. But recent Android versions started a new normal of setting up additional boot and system partitions for fail-safe measures.
Also, mount command only shows the partition which are mounted under /. Some partitions are never needed to be mounted, such as ones concerning bootloader, so you won't see them in mount's output.
answered 36 mins ago
Firelord♦
16.8k1169176
16.8k1169176
Great answer, I'll keep digging.
– Evan Carroll
34 mins ago
@EvanCarroll thanks! I think you would find this Q&A helpful. See android.stackexchange.com/q/92565/96277
– Firelord♦
31 mins ago
2
+1. My device mia1 reports 64!
– beeshyams♦
28 mins ago
add a comment |
Great answer, I'll keep digging.
– Evan Carroll
34 mins ago
@EvanCarroll thanks! I think you would find this Q&A helpful. See android.stackexchange.com/q/92565/96277
– Firelord♦
31 mins ago
2
+1. My device mia1 reports 64!
– beeshyams♦
28 mins ago
Great answer, I'll keep digging.
– Evan Carroll
34 mins ago
Great answer, I'll keep digging.
– Evan Carroll
34 mins ago
@EvanCarroll thanks! I think you would find this Q&A helpful. See android.stackexchange.com/q/92565/96277
– Firelord♦
31 mins ago
@EvanCarroll thanks! I think you would find this Q&A helpful. See android.stackexchange.com/q/92565/96277
– Firelord♦
31 mins ago
2
2
+1. My device mia1 reports 64!
– beeshyams♦
28 mins ago
+1. My device mia1 reports 64!
– beeshyams♦
28 mins ago
add a comment |
Thanks for contributing an answer to Android Enthusiasts Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fandroid.stackexchange.com%2fquestions%2f204698%2fhow-many-mmcblk-devices-is-normal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown