help to understand dmesg results? SOLVED

[bernieszu]

Can anybody explain what these lines in a dmesg result mean and if I need to do anything about them?

9.343320] Driver 'sd' needs updating - please use bus_type methods
[ 9.343334] Driver 'sr' needs updating - please use bus_type methods

[ 11.021400] via-rhine: Broken BIOS detected, avoid_D3 enabled.
[ 11.022294] eth0: VIA Rhine II at 0xfdffe000, 00:16:17:6d:05:11, IRQ 23.
[ 11.023015] eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1.

[ 21.175105] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
[ 21.175489] EXT3 FS on sda1, internal journal

Also, if anybody could point me to a link that explains HOW to use bus_type methods and how to safely use e2fsck, I would be really grateful. I have tried many times to use e2fsck but obviously I'm doing something wrong. Do you need to specify the specific area to check? How do you do that?
Here are 2 embarrassing examples of my attempts to use it.

:~$ e2fsck
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list


:~$ e2fsck -p
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list

:~$ sudo e2fsck -v
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list


Thank you

[kubicle]

Re: help to understand dmesg results?

[ 9.343320] Driver 'sd' needs updating - please use bus_type methods
[ 9.343334] Driver 'sr' needs updating - please use bus_type methods

These should be harmless and can be ignored (and let the kernel folks deal with it), the underlying problem is that the drivers use both driver and bus methods which generates this error (it shouldn't affect performance or operation)

[ 11.021400] via-rhine: Broken BIOS detected, avoid_D3 enabled.

Some BIOSES can't handle rhine chips going into D3 (power-saving) mode, this message tells such a Motherboard/BIOS has been detected and D3 mode protection has been disabled (the calls to go to D3 mode are dropped)

[ 11.022294] eth0: VIA Rhine II at 0xfdffe000, 00:16:17:6d:05:11, IRQ 23.
[ 11.023015] eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1.

Normal messages activating your ethernet (networking) chip

[ 21.175105] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
[ 21.175489] EXT3 FS on sda1, internal journal

Fixed (ext2/3/4) drives are normally checked during boot every 30 mounts (default), you usually see these messages with removable or pen drives which aren't connected/checked at boot...or with filesystems that have filesystem checks disabled in /etc/fstab.

Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

As the usage message tells you, you need to specify a 'device' (like /dev/sdXX) for e2fsck, the options in square brackets are optional, only 'device' is mandatory

Warning: do not run filesystem checks on mounted filesystems, you can use a liveCD, if this your root filesystem (which cannot be unmounted). If it's a fixed drive/filesystem, you can also use 'sudo touch /forcefsck' to force a filesystem check on next boot.

[Qqmike]

Re: help to understand dmesg results?

bernieszu, for examples, look over the table of contents here, and pick and choose:
http://members.iinet.net.au/%7Eherman546/p10.html

[bernieszu]

Re: help to understand dmesg results? SOLVED


Thank you both very much.

That is very reassuring and very helpful.
I have bookmarked the recommended site - very informative.