fsck.ext2 - сбой при загрузке нового ядра...

[defa]

После сборки нового ядра и попытки загрузиться с него, получаю следующее сообщение:

checking root file system...

fsck.ext2: No souch file or directory while trying to open /dev/hda6:

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblok is corrupt, and you might try running with e2fsck an alternative superblok:

e2fsck -b 8193 <device>

fsck failed. Please repair manually and reboot. Please note that the root file systen is currently mounted read-only. To remount it read-write:

# mount -n -o remount, rw /

CONTROL-D will exit from this shell and REBOOT the system.

Give root password from maintenans

(or type Control-D for normal startup):

Кто знает, с чего бы это... у меня мысли уже кончились...

[SignFinder]

Цитата:

Give root password from maintenans (or type Control-D for normal startup):

вводишь пароль рута и вручную чекаешь файловую систему

[defa]

Да, с этим понятно, прочитал даже тута как чекать...:

If there's another operative system in the same disk together with Linux, it can be tested if the harddisk operates normally under the other system. When this doesn't occur, the cause lies probably on a hardware problem.

Check the right placement of the data cable on the mainboard and on the hard disk. Remove the cable and plug it again on the board and on the disk. Because of corrosion could be the conductivity of the wrap connection affected. This can be repaired as follows.

Are you sure that your hardware is all right and that all data cables are properly plugged into the computer, then you can try to fix the filesystem with e2fsck (Here we are taking the ext-2-Filesystem. It is the standard one.) e2fsck is able to seek your disk for bad sectors, and to mark them so that they will never we written again.

Attention: You have to be aware, that e2fsck can't cause any wonder. In some cases (specially if there are hardware problems or severe damaged filesystems) the use of e2fsck may lead to an aggravation of your problem.

Do always before manually executing

e2fsck

a backup of all important files !!!

The user handbook contains the complete manual-page of e2fsck. Please read it, and execute the program from the rescue system (boot from CD or from SuSE installation disk and start the rescue system. Don't mount the concerned disk, see manual).

The command to repair the filesystem is (here we will take: /dev/sda5 as the damaged one):

e2fsck -f -c -y /dev/sda5

The meaning of the options es:

• -f : Checks even if it seems that the filesystem is looking good.

• -c : Looks for "Badblocks". These will be marked and they will never be written again.

• -y : Takes "yes" as answer to all questions. This way you can handle hundreds of mistakes without having to answer what to do in every single one of them. If you don't want to use this option, just leave it away.

If the new try with e2fsck fails (the first try is already failed while booting), then only remains in the most cases formatting and installing again this partition.

Но у меня возник вопрос, с чего это файловая система упала? Обрубания питания не было, работу завершал корректно. Единственное, что сделала, это грузанулся с новым ядром. И вот пожалуйста... Это может быть связанно с некорректной конфигурацией ядра перед компиляцией?

[SignFinder]

может бэд блок на винте

[defa]

Но ведь со старым ядром такого не происходит....

[defa]

Не помогает. При попытке запустить

e2fsck -f -c -y /dev/hda6

выдаёт:

fsck.ext2: No souch file or directory while trying to open /dev/hda6:

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblok is corrupt, and you might try running with e2fsck an alternative superblok:

e2fsck -b 8193 <device>

если запускаешь

e2fsck -b 8193 /dev/hda6 - та же фигня:

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblok is corrupt, and you might try running with e2fsck an alternative superblok:

e2fsck -b 8193 <device>