From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
Date: Tue, 24 May 2016 13:07:59 +0000 [thread overview]
Message-ID: <bug-118401-13602-xe3X6XPlS9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-118401-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=118401
Navin <navinp1912@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |navinp1912@gmail.com
--- Comment #6 from Navin <navinp1912@gmail.com> ---
https://ext4.wiki.kernel.org/index.php/UpgradeToExt4
says in section
"Converting an ext3 filesystem to ext4"
Note: The ext3 driver will be removed from the kernel in 4.3.
Your root filesystem is ext3 .
Maybe your second image drop is says root image is not found due to the above.
Your options are like
1) Convert your data to ext4
2) Enable the ext3 filesystem driver explicitly in your menuconfig /xconfig
After saving your .config diff with the older non-working configuration should
look like ie added EXT3_FS and build a kernel
-# CONFIG_EXT3_FS is not set
+CONFIG_EXT3_FS=y
+CONFIG_EXT3_FS_POSIX_ACL=y
+CONFIG_EXT3_FS_SECURITY=y
3) Convert your data to ext2 and then try with the current non-working kernels.
The first file in diff is working (4.2) and the second file is non working .
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
-CONFIG_EXT4_USE_FOR_EXT23=y
+CONFIG_EXT4_USE_FOR_EXT2=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
CONFIG_EXT4_ENCRYPTION=m
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
Looks like you have removed in EXT23 in your config and used it as EXT2 .
This is for first file as (4.2.) and 4.6 as the second file (.config).
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
-CONFIG_EXT4_USE_FOR_EXT23=y
+CONFIG_EXT4_USE_FOR_EXT2=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
CONFIG_EXT4_ENCRYPTION=m
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-05-24 13:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 11:41 [Bug 118401] New: Lenovo A740 gave up waiting for root device with kernels >= 4.3 bugzilla-daemon
2016-05-18 16:02 ` [Bug 118401] " bugzilla-daemon
2016-05-19 8:40 ` bugzilla-daemon
2016-05-19 8:42 ` bugzilla-daemon
2016-05-19 8:43 ` bugzilla-daemon
2016-05-19 8:56 ` bugzilla-daemon
2016-05-24 13:07 ` bugzilla-daemon [this message]
2016-05-24 14:37 ` bugzilla-daemon
2016-05-24 17:46 ` bugzilla-daemon
2016-05-31 5:51 ` bugzilla-daemon
2016-06-01 15:26 ` bugzilla-daemon
2016-06-01 16:02 ` bugzilla-daemon
2016-06-01 18:53 ` bugzilla-daemon
2016-06-01 21:50 ` bugzilla-daemon
2016-06-02 10:28 ` bugzilla-daemon
2016-06-02 12:52 ` bugzilla-daemon
2016-06-02 18:19 ` bugzilla-daemon
2016-06-03 19:03 ` bugzilla-daemon
2016-06-03 19:04 ` bugzilla-daemon
2016-06-03 19:07 ` bugzilla-daemon
2016-06-03 19:08 ` bugzilla-daemon
2016-06-04 6:28 ` bugzilla-daemon
2016-06-04 9:36 ` bugzilla-daemon
2016-06-04 13:45 ` bugzilla-daemon
2016-06-04 22:05 ` bugzilla-daemon
2016-06-05 1:46 ` bugzilla-daemon
2016-06-05 11:12 ` bugzilla-daemon
2016-06-05 11:14 ` bugzilla-daemon
2016-06-05 12:21 ` bugzilla-daemon
2016-06-05 13:43 ` bugzilla-daemon
2016-06-06 7:27 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-118401-13602-xe3X6XPlS9@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox