Error bad init encrypted filesystem - Исправление ошибок и поиск оптимальных решений проблем

Здравствуйте!
Столкнулся с проблемой, CM2MTK извлекает не все фото. Пришлось считать фулл в bin и открыть в R-Studio. В частности не были извлечены фото из viber и папки download. Какой алгоритм извлечения? Он ищет все файлы по расширениям или только в определённых папках?

JayDi

Только папку DCIM и ей подобные в старых версиях андройда.

Acer V360 попытка извлечения фото

Код:

Wait for phone...
Phone found! [ 15 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6575
BB_CPU_NME : [MediaTek] MT6575|MT6577_S00
BB_CPU_EXT : 0xCB00 , 0x8B00 , 0xE201
Processing BROM stage
i2c Init : 0300771F
SpeedSet : 0000
VChrgSet : 0x28 , BatStat : 0x02
WD Disable stat : 0x0000
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer   : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.3.2 on BBID : 0x84
Initialize Memory ... 
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x90 , OEM : 014A
[eMMC] : FLASH_INF : [HYNIX] , HYNIX
[eMMC] : FLASH_CID : 90014A2058494E594816A147CFC8109B
[eMMC] : FLASH_BRT : 0x00200000 , 0x00200000 , 0x00200000
[eMMC] : FLASH_LEN : 0x00000000E7000000
[eMMC] : FLASH_UCP : 3696 MiB [eMMC 4 GiB]
DEV RID    : 0x793A6513327AF89F11C776F716D1FFA9
INT RAM    : 0x00020000
EXT RAM    : 0x40000000 [1 GiB]
BOOT TYPE  : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!



Processiung : User Photo/Video/Records extraction

Trying switch source
FileSystem seems as DAMAGED or ERASED! Nothing to do :(

Read failed, error code : 0x01

Operation Failed
Elapsed: 00:00:11
Reconnect Power/Cable!

Через фулл и R-studio 613 фото и 25 видео. Часть конечно битые, но всё таки.
Лежат в папке DCIM/Camera.

Ro0f

Здравствуйте!
Столкнулся с проблемой, CM2MTK извлекает не все фото. Пришлось считать фулл в bin и открыть в R-Studio. В частности не были извлечены фото из viber и папки download. Какой алгоритм извлечения? Он ищет все файлы по расширениям или только в определённых папках?

присоединяюсь !
хотелось бы чтоб извлекал все фото.

FileSystem seems as DAMAGED or ERASED это говорит о том, что файловая система повреждена (частично/полностью) не важно.
Прога повидимому с побитой ФС не работает, о чём Вам и было сообщено в логе работы ПО.
Поэтому если Вы уверены что не стирали/перепрошивали телефон, смело читаем дамп и вытаскивает важные и не сильно фото/документы, опять же через любой доступный софт.

JayDi

6575 древний просто.
Добавлю и их.

Только что купил и активировал на бокс Infinity СМ2

Первым подопытным стал телефон сына Doogee X5 на процессоре MediaTek MT6580. Умышленно поставил графический ключ на него и решил считать, в итоге получил, что ключа нет ))) Это как так? Данный телефон не поддерживается или…?

Код:

Reading data ... 

[Error] : Bad Magic! Encrypted FS!
[Info] : DP Lock not set!

Далее решил считать телефонную книгу….Получил…

Код:

Processiung : PhoneBook extraction

Step #1
Error while reading PhoneBook! Code : 0x01 :(

Operation Failed
Elapsed: 00:00:11
Reconnect Power/Cable!

Можете проконсультировать в чем может быть проблема? Если я что-то сам делаю не так — не подсказывайте, хочу сам дойти до решения, если же это издержки самого программного продукта, тогда сообщите.

Благодарю заранее.

BQ BQS-5020 Android 6.0

Нормально считалась тел. книга….

Код:

Operation : Read UserData [ v1.58 ]

PhoneBook : Enabled

1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey

Wait for phone...
Phone found! [ 9 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6580
BB_CPU_NME : [MediaTek] MT6580_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer   : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x94
NAND Flash : NOT INSTALLED
eMMC Flash : 90014A4838473165050751C5E23863D5
Initialize Memory ... 
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x90 , OEM : 014A
[eMMC] : FLASH_INF : [HYNIX] , e1G8
[eMMC] : FLASH_CID : 90014A4838473165050751C5E23863D5
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000001D2000000
[eMMC] : FLASH_UCP : 7456 MiB [eMMC 8 GiB]
DEV RID    : 0x38380C89DE2A78D729FD1D00F89310B8
INT RAM    : 0x00020000
EXT RAM    : 0x40000000 [1 GiB]
BOOT TYPE  : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!


Processiung : PhoneBook extraction

Step #1
Step #2


Read Ok, PhoneBook records extracted : 51
TXT Saved to : C:InfinityBoxCM2MTKPhDataMT6580_PhoneBook.txt
Write : 51
CSV Saved to : C:InfinityBoxCM2MTKPhDataMT6580_PhoneBook.csv
VCF Saved to : C:InfinityBoxCM2MTKPhDataMT6580_PhoneBook.vcf

Done!
Elapsed: 00:00:30
Reconnect Power/Cable!

Finish at : [19.08.2017 / 22:08:45]

Может шифрование включено в смартфоне?

xtramen

Умышленно поставил графический ключ на него и решил считать, в итоге получил, что ключа нет )))

если андроид 6, то ключ оно и не считает

если андроид 6, то ключ оно и не считает

Да, ключ не считал…

Код:

Reading data ... 

[Info] : PatternLock Not Set!
[Info] : DP Lock not set!

JayDi

Зато сбросит без проблем без потери данных. Даже на седьмом и превьюхе восьмого. Если файловая не шифрована.

если андроид 6, то ключ оно и не считает

Зато сбросит без проблем без потери данных. Даже на седьмом и превьюхе восьмого. Если файловая не шифрована.

Сделал ResetUser Locks — получил….

Код:

Brand     : DOOGEE
ProdName  : DOOGEE
ProdModel : X5
Device    : DOOGEE
AndroidVer: 5.1
MTKxCPU   : MT6580
MTKxPRJ   : DOOGEE-X5-Android5.1-V15-2015.11.02


.......

Error : Bad init! Encrypted FileSystem!

Done!
Elapsed: 00:00:23

Считает, что ФС зашифрована, хотя в настройках даже такого пункта нет…Т.е. ребенок не мог её включить… Тогда остаётся только 1 вариант — система шифрована по умолчанию, с завода…Прошивка оригинальная стоит.

Последнее редактирование: 20/8/17

JayDi

Да, это зависит от производителя. Можно отключить это нафиг. Добавим такую опцию.

не извлекает записную

CM2MTK_v1.58
аппарат Lenovo A7000-a включается

Код:

Wait for phone...
Phone found! [ 9 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6752
BB_CPU_NME : [MediaTek] MT6732|MT6752_S00
BB_CPU_EXT : 0xCA01 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer   : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x8F
NAND Flash : NOT INSTALLED
eMMC Flash : 150100523758314D42092BC7DE60B2A7
Initialize Memory ... 
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM1X7
[eMMC] : FLASH_CID : 150100523758314D42092BC7DE60B2A7
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00080000
[eMMC] : FLASH_LEN : 0x00000001D2000000
[eMMC] : FLASH_UCP : 7456 MiB [eMMC 8 GiB]
DEV RID    : 0xBB5DAF7F707D20D46EA4F14014F0B667
INT RAM    : 0x00020000
EXT RAM    : 0x80000000 [2 GiB]
BOOT TYPE  : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!

[AP] : Initial info read Ok!

Brand     : Lenovo
ProdName  : aio_row
ProdModel : Lenovo A7000-a
Device    : A7000-a
AndroidVer: 6.0
MTKxCPU   : MT6752
MTKxPRJ   : A7000-a_USR_S228_1606211600_mp1V2.39_ROW

SECURITY : 
IMEI_SW [1] : 869045025982039
IMEI_SW [2] : 869045025982047
BTMAC Addr  : A03299FC93FF
WiFi MAC    : 5427580E93FF

MODEM : 
BaseBand  : MT6752_S00_AIO_ROW_LWG_M_V12_1_lwg_n

EXTRA : 
LCD : Not info available :(
LCD Res : 1280x720
TOUCH [0] : GT9XX_hotknot
CAM [0] : imx219ofilm_mipi_raw
CAM [1] : hi551qtech_mipi_raw
CAM [2] : hi551qtechv2_mipi_raw
MODEM : aio_row_lwg_dsds
LOCALE : en_US zh_CN zh_TW es_ES pt_BR ru_RU fr_FR de_DE tr_TR vi_VN ms_MY in_ID th_TH it_IT ar_EG hi_IN bn_BD ur_PK fa_IR pt_PT nl_NL el_GR hu_HU tl_PH ro_RO cs_CZ ko_KR km_KH iw_IL my_MM pl_PL es_US bg_BG hr_HR lv_LV lt_LT sk_SK uk_UA de_AT da_DK fi_FI nb_NO sv_SE en_GB hy_AM zh_HK et_EE ja_JP kk_KZ sr_RS sl_SI ca_ES

Done!
Elapsed: 00:00:12
Reconnect Power/Cable!

телефон включается, пытаюсь сохранить номера

Код:

Wait for phone...
Phone found! [ 9 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6752
BB_CPU_NME : [MediaTek] MT6732|MT6752_S00
BB_CPU_EXT : 0xCA01 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer   : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x8F
NAND Flash : NOT INSTALLED
eMMC Flash : 150100523758314D42092BC7DE60B2A7
Initialize Memory ... 
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM1X7
[eMMC] : FLASH_CID : 150100523758314D42092BC7DE60B2A7
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00080000
[eMMC] : FLASH_LEN : 0x00000001D2000000
[eMMC] : FLASH_UCP : 7456 MiB [eMMC 8 GiB]
DEV RID    : 0xBB5DAF7F707D20D46EA4F14014F0B667
INT RAM    : 0x00020000
EXT RAM    : 0x80000000 [2 GiB]
BOOT TYPE  : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!


Processiung : PhoneBook extraction

Step #1
Step #2


PhoneBook seems as Empty! Nothing found :(

Done!
Elapsed: 00:00:16
Reconnect Power/Cable!

а по факту дофига номеров, почему не находит?

Источник

I am trying to make a linux os with encrypted filesystem for the whole OS (boot,kernel,root,…)

I modified EXT4 filesystem’s read and write functions. after running a lot of tests ~~everything~~ read and write work fine.

EDIT:

my change is a simple XOR to file contents.

my tests include reading/writing text files, tar archive
creation/deletion, sound and videofile creation/copying/deletion and
some stress tests.

this is dmesg says when trying to run a binary:

traps: a.out[2765] trap invalid opcode ip:400e73 sp:7ffc9f3d6f10 error:0 in a.out[400000+b4000]

next step was to boot a simple linux based OS on this encrypted filesystem, I modified GRUB 2 bootloader so it cat boot the kernel from encrypted disk.
then I faced this problem:

grub can load linux kernel and kernel boots, but when it tries to run the init proccess I get kernel panic with the message: «init Not tained».

I can see from previous messages that filesystem is loaded by kernel and it is actually reading init file but refuses to run init.

my question is: is kernel reading init file in any other way than using standard read system call? is there something I am doing wrong here?

Any help would be greatly appreciated

EDIT:

now the question is:

how can I decrypt the data that kernel uses by mapping memory?

Источник

Lava Iris 870 is it Possible to remove pattern without data loss???

Lava Iris 870 is it Possible to remove pattern without data loss???

Use professional Tool Like. Cm2 Dongle , Miracle Box To Read Pattern Lock . Cm2 Dongle to Read Pattern Lock Possible

I was used cm2 see the pic

screenshot-2.png

29.2 KB

· Views: 76

Your Divice Encrypted Fs . Not Possible To Save data you are many time try Wrong Pattren So Device Encrypted

Lava Iris 870 Possible to remove pattern without data loss Not work

1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey

Wait for phone…
Phone found! [ 127 ]
Sync…
Inital Boot Ok!
BB_CPU_PID : 6737
BB_CPU_NME : [MediaTek] MT6737M|MT6737_S00
BB_CPU_EXT : 0xCB00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x0005
BLVersion : 0x00FE
PreLoader : NOT Active [ Erased ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v3.3001.00.00
Sending and initialize DA …
Running DA ver.4.2 on BBID : 0x9B
NAND Flash : NOT INSTALLED
eMMC Flash : 510001154D33323850C300421F2186C8
Initialize Memory …
DRAM configured from ScatFW!
DRAM initialize passed!
DRAM size : 0x80000000
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM328
[eMMC] : FLASH_CID : 150100513832334D4200C350C886331F
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0x4571F283F887B411798DB837BC614646
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!

USBDL : Init HSUSB Ok
Error : Bad init! Encrypted FileSystem!

Done!
Elapsed: 00:00:13
Reconnect Power/Cable!

Last edited: Mar 4, 2020

Источник

Я установил 10.10 несколько дней назад. Единственные изменения в установке по умолчанию являются добавлением Chrome и Пинты.

Это было прекрасно в течение нескольких дней, затем сегодня войдите в систему, и т.д. казался медленным. Аналогично это не могло даже представить меню перезапуска/завершения работы.

Надежда его была некоторым испорченным обновлением, я выполнил менеджера по обновлению; это пыталось установить, но отказавший (UI не сделал это очевидным, что перестало работать).

Прекрасный, хорошо. Завершите работу его (нажатие вводят в пустое диалоговое окно завершения работы).

Запустите его надежда… И… #fail.

Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.

Это — теперь кирпич?

Подробнее:

GRUB 1.98+20100804-5ubuntu3

Ubuntu, with Linux 2.6.35-22-generic

Причины

udevadm trigger is not permitted while udev is unxonfigured
Giving up waiting for root device.

Или

Ubuntu, with Linux 2.6.35-23-generic

Причины

mount: mounting /dev on /root/dev failed: No such file or directory

Затем то же для/sys и процесса /

задан
24 July 2014 в 16:42

Источник

#1 2006-09-23 14:29:25

rbl: Member; Registered: 2005-08-29; Posts: 64

[Solved] Cannot boot (mkinitcpio + encrypted root fs)

Hi guys,

after many months, I have once again a problem I cannot solve myself. Since mkinitcpio has replaced mkinitrd for the stock kernel, I cannot boot into my encrypted root anymore:

Attempting to create root device `/dev/hda3`
ERROR: Failed to parse block device name for `/dev/hda3`
   unknown
ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
:: Initramfs Completed - control passing to kinit
kinit: Cannot open root device dev(0,0)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!

Here’s my (currently bloated, tried nearly everything) mkinitcpio.conf:

MODULES="piix ide_disk reiserfs ext3 dm-crypt aes-i586"
BINARIES=""
FILES=""
HOOKS="base udev autodetect ide sata scsi usbinput lvm2 encrypt filesystems"

And my grub menu.lst:

# (0) Arch Linux
title  Arch Linux (mkinitcpio)
root   (hd0,0)
kernel /vmlinuz26 root=/dev/hda3 ro vga=792
initrd /kernel26.img

My encrypted filesystem was build according to the WIKI , is using ReiserFS, and has been / is working with earlier kernels (using old ArchCK right now..)

EDIT: solved

#2 2006-09-23 20:38:41

Lone_Wolf: Member; From: Netherlands, Europe; Registered: 2005-10-04; Posts: 10,652

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

From Configuring_mkinitcpio#Using_encrypted_root

Using loop-aes volumes

mkinitcpio does not support loop-aes yet.

I see a aes module listed, maybe that’s the problem cause ?

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B) && (time C > time B ) ≠ (A works at time C)

#3 2006-09-23 20:59:31

rbl: Member; Registered: 2005-08-29; Posts: 64

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

I don’t think I am using Loop-AES. I set up the partition with cryptsetup, not losetup as far as I remember. During bootup, the device-mapper seemed to handle the mounting. This is how I successfully boot into the fs with an old archck kernel:

# (1) Arch Linux (archck)
title  Arch Linux (archck)
root   (hd0,0)
kernel /vmlinuz26archck root=/dev/dm-0 ro
initrd /initramfs-2.6.15-archck.img

#4 2006-09-24 08:48:55

onearm: Member; From: Anywhere but here; Registered: 2006-07-06; Posts: 359; Website

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

Tried with the rootfstype= kernel parameter? (probably won’t help but trying isn’t a bad idea)

To get something done, a committee should consist of no more than three persons, two of them absent.
—
My Github

#5 2006-09-24 10:31:22

brain0: Developer; From: Aachen — Germany; Registered: 2005-01-03; Posts: 1,382

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

rbl wrote:

My encrypted filesystem was build according to the WIKI , is using ReiserFS, and has been / is working with earlier kernels (using old ArchCK right now..)

First, creating an encrypted filesystem according to this wiki page is not recommended for various reasons, mainly because it is not very secure. I’ll have to update that page soon.

Second, the mkinitcpio wiki page has a section about «legacy cryptsetup volumes», I think you should read that (and pay special attention to the crypto= option). But I am worried about something else:

Attempting to create root device `/dev/hda3`
ERROR: Failed to parse block device name for `/dev/hda3`

This look more like /dev/hda3 isn’t found in the first place, but I am not sure. Correct your crypto setup and see if this message still appears.

#6 2006-09-24 12:25:34

rbl: Member; Registered: 2005-08-29; Posts: 64

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

I tried both rootfstype=reiserfs and crypto=:::: which did not work.. if crypto= is the way to go and I need more than the default(::::) parameters, how do I get them?

#7 2006-09-24 16:35:13

brain0: Developer; From: Aachen — Germany; Registered: 2005-01-03; Posts: 1,382

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

You could perhaps tell me what the error messages are if you add the crypto=:::: parameter. Your previous output suggests that it can’t even find your hard disk controller, which is weird as you added the modules manually. Does it even ask for a passphrase?

#8 2006-09-24 20:21:53

rbl: Member; Registered: 2005-08-29; Posts: 64

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

Whether or not crypto=:::: is set, the Error messages are the same. If I add the rootfstype=reiserfs parameter, the 2 lines beginning with «ERROR» disappear, everything else remains the same. I am in no case being asked for the password.

#9 2006-09-24 22:51:32

brain0: Developer; From: Aachen — Germany; Registered: 2005-01-03; Posts: 1,382

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

Did you rebuild your mkinitcpio image after adding the encrypt hook? Can you provide a screenshot (digital camera ….) or a complete and precise copy of the messages on the screen?

#10 2006-09-25 10:35:37

rbl: Member; Registered: 2005-08-29; Posts: 64

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

yes, I did rebuild the mkinitcpio image:

root@aspirin[rebel]# mkinitcpio -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [ide]
:: Parsing hook [sata]
:: Parsing hook [scsi]
:: Parsing hook [usbinput]
:: Parsing hook [raid]
:: Parsing hook [lvm2]
:: Parsing hook [encrypt]
:: Parsing hook [filesystems]
:: Generating module dependancies
:: Generating image '/boot/kernel26.img'...SUCCESS

Unfortunately, I have no digital camera at the moment. I am willing to go through the hassle of writing the whole screen down, though.. Should I enable or disable the crypto=:::: and/or rootfstype=reiserfs parameters for this?

#11 2006-09-25 16:16:09

brain0: Developer; From: Aachen — Germany; Registered: 2005-01-03; Posts: 1,382

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

Enable crypto=::::, it doesn’t matter if you have the rootfstype option, the output shouldn’t be too different (I should be able to read both). Everything that happens after «Loading [udev]» is important.

Most important: if you rebuild the image and run a different kernel than the image is for, then your have to specify the «-k 2.6.18-ARCH» option to mkinitcpio (or -k 2.6.17-ARCH if that is the kernel version). Otherwise it is cannot boot.

#12 2006-09-25 17:12:13

rbl: Member; Registered: 2005-08-29; Posts: 64

Re: [Solved] Cannot boot (mkinitcpio + encrypted root fs)

brain0 wrote:

Most important: if you rebuild the image and run a different kernel than the image is for, then your have to specify the «-k 2.6.18-ARCH» option to mkinitcpio (or -k 2.6.17-ARCH if that is the kernel version). Otherwise it is cannot boot.

Oh well, that did it.. thanks brain0!

I kept building the images while running the old archck-kernel and did not set the -k parameter.

Источник