Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 20 Oct 2014, 21:00
All times are UTC - 4
 Forum index » House Training » Users ( For the regulars )
Making filesystem usable - FAILED
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [15 Posts]  
Author Message
Chili Dog


Joined: 20 Dec 2011
Posts: 117

PostPosted: Fri 15 Feb 2013, 06:09    Post subject:  Making filesystem usable - FAILED
Subject description: Error I get after Puppy hard drive install in ext4 partition
 

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
Back to top
View user's profile Send private message 
Flash
Official Dog Handler


Joined: 04 May 2005
Posts: 11117
Location: Arizona USA

PostPosted: Fri 15 Feb 2013, 08:56    Post subject:  

But Puppy still boots to a desktop and works ok as far as you can tell?
Back to top
View user's profile Send private message 
Chili Dog


Joined: 20 Dec 2011
Posts: 117

PostPosted: Fri 15 Feb 2013, 09:20    Post subject:  

Ya, works great!

I just wonder what causes that error message.
Back to top
View user's profile Send private message 
Semme

Joined: 07 Aug 2011
Posts: 3965
Location: World_Hub

PostPosted: Fri 15 Feb 2013, 09:48    Post subject:  

This an ext2 install?
Back to top
View user's profile Send private message 
Chili Dog


Joined: 20 Dec 2011
Posts: 117

PostPosted: Fri 15 Feb 2013, 10:41    Post subject:  

You know, I'm not even sure!
Back to top
View user's profile Send private message 
Semme

Joined: 07 Aug 2011
Posts: 3965
Location: World_Hub

PostPosted: Fri 15 Feb 2013, 11:06    Post subject:  

From a shell: mount reports your partition as what?
Back to top
View user's profile Send private message 
Chili Dog


Joined: 20 Dec 2011
Posts: 117

PostPosted: Fri 15 Feb 2013, 11:12    Post subject:  

Sorry, it's ext4. I couldn't remember what it was. Embarassed
Back to top
View user's profile Send private message 
Semme

Joined: 07 Aug 2011
Posts: 3965
Location: World_Hub

PostPosted: Fri 15 Feb 2013, 11:20    Post subject:  

Ooo.. wasn't expect'in that. I'll get back to ya as I'm not sure what this message might mean aboard Pup..
Back to top
View user's profile Send private message 
Semme

Joined: 07 Aug 2011
Posts: 3965
Location: World_Hub

PostPosted: Fri 15 Feb 2013, 11:46    Post subject:  

From a *LIVE* boot (puppy pfix=ram), run: e2fsck -f -n -v /dev/* << * the install partition.

Since I'm not techie enough to know a lot about bad blocks, maybe we return an exit code?
Back to top
View user's profile Send private message 
Chili Dog


Joined: 20 Dec 2011
Posts: 117

PostPosted: Sun 17 Feb 2013, 12:23    Post subject:  

Code:
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
Back to top
View user's profile Send private message 
Semme

Joined: 07 Aug 2011
Posts: 3965
Location: World_Hub

PostPosted: Sun 17 Feb 2013, 13:37    Post subject:  

Now take the read off and write it. Make sure it's from a *live* boot.
Code:
e2fsck -f -p -v /dev/sda2

Hey Chili- run: depmod -a and reboot prior to the above..

If depmod doesn't clear it, then go with e2fsck.
Back to top
View user's profile Send private message 
Chili Dog


Joined: 20 Dec 2011
Posts: 117

PostPosted: Sun 17 Feb 2013, 16:34    Post subject:  

Code:
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


Rebooted into the installation after the above, then ran "depmod -a" (sry didn't see your edit till just now), and rebooted again. Still says FAILED.
Back to top
View user's profile Send private message 
Semme

Joined: 07 Aug 2011
Posts: 3965
Location: World_Hub

PostPosted: Sun 17 Feb 2013, 21:52    Post subject:  

Could be a bug.. After a fresh boot, gzip'n upload a dump:
Code:
dmesg > dmesg.txt
gzip dmesg.txt

This'll be in /root.
Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 858

PostPosted: Sat 27 Apr 2013, 10:17    Post subject:  

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).
Back to top
View user's profile Send private message 
Karl Godt


Joined: 20 Jun 2010
Posts: 3972
Location: Kiel,Germany

PostPosted: Mon 29 Apr 2013, 12:09    Post subject:  

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 .
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 1 [15 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Users ( For the regulars )
Jump to:  

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
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0760s ][ Queries: 12 (0.0082s) ][ GZIP on ]