Announcement

**Rog131** · Sep 17, 2009, 12:12 PM

Re: Filesystem not clean

Welcome

Not clue, but have you tried to run the fsck by the hand ? That is, after the shutdown do the next start by using the live CD. Run the fsck to the /dev/sda3. Maybe with the -V option ?

man fsck

-V Produce verbose output, including all file system-specific commands that are executed.

Maybe there is more information.

**dibl** · Sep 17, 2009, 12:27 PM

Re: Filesystem not clean

Or, you could boot a Parted Magic Live CD: http://partedmagic.com/

or GParted Live CD, and just right-click each partition and choose "check" for each one. Then click "Apply" and they will be checked and fixed as needed.

But, as you say, if it happens again on the next boot, there may be something wrong with the shutdown routine, when it is supposed to unmount the filesystems.

BTW, reiserfs is a mostly-unmaintained format, for some time now -- not sure that is a good bet for the future.

**armandrix** · Sep 17, 2009, 04:21 PM

Re: Filesystem not clean

Hi Rog131

Tx for your reply.

Yes, I already checked some times filesystems, but always clean after bootup. Boot process execs fsck in sda3 and sda4 and their appears ok after system is up. If I do it again fsck finds no errors.

**armandrix** · Sep 17, 2009, 04:27 PM

Re: Filesystem not clean

Hi dibl ...

But, as you say, if it happens again on the next boot, there may be something wrong with the shutdown routine, when it is supposed to unmount the filesystems.

I don't think there is some problems with fsck, but as you said something in unmount routines, wich i don't know where it resides in system.

Any system running here will correct both filesystems all right. but after shutdown or reboot kubuntu, same messages indicating at least wrong unmounting (can't see nothing about busy or so).

Thank you

**dibl** · Sep 17, 2009, 04:36 PM

Re: Filesystem not clean

How did you install Kubuntu? Did you wipe (reformat) the partition, or did you leave slackware on it and install over it? I have never seen *buntu fail to shut down correctly, but I know that funny things can happen if you try to install "over" another OS -- it doesn't replace everything. There might be a slackware script messing you up.

**armandrix** · Sep 18, 2009, 02:39 PM

Hi dibl

So Funny

Actually i'm unmounting manually sda3 & 4 to avoid data corruption or worst... Not a big deal but annoys

I always install systems formatting and checking partitions, old behavior. Kubuntu and slack recently wasn't other way (thought it about different partitions: kubuntu sda2, slack sda3), sda4 reiserfs never had a system installed into, it's just to keep data.

Also kubuntu is my main system here and so, mbr belongs to it. slack was installed with lilo in sda3 root .

Do you know how to setup a full verbose log from shutdown process to try find this out? notice that no problems occurs if umount it before shutdown, maybe it can confirm something wrong with scripts. if so, what-a-hell is happenning here

-- instigating --

**dibl** · Sep 18, 2009, 03:06 PM

Re: Hi dibl

Originally posted by armandrix

Do you know how to setup a full verbose log from shutdown process to try find this out?

No I don't -- sorry. I've never seen such a problem.

Can you post your /etc/fstab file? Maybe we'll be able to learn something there.

**armandrix** · Sep 18, 2009, 10:53 PM

Surely pal

here is:

# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda2 during installation
UUID=aa385095-9d0a-4244-a642-e924aab10b54 / ext4 relatime,errors=remount-ro 0 1
# /media/arquivo was on /dev/sda4 during installation
UUID=4eb137cf-9830-4c6a-be10-ad32d400ff1c /media/arquivo reiserfs relatime 0 2
# /media/sda3 was on /dev/sda3 during installation
UUID=a601fbb0-2039-454c-8038-1fb205ee8a67 /media/sda3 ext4 relatime 0 2
# swap was on /dev/sda1 during installation
UUID=d088ddc2-40dd-49ce-a574-c0272b106a47 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

for the quest i've already tried /dev/sda3( or 4 ) /media/respective folder without success

What i'm really thinking now it's why or where is that usual /etc/inittab

? (k)ubuntu changes places things that i think made only for disturbing.. why that

what advantage

Really i left RWIN behind since win98 when they think tooked control of my own machine.. that machine (the mine) is mine, i'd buy it and i think can make with it what i want and not anyone..

That kind of obscured confs (as gnome do) think is respectless.. did you read "man boot"?? it is talking about slackware or *bsds boot not debian-like.. and tell us it's well documented!!!!! shame!!!!

can saw here U R senior member.. but even a senior member cannot known a simple boot process from system.. it's not personal please.. i'm very very pleased cause U could expose yourself in a such weird thing and are trying your best to solve it.. really appreciate you dedication.

But now i'm thinking what else is behind

?

Do you have doubts?? wanna logs posts?? dunnow..

There is something wrong i know, but why a experienced user can't know where?? (talking about me ok??)

QUESTION FOR ALL *UBUNTU PEOPLE: WHERE IS THE SHUTDOWN LOGS AND WHERE I CAN SET IT UP

?

If i never get back was blocked ok??

thnk you very much dibl

cheers

p.s.: only for consciencious:

Ar:~$ vol_id
no device
Ar:~$ vol_id /dev/sda3
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext4
ID_FS_VERSION=1.0
ID_FS_UUID=a601fbb0-2039-454c-8038-1fb205ee8a67
ID_FS_UUID_ENC=a601fbb0-2039-454c-8038-1fb205ee8a67
ID_FS_LABEL=hda3
ID_FS_LABEL_ENC=hda3
Ar:~$ vol_id /dev/sda4
ID_FS_USAGE=filesystem
ID_FS_TYPE=reiserfs
ID_FS_VERSION=3.6
ID_FS_UUID=4eb137cf-9830-4c6a-be10-ad32d400ff1c
ID_FS_UUID_ENC=4eb137cf-9830-4c6a-be10-ad32d400ff1c
ID_FS_LABEL=
ID_FS_LABEL_ENC=
Ar:~$ vol_id /dev/sda2
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext4
ID_FS_VERSION=1.0
ID_FS_UUID=aa385095-9d0a-4244-a642-e924aab10b54
ID_FS_UUID_ENC=aa385095-9d0a-4244-a642-e924aab10b54
ID_FS_LABEL=
ID_FS_LABEL_ENC=

**ntzim** · Sep 19, 2009, 01:41 AM

Re: Filesystem not clean

I am inexperienced so maybe this is a bad idea ...

but why don't you rename the rc and init directories, make a reconfigure of your system so that the directories are made new again, check if problem solved and if yes compare the original directories with the new ones to see what changed?

**dibl** · Sep 19, 2009, 06:47 AM

Re: Surely pal

Originally posted by armandrix

can saw here U R senior member.. but even a senior member cannot known a simple boot process from system.. it's not personal please.. i'm very very pleased cause U could expose yourself in a such weird thing and are trying your best to solve it.. really appreciate you dedication.

"expose myself"?

You mean, like expose my ignorance?

Please understand, ignorance is the predecessor condition to knowledge -- only ignorant people can learn something. People who already know it all are unable to learn anything new.

QUESTION FOR ALL *UBUNTU PEOPLE: WHERE IS THE SHUTDOWN LOGS AND WHERE I CAN SET IT UP

?

I searched in Ubuntu forum and found this tip:

http://ubuntuforums.org/showthread.php?t=136368

So, open the /etc/default/bootlogd with kate, and change it to "Yes", and reboot and let's see if there is more information.

p.s.: only for consciencious:

Ar:~$ vol_id
no device
Ar:~$ vol_id /dev/sda3
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext4
ID_FS_VERSION=1.0
ID_FS_UUID=a601fbb0-2039-454c-8038-1fb205ee8a67
ID_FS_UUID_ENC=a601fbb0-2039-454c-8038-1fb205ee8a67
ID_FS_LABEL=hda3
ID_FS_LABEL_ENC=hda3
Ar:~$ vol_id /dev/sda4
ID_FS_USAGE=filesystem
ID_FS_TYPE=reiserfs
ID_FS_VERSION=3.6
ID_FS_UUID=4eb137cf-9830-4c6a-be10-ad32d400ff1c
ID_FS_UUID_ENC=4eb137cf-9830-4c6a-be10-ad32d400ff1c
ID_FS_LABEL=
ID_FS_LABEL_ENC=
Ar:~$ vol_id /dev/sda2
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext4
ID_FS_VERSION=1.0
ID_FS_UUID=aa385095-9d0a-4244-a642-e924aab10b54
ID_FS_UUID_ENC=aa385095-9d0a-4244-a642-e924aab10b54
ID_FS_LABEL=
ID_FS_LABEL_ENC=

Code:

dibl@karmic:~$ man vol_id
No manual entry for vol_id
dibl@karmic:~$ sudo apt-get install vol_id
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package vol_id

Where is that "vol_id" command located? I'm running 9.10, and there is no such command, and no such package in the repository?

Please post the output of

Code:

lsb_release -a

and

Code:

uname -a

**vinnywright** · Sep 19, 2009, 08:44 AM

Re: Filesystem not clean

at hear

NAME
vol_id - probe filesystem type and read label and uuid

DESCRIPTION
vol_id is usually called from a udev rule, to provide udev with the filesystem type, the
label and the uuid of a volume. It supports most of the common filesystem formats and
detects various raid setups to prevent the recognition of raid members as a volume with a
filesystem.

and I had to use sudo to work it

Code:

vinny@desktop:~$ vol_id /dev/sda5
/dev/sda5: error opening volume
vinny@desktop:~$ sudo vol_id /dev/sda3
[sudo] password for vinny:
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=0ee90e7d-8196-414d-b049-a5b32b7d8b77
ID_FS_UUID_ENC=0ee90e7d-8196-414d-b049-a5b32b7d8b77
ID_FS_LABEL=
ID_FS_LABEL_ENC=

hear

Code:

vinny@desktop:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:  Ubuntu 9.04
Release:    9.04
Codename:    jaunty

but of corse it's Kubuntu

perhaps it dident make it to 9.10

of corse none of this helps the OP ...........

VINNY

**dibl** · Sep 19, 2009, 09:17 AM

Re: Filesystem not clean

Aha -- thanks vinny!

Yeah, maybe 9.10 doesn't need it.

These 2 lines in that output bother me:

ID_FS_LABEL=hda3
ID_FS_LABEL_ENC=hda3

But I don't know whether the fact that they should be "sd" not "hd" is related to the fsck problem or not. Notice that the same lines for the other partitions are blank.

**Rog131** · Sep 19, 2009, 09:25 AM

Re: Filesystem not clean

Bootlog

> Bug #98955: logd not running

/sbin/logd is not started since Gutsy, leading to an empty /var/log/boot file

this is a setting in /etc/default/bootlogd, and the reason this has been disabled is that it caused several other processes to crash unexpectedly

There are "workarounds" (they may or may not work).
++ lot of...

Shutdown log ?

> Bug #69771: shutdown console messages are lost

> Bug #328881: init: support logging of job output

...
kapetr wrote on 2009-08-10:

Yes, Yes and again YES

many people are discussing on many places about this logging problem.
I also WILL to have /var/log/boot .. shutdown !!!

Can we make some kind of pressure ?
How ?
Where?

Scott James Remnant wrote on 2009-08-10:

No.
You could do the work yourself and contribute the necessary support in
the form of patches.
...
Scott James Remnant wrote on 2009-08-24:

Fixing boot logging is on my TODO list, but it's about item 246 right
now and probably in the karmic+2 timeframe.
...

++ lot of...

Linux logs

> Ubuntu community - Linux Log Files

Some of the boot messages could be found from the other log files.

It is possible to turn the splash off and record (with the help of a video camera, example from a bug report /1/ ) the boot&shutdown messages.

/1/ Bug #430654:

...I attached a picture of the errors.
http://launchpadlibrarian.net/31897148/udeverror.jpg

**dibl** · Sep 19, 2009, 09:34 AM

Re: Filesystem not clean

Ahhhhhh -- Rog, you are the master!

Thanks!

Announcement

Filesystem not clean

Filesystem not clean

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment