You are not logged in.

#1 2011-08-01 18:49:38

uxrs75
Member
Registered: 2010-07-28
Posts: 4

Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

After modifying my time/date setup (setting the hardware clock to UTC, and using a custom timezone file) I started to get a [FAIL] message during boot (after the system had resynched to drive times to the system time), and shutdown.

@ boot time

Mounting local filesystem
        Ext3-fs: barriers not enabled
        kjournal starting. Commit interval 5 seconds
        Ext3-fs (sda4): using internal journal
        Ext3-fs (sda4): mounted filesystem with ordered data mode
                                                                                                                 [FAIL]

@ shutdown

Unmounting Filesystem                    [FAIL]

Nothing seems to be negatively affected, and the boot and shutdown processes continue without even pausing, and sda4 (my /home directory) certainly seems to by mounted (since I'm using it now).

I've run fsck at boot a couple times, but the drives keep coming back clean. I've tried using my old timezone setup, but the fail message persists. I've successfully unmounted and mounted sda4 as Root, trying to generate an error message of some kind, but all I get is a successfully unmounted, or mounted, drive. I've unmounted sda4 priod to shutdown as well, but the message persists.

The only place in the logs the [FAIL] message shows up is in /var/log/boot:

Mounting local filesystem   [BUSY]  [FAIL]

I'm at a loss. I would like to fix this, if only to be sure that it's not a symptom of a larger problem. At the very least, I'd like to know what is causing it.

Last edited by uxrs75 (2011-08-02 06:40:31)

Offline

#2 2011-08-01 19:17:09

Logicien
Member
Registered: 2010-07-31
Posts: 10

Re: Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

If I understand, when you enter in the BIOS setup, you see the hardware clock set to UTC. If so, you must set HARDWARECLOCK="UTC" in /etc/rc.conf. Then using your timezone would give the right system time at boot time. If this is ok, helpfull would be to post the output of the commands of fdisk -l, dumpe2fs -h /dev/sda* for every Ext4 filesystems and /etc/fstab.Some options can be wrong and/or missing. Why not recreate the initrd with the command mkinitcpio -p kernel26 (or kernel30 as a guest, no kernel 3.0 in install yet in my ArchLinux amd64). The problem can origin from there.

Last edited by Logicien (2011-08-01 19:20:38)

Offline

#3 2011-08-01 20:18:00

MoonSwan
Member
From: Great White North
Registered: 2008-01-23
Posts: 881

Re: Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

Search around for the word "quiet" in very recent posts, that may be your issue.

Example, see Karol's reply URL from another thread:

Does it break anything or are you just curious why it suddenly started to appear?
It may be because of the VERBOSE parameter http://mailman.archlinux.org/pipermail/ … 21114.html Do you have 'quiet' on you kernel boot line?

Offline

#4 2011-08-01 20:27:42

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,810

Re: Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

I wouldn't think the removal of VERBOSE should cause the step to report [FAIL]. And if it does, it's clearly a bug if the partitions are being mounted without problems.


But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#5 2011-08-01 23:06:23

uxrs75
Member
Registered: 2010-07-28
Posts: 4

Re: Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

You interpret correctly, Logicien. BIOS is set to UTC; HARDWARECLOCK="UTC". Time and date are a-ok.

I ran mkinitcpio -p kernel26, but the message persists. I also tried using the live cd, and mounting each of the drives in turn. All of them mounted successfully, with no error messages. To verify that it is sda4, I commented the sda4 line out in fstab, and rebooted the machine. I got:

Mounting Local Filesystems    [FAIL]

but none of the Ext3-fs stuff, and the boot process continued successfully. I'm wondering if it's something else.

I'll try adding quiet to the kernel boot line later this evening and see what that brings about.


rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
#   Note: Using "localtime" is discouraged, using "" makes hwclock fall back
#   to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
#   Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="PST"
KEYMAP="uk"
CONSOLEFONT="ter-116n.psf.gz"
#CONSOLEMAP="8859-1"
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MODULES=()

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="no"

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="darkstar"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
#   - broadcast: broadcast address (ignored for DHCP) (optional)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=
broadcast=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
DAEMONS=(hwclock syslog-ng dbus !network !netfs crond alsa mpd)

fstab

# 
# /etc/fstab: static file system information
#
# <file system>  <dir>        <type>  <options>              <dump> <pass>
none             /dev/pts     devpts  defaults                0      0
none             /dev/shm     tmpfs   defaults                0      0
#none /proc/bus/usb usbfs auto,busgid=101,busmode=0775,devgid=101,devmode=0664 0 0

/dev/sr0         /media/sr0   auto    ro,users,noauto,unhide  0      0
/dev/sr1         /media/sr1   auto    ro,users,noauto,unhide  0      0

#/dev/sda1        /boot        ext2    defaults                0      1
#/dev/sda2        swap         swap    defaults                0      0
#/dev/sda3        /            ext3    defaults                0      1
#/dev/sda4        /home        ext3    defaults                0      1

UUID=597bd99a-173b-4b23-947d-b8a50859bcdd       /boot   ext2    defaults        0       1
UUID=a51a3b55-7c5c-45bb-96eb-79cfd1a77f54       swap    swap    defaults        0       0 
UUID=c6ecf0fe-d2c4-4743-b639-1550295b65c6       /       ext3    defaults        0       1 
UUID=ff7030b8-890a-4673-bd1c-f502ca5efb2b       /home   ext3    defaults        0       1 

/dev/sdb1        /media/sdb1  auto    noauto,owner,users      0      0
/dev/sdb1        /media/sdb1  auto    noauto,owner,users      0      0
/dev/sdc1        /media/sdc1  auto    noauto,owner,users      0      0
/dev/sdd1        /media/sdd1  auto    noauto,owner,users      0      0
/dev/sde1        /media/sde1  auto    noauto,owner,users      0      0
/dev/sdf1        /media/sdf1  auto    noauto,owner,users      0      0

fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1      208844      104422   83  Linux
/dev/sda2          208845      738989      265072+  82  Linux swap / Solaris
/dev/sda3          738990   103153364    51207187+  83  Linux
/dev/sda4       103153365   976768064   436807350   83  Linux

dumpe2fs -h /dev/sda1

dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          597bd99a-173b-4b23-947d-b8a50859bcdd
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      ext_attr resize_inode dir_index filetype sparse_super
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         not clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              26208
Block count:              104420
Reserved block count:     5221
Free blocks:              84721
Free inodes:              26177
First block:              1
Block size:               1024
Fragment size:            1024
Reserved GDT blocks:      256
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2016
Inode blocks per group:   252
Filesystem created:       Fri Apr 30 20:35:47 2010
Last mount time:          Thu Aug 19 05:44:48 2010
Last write time:          Mon Aug  1 13:58:14 2011
Mount count:              8
Maximum mount count:      23
Last checked:             Mon Aug  1 07:23:24 2011
Check interval:           15552000 (6 months)
Next check after:         Sat Jan 28 07:23:24 2012
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              128
Default directory hash:   half_md4
Directory Hash Seed:      f5f22ff8-0cb1-4c30-a172-ead082f0ad8a

dumpe2fs -h /dev/sda3

dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          c6ecf0fe-d2c4-4743-b639-1550295b65c6
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              3203072
Block count:              12801796
Reserved block count:     640089
Free blocks:              10487133
Free inodes:              3000642
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      1020
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Fri Apr 30 20:35:51 2010
Last mount time:          Mon Aug  1 13:58:14 2011
Last write time:          Mon Aug  1 07:22:14 2011
Mount count:              8
Maximum mount count:      23
Last checked:             Mon Aug  1 07:22:14 2011
Check interval:           15552000 (6 months)
Next check after:         Sat Jan 28 07:22:14 2012
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
First orphan inode:       262152
Default directory hash:   half_md4
Directory Hash Seed:      08e3f2db-7bb4-41fc-9364-9a9f637951ff
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x0007df4e
Journal start:            1

dumpe2fs -h /dev/sda4

dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          ff7030b8-890a-4673-bd1c-f502ca5efb2b
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              27303936
Block count:              109201837
Reserved block count:     5460091
Free blocks:              80860937
Free inodes:              27074933
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      997
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Fri Apr 30 20:36:07 2010
Last mount time:          Mon Aug  1 13:58:14 2011
Last write time:          Mon Aug  1 13:58:14 2011
Mount count:              8
Maximum mount count:      25
Last checked:             Mon Aug  1 07:23:25 2011
Check interval:           15552000 (6 months)
Next check after:         Sat Jan 28 07:23:25 2012
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      e8dbb219-f7fe-4878-96b6-9137361ce1e2
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x0011b560
Journal start:            1

Last edited by uxrs75 (2011-08-02 06:19:11)

Offline

#6 2011-08-01 23:23:18

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,810

Re: Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

I don't know if this is the cause, but only the root file-system should have '1' in the 6th field of fstab.  All others should have '2' if you want them checked, or '0' if you don't.


But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#7 2011-08-02 00:06:35

thisoldman
Member
From: Pittsburgh
Registered: 2009-04-25
Posts: 1,172

Re: Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

@uxrs75,

I noticed in your rc.conf that you have

TIMEZONE="PST"

Do you have the file '/usr/share/zoneinfo/PST' on your machine?  It doesn't exist on mine.  I do have '/usr/share/zoneinfo/PST8PDT'.

And would you please edit the #5 post in this thread, replacing the word "quote" within the square brackets in the BBCode with the word "code".  It will make the page scroll nicer for others (me) and make the code easier for others (me) to read.

Offline

#8 2011-08-02 01:46:53

Logicien
Member
Registered: 2010-07-31
Posts: 10

Re: Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

Check with the command blkid if the UUID of each partition in fstab correspond with what blkid show. Because your /boot partition is in ext2, fsck can not use a journal to recover and make the filesystem clean. So, this partition must be check by you (e2fsck -y /dev/sda1) after unmount it. If it is unclean at boot tine, like dumpe2fs show, it can generate an error when it is mounted.

Last edited by Logicien (2011-08-02 01:47:31)

Offline

#9 2011-08-02 06:24:38

uxrs75
Member
Registered: 2010-07-28
Posts: 4

Re: Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

thisoldman wrote:

Do you have the file '/usr/share/zoneinfo/PST' on your machine?  It doesn't exist on mine.  I do have '/usr/share/zoneinfo/PST8PDT'.

I do indeed have '/usr/share/zoneinfo/PST' on my machine. It's a custom file I created that doesn't include DST (A part of my ineffective protest against daylight savings time).

thisoldman wrote:

And would you please edit the #5 post in this thread, replacing the word "quote" within the square brackets in the BBCode with the word "code".  It will make the page scroll nicer for others (me) and make the code easier for others (me) to read.

Certainly. It's been a long while since I've used BBcode (though I knew enough html that I should have been able to make the leap... Ah well...)

Offline

#10 2011-08-02 06:37:56

uxrs75
Member
Registered: 2010-07-28
Posts: 4

Re: Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

So, I tried adding 'quiet' to the kernel boot line, but the problem remained. I took a break there, and left the problem to attend a family gathering, and while I was on my way, I recalled Logicien asking for my fstab, and I thought that perhaps one of the other entries in fstab might be causing my problem. When I got back, I commented out everything in fstab except the hard drive partitions, and rebooted the machine. Lo-and-behold, everything was fine. Not a [FAIL] message to be seen. Systematic uncommenting and rebooting revealed the problem to be this line:

none             /dev/pts     devpts  defaults                0      0

It should have read (as per fstab.pacnew)

devpts                 /dev/pts      devpts    defaults            0      0

(The shm entry has also been updated, though its previous format did not generate any error message)

My thanks to you all.
*Tips hat*

Offline

Board footer

Powered by FluxBB