Making filesystem usable - FAILED
Making filesystem usable - FAILED
I have Slacko 5.3 installed on my pc, and when it boots it always gives me that error.
Anyone know what causes that?
Thanks
Anyone know what causes that?
Thanks
Code: Select all
sh-4.1# e2fsck -f -n -v /dev/sda2
e2fsck 1.41.14 (22-Dec-2010)
Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set) Fix? no
Superblock last write time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set). Fix? no
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
74696 inodes used (2.85%)
633 non-contiguous files (0.8%)
25 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 70847/11
1374498 blocks used (13.15%)
0 bad blocks
1 large file
64748 regular files
6111 directories
156 character device files
169 block device files
0 fifos
0 links
3501 symbolic links (3501 fast symbolic links)
2 sockets
--------
74687 files
Now take the read off and write it. Make sure it's from a *live* boot.
Hey Chili- run: depmod -a and reboot prior to the above..
If depmod doesn't clear it, then go with e2fsck.
Code: Select all
e2fsck -f -p -v /dev/sda2
If depmod doesn't clear it, then go with e2fsck.
Code: Select all
sh-4.1# e2fsck -f -p -v /dev/sda2
/dev/sda2: Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set) FIXED.
/dev/sda2: Superblock last write time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set). FIXED.
74696 inodes used (2.85%)
633 non-contiguous files (0.8%)
25 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 70847/11
1374498 blocks used (13.15%)
0 bad blocks
1 large file
64748 regular files
6111 directories
156 character device files
169 block device files
0 fifos
0 links
3501 symbolic links (3501 fast symbolic links)
2 sockets
--------
74687 files
Could be a bug.. After a fresh boot, gzip'n upload a dump:
This'll be in /root.
Code: Select all
dmesg > dmesg.txt
gzip dmesg.txt
The "Making the filesystem usable..." section of /etc/r.d./rc.sysinit mounts a number of pseudo-filesystems:
/proc
/dev/pts
/sys
/dev/shm
If there is a problem mounting one of these, you will see the red "failed" report.
You may find a detailed error message at the beginning of the /tmp/bootsysinit.log file, before the "VERSION UPDATE" line.
Note that because /proc is mounted before output is redirected to that log file, if there was a problem mounting /proc, you would probably see that detailed error message on the console if you have a full installation. For a frugal installation or a live CD, that message might appear on the console, or it might be lost since init in initrd previously redirected output to its own log file which no longer exists (although its contents were copied to /initrd/tmp/bootinit.log).
/proc
/dev/pts
/sys
/dev/shm
If there is a problem mounting one of these, you will see the red "failed" report.
You may find a detailed error message at the beginning of the /tmp/bootsysinit.log file, before the "VERSION UPDATE" line.
Note that because /proc is mounted before output is redirected to that log file, if there was a problem mounting /proc, you would probably see that detailed error message on the console if you have a full installation. For a frugal installation or a live CD, that message might appear on the console, or it might be lost since init in initrd previously redirected output to its own log file which no longer exists (although its contents were copied to /initrd/tmp/bootinit.log).
npierce is absolutely right with his statements .
What I can imagine is that you boot with the rw kernel parameter .
In that case mount -o remount,rw / in the if PUPMODE = 2 or if ! -d /initrd test part might fail .
I have also read that newest kernels 3.8.X might not support some pseudo filesystems anymore ie /proc/bus/usb .
What I can imagine is that you boot with the rw kernel parameter .
In that case mount -o remount,rw / in the if PUPMODE = 2 or if ! -d /initrd test part might fail .
I have also read that newest kernels 3.8.X might not support some pseudo filesystems anymore ie /proc/bus/usb .