Error 6 mounting ext3 - Исправление ошибок и поиск оптимальных решений проблем

Содержание

Arch Linux
#1 2014-12-04 09:55:15
kernel panic with clonned disk
#2 2014-12-04 10:45:14
Re: kernel panic with clonned disk
#3 2014-12-04 10:54:56
Re: kernel panic with clonned disk
#4 2014-12-04 11:29:54
Re: kernel panic with clonned disk
#5 2014-12-04 11:52:32
Re: kernel panic with clonned disk
#6 2014-12-04 12:10:40
Re: kernel panic with clonned disk
#7 2014-12-04 13:46:42
Re: kernel panic with clonned disk
#8 2014-12-04 23:02:45
Re: kernel panic with clonned disk
#9 2014-12-05 09:47:25
Re: kernel panic with clonned disk
#10 2014-12-05 12:39:09
Re: kernel panic with clonned disk
#11 2014-12-05 12:58:52
Re: kernel panic with clonned disk
#12 2014-12-05 13:38:36
Re: kernel panic with clonned disk
#13 2014-12-05 13:42:08
Re: kernel panic with clonned disk
#14 2014-12-05 14:09:15
Re: kernel panic with clonned disk
#15 2014-12-05 15:01:41
Re: kernel panic with clonned disk
#16 2014-12-05 15:28:58
Re: kernel panic with clonned disk
#17 2014-12-05 17:19:25
Re: kernel panic with clonned disk
#18 2014-12-05 18:00:27
Re: kernel panic with clonned disk
#19 2014-12-05 18:59:05
Re: kernel panic with clonned disk
#20 2014-12-05 19:33:59
Re: kernel panic with clonned disk
#21 2014-12-05 19:40:18
Re: kernel panic with clonned disk
#22 2014-12-06 10:26:52
Re: kernel panic with clonned disk
Mount error 6 mounting ext3
Перенос старого MСBC 3 на виртуальную машину.

Arch Linux

You are not logged in.

#1 2014-12-04 09:55:15

kernel panic with clonned disk

I have an old hard drive with pretty old software for server needs and I decided to change hard drive. I bought new one. Ran the following:

Rebooted to load from sdb, GRUB loads without troubles, but got the kernel panic:

What’s wrong with my dd?! What did I wrong?! What the different between these tow hard disks? Because my original hard drive loads well.

#2 2014-12-04 10:45:14

Re: kernel panic with clonned disk

I wouldn’t use dd myself. I recommend that you partition the new drive to your liking, then simply rsync over the old hdd to the new one. If you have multiple partitions to mirror, you can do them one at a time or if you have a more simplified setup in the new drive, simply mount them up and sync over as you see fit. Remember to update your bootloader if using a different layout or uuids as well as your fstab.

#3 2014-12-04 10:54:56

Re: kernel panic with clonned disk

I wouldn’t use dd myself.

Why? It’s recommended way according to the wiki.

Remember to update your bootloader if using a different layout or uuids as well as your fstab.

This will clone the entire drive, including MBR (and therefore bootloader), all partitions, UUIDs, and data.

Is it a mistake in the article?

Last edited by SkyTod (2014-12-04 10:55:26)

#4 2014-12-04 11:29:54

Re: kernel panic with clonned disk

The wiki recommends several things that I disagree with. My suggestion is just one way to do things. You have the freedom to select an alternative if you wish. As you have already done so, and ran into problems, I offered up an alternative. Do as you wish.

#5 2014-12-04 11:52:32

Re: kernel panic with clonned disk

Was the sda drive mounted writable and was this the os you used for dd? — Try a live usb system with unmounted sda.

For the uuids: compare blkid output and fstab.

#6 2014-12-04 12:10:40

Re: kernel panic with clonned disk

Thank you for that, can you share some step-by-step manual?

Was the sda drive mounted writable and was this the os you used for dd? — Try a live usb system with unmounted sda.

First time I tried my archlinux, then my LiveCD (some minor linux build) with unmounted both sd* — the same result.

For the uuids: compare blkid output and fstab.

Do you mean /etc/fstab? How can I compare blkid?

#7 2014-12-04 13:46:42

Re: kernel panic with clonned disk

Just checked. There are no /etc/blkid.tabs, no differences in fstabs.

#8 2014-12-04 23:02:45

Re: kernel panic with clonned disk

The command blkid will give you a list of blockdevices and their uuid. Compare those to the uuids you’ve got in your /etc/fstab file. If this is still unclear post the output/content of the command/file.

#9 2014-12-05 09:47:25

Re: kernel panic with clonned disk

The command blkid will give you a list of blockdevices and their uuid.

There is no blkid on my LiveCD, is there any other tools?

#10 2014-12-05 12:39:09

Re: kernel panic with clonned disk

blkid is provided by util-linux, you can install that on your livecd. Alternatively; simply execute ls /dev/disk/by-uuid/

#11 2014-12-05 12:58:52

Re: kernel panic with clonned disk

Last edited by SkyTod (2014-12-05 12:59:45)

#12 2014-12-05 13:38:36

Re: kernel panic with clonned disk

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

Last edited by Spider.007 (2014-12-05 13:39:53)

#13 2014-12-05 13:42:08

Re: kernel panic with clonned disk

Yeah. You should replace the /dev/hda* entries with the uuid of the corresponding device. If you ls -l /dev/disk/by-uuid it should also show which uuid belongs to the harddrives (it’s just a link in the folder).
The entries have to look like:

#14 2014-12-05 14:09:15

Re: kernel panic with clonned disk

and my ls -l /dev/disk/by-uuid:

There is no sdb*, so it’s a problem, yeah?

#15 2014-12-05 15:01:41

Re: kernel panic with clonned disk

If you still have the original disk in your system you obviously have a conflict; since the UUID is the same for both disks. Do you want to keep the original (40G) drive? Because otherwise I’d temporarily disconnect it

#16 2014-12-05 15:28:58

Re: kernel panic with clonned disk

since the UUID is the same for both disks.

Right, that’s the reason. However I updated fstab with UUID= and it boots with kernel panic anyway. I don’t really have a clue why it happens. Isn’t it able to find ext3 driver?

#17 2014-12-05 17:19:25

Re: kernel panic with clonned disk

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

? Also; I still think two disks are not gonna help your boot process so I’d disconnect the old disk.

#18 2014-12-05 18:00:27

Re: kernel panic with clonned disk

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

? Also; I still think two disks are not gonna help your boot process so I’d disconnect the old disk.

I disconnected it of course. There is no way to run it because my LiveCD provides zsh, thus I can’t chroot to my bash. :-/

#19 2014-12-05 18:59:05

Re: kernel panic with clonned disk

If you give up, I recommend the rsync or tar method.

#20 2014-12-05 19:33:59

Re: kernel panic with clonned disk

I never used rsync before and don’t trust disk operations with unknown tools myself, is there accurate article somewhere?

#21 2014-12-05 19:40:18

Re: kernel panic with clonned disk

You can find something in google I’ll bet. use tar if you don’t wanna try rsync.

#22 2014-12-06 10:26:52

Re: kernel panic with clonned disk

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

? Also; I still think two disks are not gonna help your boot process so I’d disconnect the old disk.

I disconnected it of course. There is no way to run it because my LiveCD provides zsh, thus I can’t chroot to my bash. :-/

Why don’t you use the arch-iso; it provides arch-chroot which works even better? And I’ve never heard of zsh not being able to chroot, I’m pretty sure that should work just fine. Are you running chroot $DIR instead of chroot $DIR /bin/bash?

Источник

Mount error 6 mounting ext3

Профиль | Отправить PM | Цитировать

После установки не могу загрузить Mandriva 2006
Загрузка останавливается на следующем:

Creating root device
No resume device specifield
Mounting root fylesystem /dev/root
mount: error 6 mounting ext3 flags defaults
well, retrying without the option flags
.
.
И еще несколько строк в таком же духе
В конце
Kernel panic — not syncing: Attempted to kill init swithroot: mount failed: 22

Сообщения: 7
Благодарности:

В связи с тем, что система не стартует — логи не пишутся, поэтому пришлось ручками списывать целый экран текста.
(Приношу свои извинения за допущенные орфографические ошибки )

NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64 Kbytes
TCP established hash table entries: 131072 (order:8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
NET: Registered protocol family 1
Using IPI Shortcut mode
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Freeing unused kernel memory: 236k freed
Loading jbd.ko module
Loading ext3.ko module
Mounting /proc filesystem
Mounting sysfs
Creating device files
Mounting tmpfs on /dev
Creating root device
No resume device specified
Mounting root filesystem /dev/root
mount: error 6 mounting ext3 flags defaults
well, retrying without the option flags
mount: error 6 mounting ext3
well, retrying read-only without any flag
input: AT Translated Set 2 keyboard on isa0060/serio0
mount: error 6 mounting ext3
Switching to new root
ERROR opening /dev/console. 2
unmounting old /proc
unmounting old /sys
switchroot: mount failed: 22
Initrd finished
Kernel panic — not syncing: Attempted to kill init!

Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.

Конфигурация компьютера
Материнская плата: Biostar TForce 550
HDD: 200Gb Sata2
Блок питания: Asrock 430W
ОС: Ubuntu 9.04

——-
Вопреки популярному мнению, Unix — дружелюбная ОС.
Просто так случилось, что она очень избирательна в выборе друзей.

Сообщения: 7
Благодарности:

Нет все параметры родные

Свойства ЦП:
Тип ЦП DualCore Intel Pentium D 840
Псевдоним ЦП Smithfield
CPU stepping A0
Engineering Sample Нет
Имя ЦП CPUID Intel(R) Pentium(R) D CPU 3.20GHz
Версия CPUID 00000F44h

Частота ЦП:
Частота ЦП 3199.7 MHz (исходное: 3200 MHz)
Множитель ЦП 16.0x
CPU FSB 200.0 MHz (исходное: 200 MHz)

Кэш ЦП:
Кэш L1 трассировки 12K Instructions
Кэш L1 данных 16 Кб
Кэш L2 1 Мб per core (On-Die, ECC, ATC, Full-Speed)

Свойства BIOS:
Дата системной BIOS 08/23/06
Дата BIOS видеоадаптера 06/19/06
Тип Award BIOS Phoenix — AwardBIOS v6.00PG
Сообщение Award BIOS ASUS P5VD2-MX ACPI BIOS Revision 1002
DMI версия BIOS ASUS P5VD2-MX ACPI BIOS Revision 1002

Свойства графического процессора:
Видеоадаптер ATI Radeon X1600 Pro (RV530)
Кодовое название ГП RV530 (PCI Express x16 1002 / 71C2, Rev 00)
Частота ГП 500 МГц (исходное: 500 MHz)
Частота памяти 392 МГц (исходное: 400 MHz)

Motherboard ASUS P5VD2-MX ACPI BIOS Revision 1002
Motherboard DMIMOBO: ASUSTeK Computer INC. P5VD2-MX
PCI/AGP 1106-0327: VIA Standard Host Bridge [1106-0327] [NoDB]
PCI/AGP 1106-0591: VIA Serial ATA Controller — 0591 [1106-0591] [NoDB]
PCI/AGP 1106-1327: VIA Standard Host Bridge [1106-1327] [NoDB]
PCI/AGP 1106-2327: VIA Standard Host Bridge [1106-2327] [NoDB]
PCI/AGP 1106-3327: VIA Standard Host Bridge [1106-3327] [NoDB]
PCI/AGP 1106-4327: VIA Standard Host Bridge [1106-4327] [NoDB]
PCI/AGP 1106-5327: VIA I/O APIC Interrupt Controller [1106-5327] [NoDB]
PCI/AGP 1106-6327: VIA Security Device [1106-6327] [NoDB]
PCI/AGP 1106-7327: VIA Standard Host Bridge [1106-7327] [NoDB]
PCI/AGP 1106-A327: VIA PCI to PCI Bridge Controller [1106-A327] [NoDB]
PCI/AGP 1106-C327: VIA PCI to PCI Bridge Controller [1106-C327] [NoDB]
PCI/AGP 197B-2363: JMicron JMB36X RAID Controller [197B-2363] [NoDB]

Источник

Перенос старого MСBC 3 на виртуальную машину.

День добрый, уважаемые!

Помогите с проблемой. Ситуация следующая: Есть старенький сервер, уже морально и физически собравший чемоданы на тот свет(эксплуатировать его перестали где-то в 90-ых), но до сих пор используют как архив. Появилась мысль перенести его на vmware esxi. Сделал образ, залил на vmware, но появилась проблема. При запуске машины выдает: mount: error 6 mounting ext2 Ну и соответственно кернел паникует) На том динозавре было 2 RAIDа из скази дисков: 1 (на систему) и 5 (на бд oracle) Загрузился с livecd, посмотрел что он пытается грузится с cciss.. но диски то изменились. sda2 — система, sdb1 — oracle, sda1 — swap. Нашел это дело в LILO и переписал все запуски с sda2. Так же переписал диски в fstab и mtab. Но кернел все еще паникует) Подскажите что я делаю не так? В линуксе я не силен, так что прошу сильно не ругать)) Поиск в инете результатов особо не дал.. Прошу Вашей помощи!

то есть ты уверен, что должно корень действительно на sda2, в параметрах загрузки у тебя root=/dev/sda2, в fstab корень — /dev/sda2, а. что и в каком месте паникует? кроме initrd/initramfs больше ничего не придумывается, пока не скажешь, что и как «все еще паникует»

Корень точно на sda2. Какие ошибки вылетают: 1. /lib/cciss.o: init_module: No such device 2. ERROR: /bin/insmod exited abnormally! 3. mount: error 6 mounting ext2 4. pivotroot: pivot_root (/sysroot, /sysroot/initrd) failed: 2 5. umount /initrd/proc failed: 2 6. Kernel panicL No init found. Try passing init = option to kernel.

судя по pivot_root у тебя initrd используется. Вот его надо еще пересобрать

Источник

Adblock
detector

Источник

View previous topic :: View next topic

Author

Message

matthead
n00b
n00b

Joined: 04 Dec 2002
Posts: 63

Posted: Thu Nov 02, 2006 10:56 pm Post subject: initrd: error 6 mounting ext3

I’m moving the root volume from an IDE disk to a SCSI disk. Since my kernel doesn’t have the right SCSI driver compiled in, I figured I’d just compile it as a module and use an initrd to boot. Except I can’t get the initrd working the way it should!

The module I need is mptspi.ko. So I build the module and install it. Oops, mkinitrd isn’t part of «system.» So:

Code:

emerge mkinitrd

Now I’m ready to make the initrd. I run:

Code:

mkinitrd -v —preload mptspi /boot/initrd-2.6.16.16.gz 2.6.16.16

It correctly detects the dependencies, and sets up the initrd. I edit the GRUB config file appropriately, reboot, and get:

Code:

…

RAMDISK: Compressed image found at block 0

VFS: Mounted root (ext2 filesystem)

Red Hat nash version 3.5.7 starting

Loading mptbase.ko module

Fusion MPT base driver 3.03.07

Copyright (c) 1999-2005 LSI Logic Corporation

Loading mptscsih.ko module

Loading mptspi.ko module

Fusion MPT SPI Host driver 3.03.07

…

SCSI device sda: 8388608 512-byte hdwr sectors

sda: Write Protect is off

sda: cache data unavailable

sda: assuming drive cache: write through

SCSI device sda: 8388608 512-byte hdwr sectors

sda: Write Protect is off

sda: cache data unavailable

sda: assuming drive cache: write through

sda: sda1

sd 0:0:0:0: Attached scsi disk sda

Mounting /proc filesystem

Creating block devices

Creating root device

Mounting root filesystem

mount: error 6 mounting ext3

pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2

umount /initrd/proc failed: 2

And then a kernel panic, because it can’t find /sbin/init. So it loads the modules and detects the disk OK! I just didn’t get the next part, where it can’t mount the root filesystem. Yes, ext3 is compiled directly into the kernel. Everything it needs except the SCSI driver is compiled into the kernel. Since the SCSI driver is being loaded, it looks like it should work. Yes, the root device is on the kernel command line. GRUB config is:

Code:

kernel /boot/bzImage-2.6.16.16 root=/dev/sda1

initrd /boot/initrd-2.6.16.16.gz

After some poking around, I found in /linuxrc (inside the initrd):

Code:

echo 0x0100 >/proc/sys/real-root-dev

Why is this stuck in here? It looks like it’s overwriting my requested root device! So what is my root device? Well, ls -l /dev/sda1 shows the device numbers are 8,1. Sure enough, if I change this line to

Code:

echo 0x0801 >/proc/sys/real-root-dev

It works! Mostly. I still get the errors above, but instead of a kernel panic the system actually boots! On the other hand, if I comment the line out in linuxrc, the system doesn’t boot at all (slightly different error message, though «cannot find device sda1» or something similar). Can anyone help me figure out just what the heck is going on here? Honestly, I don’t think I ever had this much trouble with initrd when using Red Hat/Fedora. Of course, Red Hat always used labels for mounting, not device names.

Arrgh! At least I got it kinda working. Any thoughts?
_________________
Matt

Linux Filesystem Features

Last edited by matthead on Tue Nov 07, 2006 6:19 am; edited 1 time in total

xoomix
Guru
Guru

Joined: 02 Jan 2003
Posts: 489

Posted: Thu Nov 02, 2006 11:04 pm Post subject:

Try appending a «real_root=/dev/blah» line in your Grub conf — using Genkernel shows you the exact verbiage at the end.

matthead
n00b
n00b

Joined: 04 Dec 2002
Posts: 63

Posted: Tue Nov 07, 2006 6:18 am Post subject:

That doesn’t work either. I get the same error as before. I expect that /proc/sys/real-root-dev overrides it, since it’s a post-boot action. _________________ Matt Linux Filesystem Features

DamFam
n00b
n00b

Joined: 20 Jun 2006
Posts: 18

Posted: Tue Nov 07, 2006 1:37 pm Post subject:

I had this problem as well. The problem was two-fold First, there was no device listing for my root file system in the /dev directory of my initrd. For example, my root filesystem ( / ) was on sda, partition 3. There was no listing in the /dev directory in the initramfs for sda3, only sda, and sda1 (which is my boot partition). booting the livecd and mounting my partitions, I corrected that (uncompressing the initrd, then mounting it, I went in and made a new node (mknod) for sda3) this error: mount: error 6 mounting ext3 went away. The root filesystem was loaded, and ext3 was initialized. I was still getting: pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 umount /initrd/proc failed: 2 However. This is because you need a «initrd» directory on your root filesystem. Booted with the livecd, mounted my root partition and created the /initrd directory. Unmounted, rebooted… and SUCCESS! The system boots without a single error. Hope this helps.

matthead
n00b
n00b

Joined: 04 Dec 2002
Posts: 63

Posted: Wed Nov 08, 2006 8:35 am Post subject:

No dice, unfortunately. I created /dev/sda and /dev/sda1 nodes on the failing initrd, and the behavior is the same. As for the second part, I do have an /initrd directory on the root fs. Curiously, even with the working initrd I still get the pivot_root and umount errors. I wonder if those have to do with whatever is causing the «error mounting ext3,» which I also still get on the working initrd. Once the system is booted and I login, I can «umount /initrd/proc; umount /initrd» with no problem. Thanks for the suggestions! I just wish they worked for me. Of course, this also raises the question of why Gentoo’s mkinitrd isn’t creating the devices. _________________ Matt Linux Filesystem Features

DamFam
n00b
n00b

Joined: 20 Jun 2006
Posts: 18

Posted: Wed Nov 08, 2006 1:24 pm Post subject:

matthead wrote:

No dice, unfortunately. I created /dev/sda and /dev/sda1 nodes on the failing initrd, and the behavior is the same.

As for the second part, I do have an /initrd directory on the root fs. Curiously, even with the working initrd I still get the pivot_root and umount errors. I wonder if those have to do with whatever is causing the «error mounting ext3,» which I also still get on the working initrd. Once the system is booted and I login, I can «umount /initrd/proc; umount /initrd» with no problem.

Thanks for the suggestions! I just wish they worked for me. Of course, this also raises the question of why Gentoo’s mkinitrd isn’t creating the devices.

Make sure ALL your filesystems are there.

/dev/sda is the disk device

/dev/sda1 is one partition (is this your /boot or «/» directory?) you need both in there.

Also, make sure the node numbers are right.

For example, /dev/sda might be 8,0, /dev/sda1 8,1 /dev/sda2 8,2 etc etc

matthead
n00b
n00b

Joined: 04 Dec 2002
Posts: 63

Posted: Wed Nov 08, 2006 4:40 pm Post subject:

Yes, I understand the problem. /dev/sda1 is my root filesystem; I did not separate /boot. And /dev/sda1 is 0x0801 on every Linux machine I’ve ever been on, and that’s what I created the node as.

Code:

logan ~:0# gunzip /boot/initrd-bad-2.6.16.16.gz

logan ~:0# mount -t ext2 -o loop /boot/initrd-bad-2.6.16.16 /mnt/cdrom

logan ~:0# ls -l /mnt/cdrom/dev

total 2

drwxr-xr-x 2 root root 1024 Nov 8 02:09 ./

drwxr-xr-x 9 root root 1024 Nov 4 15:02 ../

crw-r—r— 1 root root 5, 1 Nov 4 15:02 console

crw-r—r— 1 root root 1, 3 Nov 4 15:02 null

brw-r—r— 1 root root 1, 1 Nov 4 15:02 ram

brw-r—r— 1 root root 8, 0 Nov 8 02:09 sda

brw-r—r— 1 root root 8, 1 Nov 8 02:09 sda1

crw-r—r— 1 root root 4, 0 Nov 4 15:02 systty

crw-r—r— 1 root root 4, 1 Nov 4 15:02 tty1

crw-r—r— 1 root root 4, 2 Nov 4 15:02 tty2

crw-r—r— 1 root root 4, 3 Nov 4 15:02 tty3

crw-r—r— 1 root root 4, 4 Nov 4 15:02 tty4

You forgot to remind me to make sure that I created them as block devices, not character devices.

Looking again at the linuxrc script, I see that it’s supposed to make the necessary devices itself! There’s a line:

Code:

mkdevices /dev

The nash man page says that’s supposed to create a node for everything in /proc/partitions. I’ll have to figure out what the contents of /proc/partitions is at that point in time. But the linuxrc is still mounting «/dev/root» as the root filesystem, not «/dev/sda1.» I’m curious what your working linuxrc script looks like. Does it have this junk about «echo 0x0100» into real-root-dev?

Code:

echo «Loading mptbase.ko module»

insmod /lib/mptbase.ko

echo «Loading mptscsih.ko module»

insmod /lib/mptscsih.ko

echo «Loading mptspi.ko module»

insmod /lib/mptspi.ko

echo Mounting /proc filesystem

mount -t proc /proc /proc

echo Creating block devices

mkdevices /dev

echo Creating root device

mkrootdev /dev/root

echo 0x0100 > /proc/sys/kernel/real-root-dev

echo Mounting root filesystem

mount -o defaults —ro -t ext3 /dev/root /sysroot

pivot_root /sysroot /sysroot/initrd

umount /initrd/proc

_________________
Matt

Linux Filesystem Features

wynn
Advocate

Joined: 01 Apr 2005
Posts: 2421
Location: UK

Posted: Wed Nov 08, 2006 4:55 pm Post subject:

Just a tiny little point, shouldn’t

Code:

mount -o defaults —ro -t ext3 /dev/root /sysroot

Code:

mount -o defaults,ro -t ext3 /dev/root /sysroot

There doesn’t appear to be a —ro flag.

Code:

mount: error 6 mounting ext3

appears to be

Code:

ENXIO 6 /* No such device or address */

which, as you’ve already found out, is due to the missing /dev/sda1

matthead wrote:

Honestly, I don’t think I ever had this much trouble with initrd when using Red Hat/Fedora. Of course, Red Hat always used labels for mounting, not device names

Code:

mkrootdev /dev/root

echo 0x0100 > /proc/sys/kernel/real-root-dev

From the nash manpage

Quote:

mkrootdev path

Makes path a block inode for the device which should be mounted as root. To determine this device nash uses the device suggested by the root= kernel command line argument (if root=LABEL is used devices are probed to find one with that label). If no root= argument is available, /proc/sys/kernel/real-root-dev provides the device number.

So it seems that /dev/root is being made into /dev/sda1 (8,1) but, as /proc/sys/kernel/real-root-dev is being set to /dev/ram0 afterwards it should have no effect on what /dev/root is set to.
_________________
The avatar is jorma, a «duck» from «Elephants Dream»: the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.

matthead
n00b
n00b

Joined: 04 Dec 2002
Posts: 63

Posted: Wed Nov 08, 2006 8:37 pm Post subject:

wynn wrote:

There doesn’t appear to be a —ro flag.

This is nash’s builtin mount, not /bin/mount. nash mount does have an —ro switch.

wynn wrote:

So it seems that /dev/root is being made into /dev/sda1 (8,1) but, as /proc/sys/kernel/real-root-dev is being set to /dev/ram0 afterwards it should have no effect on what /dev/root is set to.

But I noted before that I still cannot boot with this initrd, even if I comment out the echo! And that’s with a root=/dev/sda1 kernel command line, and I’ve never commented out or removed the mkrootdev or mkdevices commands.
_________________
Matt

Linux Filesystem Features

Display posts from previous:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Источник

#1 2014-12-04 09:55:15

SkyTod: Member; Registered: 2009-09-01; Posts: 226

kernel panic with clonned disk

Hey,

I have an old hard drive with pretty old software for server needs and I decided to change hard drive. I bought new one. Ran the following:

dd if=/dev/sda of=/dev/sdb bs=512 conv=noerror,sync

Rebooted to load from sdb, GRUB loads without troubles, but got the kernel panic:

...
Mounting root filesystem
mount: error 6 mounting ext3
pivotroot: pivot_root(/sysroot./sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Freeing unsed kernel memory: 116k freed
Kernel panic: No init  found. Try passing init= option to kernel.

What’s wrong with my dd?! What did I wrong?! What the different between these tow hard disks? Because my original hard drive loads well.

#2 2014-12-04 10:45:14

graysky: Wiki Maintainer; From: :wq; Registered: 2008-12-01; Posts: 10,472; Website

Re: kernel panic with clonned disk

#3 2014-12-04 10:54:56

SkyTod: Member; Registered: 2009-09-01; Posts: 226

Re: kernel panic with clonned disk

graysky wrote:

I wouldn’t use dd myself.

Why? It’s recommended way according to the wiki.

graysky wrote:

Remember to update your bootloader if using a different layout or uuids as well as your fstab.

See here:

This will clone the entire drive, including MBR (and therefore bootloader), all partitions, UUIDs, and data.

Is it a mistake in the article?

Last edited by SkyTod (2014-12-04 10:55:26)

#4 2014-12-04 11:29:54

graysky: Wiki Maintainer; From: :wq; Registered: 2008-12-01; Posts: 10,472; Website

Re: kernel panic with clonned disk

The wiki recommends several things that I disagree with… My suggestion is just one way to do things. You have the freedom to select an alternative if you wish. As you have already done so, and ran into problems, I offered up an alternative. Do as you wish.

#5 2014-12-04 11:52:32

null: Member; Registered: 2009-05-06; Posts: 397

Re: kernel panic with clonned disk

Was the sda drive mounted writable and was this the os you used for dd? — Try a live usb system with unmounted sda.

For the uuids: compare blkid output and fstab.

#6 2014-12-04 12:10:40

SkyTod: Member; Registered: 2009-09-01; Posts: 226

Re: kernel panic with clonned disk

graysky wrote:

The wiki recommends several things that I disagree with… My suggestion is just one way to do things. You have the freedom to select an alternative if you wish. As you have already done so, and ran into problems, I offered up an alternative. Do as you wish.

Thank you for that, can you share some step-by-step manual?

null wrote:

Was the sda drive mounted writable and was this the os you used for dd? — Try a live usb system with unmounted sda.

First time I tried my archlinux, then my LiveCD (some minor linux build) with unmounted both sd* — the same result.

null wrote:

For the uuids: compare blkid output and fstab.

Do you mean /etc/fstab? How can I compare blkid?

#7 2014-12-04 13:46:42

SkyTod: Member; Registered: 2009-09-01; Posts: 226

Re: kernel panic with clonned disk

Just checked. There are no /etc/blkid.tabs, no differences in fstabs.

#8 2014-12-04 23:02:45

null: Member; Registered: 2009-05-06; Posts: 397

Re: kernel panic with clonned disk

#9 2014-12-05 09:47:25

SkyTod: Member; Registered: 2009-09-01; Posts: 226

Re: kernel panic with clonned disk

null wrote:

The command blkid will give you a list of blockdevices and their uuid.

There is no blkid on my LiveCD, is there any other tools?

#10 2014-12-05 12:39:09

Spider.007: Member; Registered: 2004-06-20; Posts: 1,175

Re: kernel panic with clonned disk

blkid is provided by util-linux, you can install that on your livecd. Alternatively; simply execute ls /dev/disk/by-uuid/

#11 2014-12-05 12:58:52

SkyTod: Member; Registered: 2009-09-01; Posts: 226

Re: kernel panic with clonned disk

Okay, my fstabs:

/dev/hda2               /                       ext3    defaults        1 1
/dev/hda1               /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /proc                   proc    defaults        0 0
/dev/hda5               swap                    swap    defaults        0 0
/dev/cdrom              /mnt/cdrom              udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu 0 0

ls /dev/disk/by-uuid/

/dev/disk/by-uuid/FEE0-AD1E

/dev/disk/by-uuid/9340cd5c-f738-11da-9b27-fbc3f2afcb6d

/dev/disk/by-uuid/2cfa08ec-f738-11da-8e32-bbd5b9627316

Last edited by SkyTod (2014-12-05 12:59:45)

#12 2014-12-05 13:38:36

Spider.007: Member; Registered: 2004-06-20; Posts: 1,175

Re: kernel panic with clonned disk

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

Last edited by Spider.007 (2014-12-05 13:39:53)

#13 2014-12-05 13:42:08

null: Member; Registered: 2009-05-06; Posts: 397

Re: kernel panic with clonned disk

UUID="UUID of your root device"             /                       ext3    defaults        1 1

https://wiki.archlinux.org/index.php/Fstab#UUIDs

#14 2014-12-05 14:09:15

SkyTod: Member; Registered: 2009-09-01; Posts: 226

Re: kernel panic with clonned disk

My fdisk -l:

Disk /dev/sda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x08820881

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1           6       48163+  83  Linux
/dev/sda2   *           7        1281    10241437+  83  Linux
/dev/sda3            1282        1330      393592+   f  W95 Ext'd (LBA)
/dev/sda5            1282        1330      393561   82  Linux swap / Solaris

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x08820881

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1           6       48163+  83  Linux
/dev/sdb2   *           7        1281    10241437+  83  Linux
/dev/sdb3            1282        1330      393592+   f  W95 Ext'd (LBA)
/dev/sdb5            1282        1330      393561   82  Linux swap / Solaris

Disk /dev/sdc: 4016 MB, 4016046080 bytes
255 heads, 63 sectors/track, 488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00681f73

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1         489     3921888+   c  W95 FAT32 (LBA)
Partition 1 has different physical/logical endings:
     phys=(487, 254, 63) logical=(488, 65, 25)

and my ls -l /dev/disk/by-uuid:

total 0
lrwxrwxrwx 1 root root 10 2014-12-05 14:44 2cfa08ec-f738-11da-8e32-bbd5b9627316 -> ../../sda2
lrwxrwxrwx 1 root root 10 2014-12-05 14:44 9340cd5c-f738-11da-9b27-fbc3f2afcb6d -> ../../sda1
lrwxrwxrwx 1 root root 10 2014-12-05 14:42 FEE0-AD1E -> ../../sdc1

There is no sdb*, so it’s a problem, yeah?

#15 2014-12-05 15:01:41

Spider.007: Member; Registered: 2004-06-20; Posts: 1,175

Re: kernel panic with clonned disk

#16 2014-12-05 15:28:58

SkyTod: Member; Registered: 2009-09-01; Posts: 226

Re: kernel panic with clonned disk

Spider.007 wrote:

since the UUID is the same for both disks.

Right, that’s the reason. However I updated fstab with UUID= and it boots with kernel panic anyway. I don’t really have a clue why it happens. Isn’t it able to find ext3 driver?

#17 2014-12-05 17:19:25

Spider.007: Member; Registered: 2004-06-20; Posts: 1,175

Re: kernel panic with clonned disk

Did you:

Spider.007 wrote:

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

? Also; I still think two disks are not gonna help your boot process so I’d disconnect the old disk.

#18 2014-12-05 18:00:27

SkyTod: Member; Registered: 2009-09-01; Posts: 226

Re: kernel panic with clonned disk

Spider.007 wrote:

Did you:

Spider.007 wrote:

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

? Also; I still think two disks are not gonna help your boot process so I’d disconnect the old disk.

I disconnected it of course. There is no way to run it because my LiveCD provides zsh, thus I can’t chroot to my bash. :-/

#19 2014-12-05 18:59:05

graysky: Wiki Maintainer; From: :wq; Registered: 2008-12-01; Posts: 10,472; Website

Re: kernel panic with clonned disk

If you give up, I recommend the rsync or tar method…

graysky wrote:

I wouldn’t use dd myself. I recommend that you partition the new drive to your liking, then simply rsync over the old hdd to the new one. If you have multiple partitions to mirror, you can do them one at a time or if you have a more simplified setup in the new drive, simply mount them up and sync over as you see fit. Remember to update your bootloader if using a different layout or uuids as well as your fstab.

#20 2014-12-05 19:33:59

SkyTod: Member; Registered: 2009-09-01; Posts: 226

Re: kernel panic with clonned disk

I never used rsync before and don’t trust disk operations with unknown tools myself, is there accurate article somewhere?

#21 2014-12-05 19:40:18

graysky: Wiki Maintainer; From: :wq; Registered: 2008-12-01; Posts: 10,472; Website

Re: kernel panic with clonned disk

You can find something in google I’ll bet… use tar if you don’t wanna try rsync.

#22 2014-12-06 10:26:52

Spider.007: Member; Registered: 2004-06-20; Posts: 1,175

Re: kernel panic with clonned disk

SkyTod wrote:

Spider.007 wrote:

Did you:

Spider.007 wrote:

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

? Also; I still think two disks are not gonna help your boot process so I’d disconnect the old disk.

I disconnected it of course. There is no way to run it because my LiveCD provides zsh, thus I can’t chroot to my bash. :-/

#23 2014-12-06 14:10:04

ANOKNUSA: Member; Registered: 2010-10-22; Posts: 2,141

Re: kernel panic with clonned disk

Spider.0007 wrote:

There is no way to run it because my LiveCD provides zsh, thus I can’t chroot to my bash. :-/

I get the feeling the OP has some aliases and/or plugins they’ve become dependent on. arch-chroot defaults to bash in sh-compatibility mode; one can always just run bash inside the chroot.

SkyTod wrote:

I never used rsync before and don’t trust disk operations with unknown tools myself, is there accurate article somewhere?

rsync won’t destroy data (unless you explicitly tell it to), won’t alter any disk or partition information (like a UUID) and there’s plenty of easy-to-find and easy-to-understand info about it. It’s been widely used for nearly twenty years.

Источник

Arch Linux

You are not logged in.

#1 2014-12-04 09:55:15

kernel panic with clonned disk

I have an old hard drive with pretty old software for server needs and I decided to change hard drive. I bought new one. Ran the following:

Rebooted to load from sdb, GRUB loads without troubles, but got the kernel panic:

What’s wrong with my dd?! What did I wrong?! What the different between these tow hard disks? Because my original hard drive loads well.

#2 2014-12-04 10:45:14

Re: kernel panic with clonned disk

#3 2014-12-04 10:54:56

Re: kernel panic with clonned disk

I wouldn’t use dd myself.

Why? It’s recommended way according to the wiki.

Remember to update your bootloader if using a different layout or uuids as well as your fstab.

This will clone the entire drive, including MBR (and therefore bootloader), all partitions, UUIDs, and data.

Is it a mistake in the article?

Last edited by SkyTod (2014-12-04 10:55:26)

#4 2014-12-04 11:29:54

Re: kernel panic with clonned disk

#5 2014-12-04 11:52:32

Re: kernel panic with clonned disk

Was the sda drive mounted writable and was this the os you used for dd? — Try a live usb system with unmounted sda.

For the uuids: compare blkid output and fstab.

#6 2014-12-04 12:10:40

Re: kernel panic with clonned disk

Thank you for that, can you share some step-by-step manual?

Was the sda drive mounted writable and was this the os you used for dd? — Try a live usb system with unmounted sda.

First time I tried my archlinux, then my LiveCD (some minor linux build) with unmounted both sd* — the same result.

For the uuids: compare blkid output and fstab.

Do you mean /etc/fstab? How can I compare blkid?

#7 2014-12-04 13:46:42

Re: kernel panic with clonned disk

Just checked. There are no /etc/blkid.tabs, no differences in fstabs.

#8 2014-12-04 23:02:45

Re: kernel panic with clonned disk

#9 2014-12-05 09:47:25

Re: kernel panic with clonned disk

The command blkid will give you a list of blockdevices and their uuid.

There is no blkid on my LiveCD, is there any other tools?

#10 2014-12-05 12:39:09

Re: kernel panic with clonned disk

blkid is provided by util-linux, you can install that on your livecd. Alternatively; simply execute ls /dev/disk/by-uuid/

#11 2014-12-05 12:58:52

Re: kernel panic with clonned disk

Last edited by SkyTod (2014-12-05 12:59:45)

#12 2014-12-05 13:38:36

Re: kernel panic with clonned disk

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

Last edited by Spider.007 (2014-12-05 13:39:53)

#13 2014-12-05 13:42:08

Re: kernel panic with clonned disk

#14 2014-12-05 14:09:15

Re: kernel panic with clonned disk

and my ls -l /dev/disk/by-uuid:

There is no sdb*, so it’s a problem, yeah?

#15 2014-12-05 15:01:41

Re: kernel panic with clonned disk

#16 2014-12-05 15:28:58

Re: kernel panic with clonned disk

since the UUID is the same for both disks.

Right, that’s the reason. However I updated fstab with UUID= and it boots with kernel panic anyway. I don’t really have a clue why it happens. Isn’t it able to find ext3 driver?

#17 2014-12-05 17:19:25

Re: kernel panic with clonned disk

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

? Also; I still think two disks are not gonna help your boot process so I’d disconnect the old disk.

#18 2014-12-05 18:00:27

Re: kernel panic with clonned disk

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

? Also; I still think two disks are not gonna help your boot process so I’d disconnect the old disk.

I disconnected it of course. There is no way to run it because my LiveCD provides zsh, thus I can’t chroot to my bash. :-/

#19 2014-12-05 18:59:05

Re: kernel panic with clonned disk

If you give up, I recommend the rsync or tar method.

#20 2014-12-05 19:33:59

Re: kernel panic with clonned disk

I never used rsync before and don’t trust disk operations with unknown tools myself, is there accurate article somewhere?

#21 2014-12-05 19:40:18

Re: kernel panic with clonned disk

You can find something in google I’ll bet. use tar if you don’t wanna try rsync.

#22 2014-12-06 10:26:52

Re: kernel panic with clonned disk

It seems re-running grub-install on the new disk might fix this (you can do this from the livecd). I’d also re-run `mkinitcpio`

? Also; I still think two disks are not gonna help your boot process so I’d disconnect the old disk.

I disconnected it of course. There is no way to run it because my LiveCD provides zsh, thus I can’t chroot to my bash. :-/

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

Темы без ответов
Активные темы
Поиск
Статус форума

Проблемы при установке (То ли с приводом, то ли с биосом)

Проблемы при установке

Сообщение Danila » 25.05.2008 09:59

Re: Проблемы при установке

Сообщение MadDog » 25.05.2008 16:34

Re: Проблемы при установке

Сообщение t2a » 25.05.2008 16:49

«И как решить проблему?»

А что, системные блоки ПК1 и ПК2 идентичны по «железу»?
Может раскроете «тайну» ПК1 и ПК2 поподробнее?
Например:
ПК1:
Матплата — Microstar MSI NEO-F 965p (MS-7235)
и т.д. и т.п.

Re: Проблемы при установке

Сообщение Danila » 31.05.2008 11:40

ПК1:
Мат. плата Socket 775 Intel «DQ965GFEKR»
ПК2:
ASUS P2B

Может быть это и в железе дело, но почему тогда LiveCD на обоих ПК грузится? И меню диска тоже загружается на обоих ПК, а вот когда жму Install тут и начинается.

Re: Проблемы при установке

Сообщение t2a » 31.05.2008 22:01

«Может быть это и в железе дело»

А «и т.д. и т.п.» не надо?

За Вас, что-ли, по сайтам производителей бегать и выяснять: SonyNEC 5170 — SATA или PATA?
И так далее.

Посему Вам в ПОИСК .

Re: Проблемы при установке

Сообщение Danila » 18.09.2008 19:36

Re: Проблемы при установке

Сообщение t2a » 19.09.2008 00:46

«Шаг 2 зависло при загрузке. Что делать?»

Что-нибудь отображается на экране, «-«, «крякозябры», или еще что, или ничего?
Kernel panic?
. и .
КОГДА научитесь приемлемо описывать проблемы?
Тяжко?
Тогда кто и (или) что мешает фотоснимок, в конце концов, приложить?
Или прикажете «по оперению . «?

Re: Проблемы при установке

Сообщение Danila » 19.09.2008 06:08

Re: Проблемы при установке

Сообщение Danila » 20.09.2008 05:04

Re: Проблемы при установке

Сообщение eddy » 20.09.2008 12:42

Re: Проблемы при установке

Сообщение t2a » 20.09.2008 13:10

«Kernel panic — not syncing: Attemted to kill init!»

А в Поиск набрав Kernel panic — not syncing: Attemted to kill init можно быстро найти:
http://opensource.com.ua/forum/archive/index.php/t-157.html
и еще-чего по теме найдется.
Даже в разделе «Вопрос новичка» энную часть Net в раздел не переписывают. Накладно.

Re: Проблемы при установке

Сообщение Danila » 20.09.2008 20:57

Готово!
Оказалось всё намного проще.
Спасибо t2a, я зашел по ссылкам и двинулся с мертвой точки.

I ШАГ
Как только с диска загружается меню:
1. Загрузка с жесткого диска
2. Установка
.
n. тест памяти

под ними строка параметров. В самый конец я прописал ту команду, которую нашел по ссылкам. Чудо! Установка пошла!

установка завершилась. Кстати надо запомнить путь до корневого раздела. Например, /dev/hde5. Особенно то что он hde5

II ШАГ
С жесткого диска ОС грузится не стала, потому пришлось искать решение данной проблемы. Так же как и в предыдущем случае на форуме было упоминание о том, что нужно прописать в загрузчике (LILO, GRUB) ту же: all-generic-ide я стал искать «как».
В том же меню диска под установкой, может еще чуть ниже есть пункт «Загрузить аварийную систему»
1. Встает на нее курсором. И снова прописываем all-generic-ide. В противном случае ничего не загрузится
2. В загрузившемся меню после операций с LILO будет «загрузить консоль». Жмем!
3. Далее вот такой код

Послесловие
Огромную благодарность хочу выразить свою новому товарищу по сети, которого я нашел в одном из месенджеров, который терпеливо и с понимаем мне всё объяснил. Кое-что приходилось проделывать несколько раз.
Уважаемые знатоки! Не бойтесь всё расписывать!
Уважаемые модераторы! Пожалуйста почистите форум от ненужных дубликатов, чтобы упростить поиск, и опять же уменьшить количество однотипных постов, потому что пользователю действительно затруднительно искать в таком количестве постов нужный ему. И выходит, что быстрее по времени завести новую тему. Тем самым круг замыкается. И я их понимаю.

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

Темы без ответов
Активные темы
Поиск
Статус форума

Проблемы при установке (То ли с приводом, то ли с биосом)

Проблемы при установке

Сообщение Danila » 25.05.2008 09:59

Re: Проблемы при установке

Сообщение MadDog » 25.05.2008 16:34

Re: Проблемы при установке

Сообщение t2a » 25.05.2008 16:49

«И как решить проблему?»

Re: Проблемы при установке

Сообщение Danila » 31.05.2008 11:40

ПК1:
Мат. плата Socket 775 Intel «DQ965GFEKR»
ПК2:
ASUS P2B

Re: Проблемы при установке

Сообщение t2a » 31.05.2008 22:01

«Может быть это и в железе дело»

А «и т.д. и т.п.» не надо?

За Вас, что-ли, по сайтам производителей бегать и выяснять: SonyNEC 5170 — SATA или PATA?
И так далее.

Посему Вам в ПОИСК .

Re: Проблемы при установке

Сообщение Danila » 18.09.2008 19:36

Re: Проблемы при установке

Сообщение t2a » 19.09.2008 00:46

«Шаг 2 зависло при загрузке. Что делать?»

Re: Проблемы при установке

Сообщение Danila » 19.09.2008 06:08

Re: Проблемы при установке

Сообщение Danila » 20.09.2008 05:04

Re: Проблемы при установке

Сообщение eddy » 20.09.2008 12:42

Re: Проблемы при установке

Сообщение t2a » 20.09.2008 13:10

«Kernel panic — not syncing: Attemted to kill init!»

Re: Проблемы при установке

Сообщение Danila » 20.09.2008 20:57

Готово!
Оказалось всё намного проще.
Спасибо t2a, я зашел по ссылкам и двинулся с мертвой точки.

I ШАГ
Как только с диска загружается меню:
1. Загрузка с жесткого диска
2. Установка
.
n. тест памяти

Источник

Готово!
Оказалось всё намного проще.
Спасибо t2a, я зашел по ссылкам и двинулся с мертвой точки.

I ШАГ
Как только с диска загружается меню:
1. Загрузка с жесткого диска
2. Установка
…
n. тест памяти

Код: Выделить всё

строка параметров: "текст по умолчанию" all-generic-ide

Код: Выделить всё

mkdir /tmp/disk # создаем каталог для монтирования нашего системного диска
mount /dev/hde5 #собственно монтируем. В моем случае это hde5, в остальных hd*, где * 2 конечных символа вашего системного диска
chroot /tmp/disk #chroot команда замечательная! Дает возможность работать прямо с установленной на жесткий диск ОС, а посему запускаем:
mc /etc/lilo.conf #жмем F4, находим строку с названием linux* (* - по умолчанию, может и не быть ), далее последнюю строку параметров для linux  и теперь в конце этой строки прописываем all-generic-ide. Эту операцию повторите и для других записей "безопасный режим", например. Кромен Windows :)
lilo # теперь всё. Перезагружаемся. Всё готова. Конец. Хотя на самом деле начало начал :). Да, потому что вы читаете этот пост с целью как это сделать :)

Источник