Собствено капнул в сторону fsck
По паралельному мануалу еще выполнил
fdisk и
blkid:
fdiskubuntu@ubuntu:~$ sudo fdisk -l
Диск /dev/sda: 498.0 ГБ, 497998102528 байт
255 heads, 63 sectors/track, 60544 cylinders
Units = цилиндры of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5328f87f
Устр-во Загр Начало Конец Блоки Id Система
/dev/sda1 1 5 40131 de Dell Utility
/dev/sda2 2437 60059 462848000 83 Linux
/dev/sda3 * 6 2437 19530752 83 Linux
/dev/sda4 60059 60545 3904513 5 Расширенный
/dev/sda5 60059 60545 3904512 82 Linux своп / Solaris
Пункты таблицы разделов расположены не в дисковом порядке
blkidubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" TYPE="vfat"
/dev/sda2: LABEL="home" UUID="dc709944-c8f9-4cd0-a90b-63a41ffac016" TYPE="ext4"
/dev/sda3: UUID="dcb4eed7-3eeb-4af4-a98f-caec4a68839f" TYPE="ext4"
/dev/sda5: UUID="3b96fc61-76e5-4479-b3a2-95ad4eb7fbf6" TYPE="swap"
Далее после того как определил необходимый раздел выполнил
fsck ubuntu@ubuntu:~$ sudo fsck /dev/sda3
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
/dev/sda3 is mounted.
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Do you really want to continue (y/n)? no
check aborted.
ubuntu@ubuntu:~$ sudo umount /dev/sda3
ubuntu@ubuntu:~$ sudo fsck /dev/sda3
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
/dev/sda3 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 135691 has zero dtime. Fix<y>? yes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 135695 was part of the orphaned inode list. FIXED.
Inode 135696 was part of the orphaned inode list. FIXED.
Inode 135698 was part of the orphaned inode list. FIXED.
Inode 135780 was part of the orphaned inode list. FIXED.
Inode 137159 was part of the orphaned inode list. FIXED.
Inode 137160 was part of the orphaned inode list. FIXED.
Inode 1056958 was part of the orphaned inode list. FIXED.
Inode 1060982 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(1496048--1496063) -4503581 -4503600 -4503622 -4503669 -4524918 -(4552683--4552684) -(4553628--4553629) -4553795 -4553806 -4553813 -4553832 -4553842 -4553922 -4554013 -4554145 -4554161 -4554182 -4554195
Fix<y>? yes
Free blocks count wrong for group #45 (1428, counted=1444).
Fix<y>? yes
Free blocks count wrong for group #137 (11581, counted=11585).
Fix<y>? yes
Free blocks count wrong for group #138 (23329, counted=23345).
Fix<y>? yes
Free blocks count wrong (2460166, counted=2460202).
Fix<y>? yes
Inode bitmap differences: -135691 -(135695--135696) -135698 -135780 -(137159--137160) -1056958 -1060982
Fix<y>? yes
Free inodes count wrong for group #16 (2032, counted=2039).
Fix<y>? yes
Free inodes count wrong for group #128 (0, counted=1).
Fix<y>? yes
Free inodes count wrong for group #129 (87, counted=88).
Fix<y>? yes
Free inodes count wrong (923907, counted=923916).
Fix<y>? yes
/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: 299076/1222992 files (0.2% non-contiguous), 2422230/4882432 blocks
При проверки на все вопросы задаваймые утилитой
fsck отвечал утвердительной.
После прогона перезагрузил сервак вроде бы проблески сознания появились и загрузка пропустила далбше
BusyBox (см. первый пост) консоли.
Грузилось очень долго, вобщем догрузило до окна выбора пользователя в графической оболочки, начал логиниться в граф оболочке и тут оболочка свернулась появилась граф консоль и начала валить [ fail ] -ами. Вобщем модули Zentyal и граф интерфейс не загрузился.
Черт сним перезагрузился. Но при перезагрузки опять появилась таже самая ошибка которую я описал в первом посте и дальше
BusyBox консоли не грузиться сново.
Пользователь решил продолжить мысль 13 Октября 2010, 07:27:23:
Так после того как выполнил
fsck 2 раз вроде запустилось и загрузилось проработоло 1,5 день и благополучно опять выдает тоже что я описывал в первом посте.
То есть таже самая ошибка.
После очередного выполнения
fsck сегодня:
ubuntu@ubuntu:~$ sudo fsck /dev/sda3
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set) Fix<y>? yes
/dev/sda3 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 135691 has zero dtime. Fix<y>? yes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 135695 was part of the orphaned inode list. FIXED.
Inode 135696 was part of the orphaned inode list. FIXED.
Inode 135698 was part of the orphaned inode list. FIXED.
Inode 135767 was part of the orphaned inode list. FIXED.
Inode 135780 was part of the orphaned inode list. FIXED.
Inode 135808 was part of the orphaned inode list. FIXED.
Inode 136685 was part of the orphaned inode list. FIXED.
Inode 1060127 was part of the orphaned inode list. FIXED.
Inode 1061485 was part of the orphaned inode list. FIXED.
Inode 1061523 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(131104--131105) -(131120--131135) -(133064--133065) -133559 -(133608--133609) -150343 -150349 -150372 -150375 -150377 -(150380--150382) -(150405--150407) -150410 -150468 -154163 -(1541984--1542000) -(1549392--1549407) -2211813 -2212272 -4390996 -4422038 -4430819 -4504734 -4505653 -4505850 -4506048 -4507223 -4507343 -4507524 -4507608 -4507611 -4527744 -(4528139--4528143) -(4528174--4528178) -4557152 -4577145 -4605655 -(4685952--4685954)
Fix<y>? yes
Free blocks count wrong for group #4 (21631, counted=21668).
Fix<y>? yes
Free blocks count wrong for group #47 (4321, counted=4354).
Fix<y>? yes
Free blocks count wrong for group #67 (20370, counted=20372).
Fix<y>? yes
Free blocks count wrong for group #134 (19272, counted=19274).
Fix<y>? yes
Free blocks count wrong for group #135 (20184, counted=20185).
Fix<y>? yes
Free blocks count wrong for group #137 (19447, counted=19456).
Fix<y>? yes
Free blocks count wrong for group #138 (24971, counted=24982).
Fix<y>? yes
Free blocks count wrong for group #139 (6502, counted=6504).
Fix<y>? yes
Free blocks count wrong for group #140 (15765, counted=15766).
Fix<y>? yes
Free blocks count wrong for group #143 (7846, counted=7849).
Fix<y>? yes
Free blocks count wrong (2556991, counted=2557092).
Fix<y>? yes
Inode bitmap differences: -135691 -(135695--135696) -135698 -135767 -135780 -135808 -136685 -1060127 -1061485 -1061523
Fix<y>? yes
Free inodes count wrong for group #16 (2018, counted=2026).
Fix<y>? yes
Free inodes count wrong for group #129 (42, counted=45).
Fix<y>? yes
Free inodes count wrong (923723, counted=923734).
Fix<y>? yes
/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: 299258/1222992 files (0.2% non-contiguous), 2325340/4882432 blocks
Народ какие у кого соображения есть?