I have installed slackware 10.0, and after first 'hard' reset after my
system hanged up i keep reciving error messages when my system starts:

kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
(...)
FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0

Could anyone help me with this problem, or advise some links to such problem
solving description ?
I would be very grateful


Btw I use reiserfs, and my fstab is probably not a cause and looks like :
/dev/hdc2 swap swap defaults 0 0
/dev/hdc1 / reiserfs defaults 1 1
/dev/hda1 /mnt/windows vfat defaults 1 0
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0

Greetings,

wezior wrote:

> I have installed slackware 10.0, and after first 'hard' reset after my
> system hanged up i keep reciving error messages when my system starts:
>
> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
> (...)
> FAT: bogus logical sector size 0
> UMSDOS: msdos_read_super failed, mount aborted.
> FAT: bogus logical sector size 0
> FAT: bogus logical sector size 0
>
> Could anyone help me with this problem, or advise some links to such
> problem solving description ?

These are not uncommon error messages, and don't in themselves reflect
something critically wrong with your system. However, if your system is
hanging at boot after these messages appear, then there is certainly *some*
problem.

I suggest checking that your partition types are correct -- that is, Linux
Native (83) for your reiser filesystem(s), Linux Swap (82) for your swap
partition, and whatever it's called for your windows partition (Win95?).

Also, check your /etc/lilo.conf -- it sounds like you have LILO on hda and
your root partition on hdc. You might need to add something to your lilo
configuration like "table = other", I'm not sure how that would work
exactly. Alternately, you could set your BIOS to boot from hdc first, and
put LILO on that drive instead by altering the "boot = /dev/hda" line to
say "boot = /dev/hdc".

Don't forget to run /sbin/lilo after making any changes to /etc/lilo.conf.

Good luck,
Jeffrey

"wezior" <wezior@tlen.pl> wrote in message
news:chn3dq$qh6$1@nemesis.news.tpi.pl...
> I have installed slackware 10.0, and after first 'hard' reset after my
> system hanged up i keep reciving error messages when my system starts:
>
> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
> (...)
> FAT: bogus logical sector size 0
> UMSDOS: msdos_read_super failed, mount aborted.
> FAT: bogus logical sector size 0
> FAT: bogus logical sector size 0
>
> Could anyone help me with this problem, or advise some links to such
problem
> solving description ?
> I would be very grateful
>
>
> Btw I use reiserfs, and my fstab is probably not a cause and looks like :
> /dev/hdc2 swap swap defaults 0 0
> /dev/hdc1 / reiserfs defaults 1 1
> /dev/hda1 /mnt/windows vfat defaults 1 0
> /dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
> /dev/fd0 /mnt/floppy auto noauto,owner 0 0
> devpts /dev/pts devpts gid=5,mode=620 0 0
> proc /proc proc defaults 0 0
>
> Greetings,
>
>
If you are running the stock kernel that comes with Slack, it will try to
load a lot of modules that may not apply to your system. It looks like it
is searching for a SCSI adapter that it is not finding, then trying to
install the UMSDOS module which fails because you don't have a UMSDOS
partition.

No problem, just takes more boot time.

--Larry

On Wednesday 08 September 2004 03:06 pm, Larry Sonderling did deign to grace
us with the following:
> "wezior" <wezior@tlen.pl> wrote in message
>> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
>> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
>> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
>> (...)
>> FAT: bogus logical sector size 0
>> UMSDOS: msdos_read_super failed, mount aborted.
>> FAT: bogus logical sector size 0
>> FAT: bogus logical sector size 0
>>
> If you are running the stock kernel that comes with Slack, it will try to
> load a lot of modules that may not apply to your system. It looks like it
> is searching for a SCSI adapter that it is not finding, then trying to
> install the UMSDOS module which fails because you don't have a UMSDOS
> partition.
>
> No problem, just takes more boot time.
>
Yabbut, there's a way to make it not do that, isn't there? I hope
I don't have to go through my init files again just to track it
down. Any handy references? Probably booting-HOWTO or something,
I suppose. Well, off to the reading.

Thanks,
Rich

On Thu, 09 Sep 2004 09:29:30 +0000, Rich Grise wrote:
> On Wednesday 08 September 2004 03:06 pm, Larry Sonderling did deign to
> grace us with the following:
>> "wezior" <wezior@tlen.pl> wrote in message
>>> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
>>> (...)
>>> FAT: bogus logical sector size 0
>>> UMSDOS: msdos_read_super failed, mount aborted. FAT: bogus logical
>>> sector size 0
>>> FAT: bogus logical sector size 0
>>>
>> If you are running the stock kernel that comes with Slack, it will try
>> to load a lot of modules that may not apply to your system. It looks
>> like it is searching for a SCSI adapter that it is not finding, then
>> trying to install the UMSDOS module which fails because you don't have a
>> UMSDOS partition.
>>
>> No problem, just takes more boot time.

Actually this is not true, and the messages are information, and not,
strictly speaking, errors. If you fix the system such that these don't
recur you'll manage to save all of a nanosecond or two at boot time.
(IOW it takes much more time to "fix" this than to put up with it.)

> Yabbut, there's a way to make it not do that, isn't there? I hope I don't

In modules.conf days it was this:
alias scsi_hostadapter off
for the SCSI "error". Similarly it could be aliased to your real SCSI
host adapter if you have one, and it will load automagically without
hotplug.

The UMSDOS thing probably means you had a type "auto" in fstab. Ah,
looking back at the OP I see this was so. mount(8) will try all the
filesystems in /proc/filesystems, in order.

> have to go through my init files again just to track it down. Any handy
> references? Probably booting-HOWTO or something, I suppose. Well, off to

Read about modprobe(8), modprobe.conf(5) and mount(8).
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

Le Thu, 09 Sep 2004 23:46:32 -0500, /dev/rob0 <rob0@gmx.co.uk> a écrit:
> In modules.conf days it was this:
> alias scsi_hostadapter off
> for the SCSI "error". Similarly it could be aliased to your real SCSI
> host adapter if you have one, and it will load automagically without
> hotplug.

Why are you saying "In modules.conf days" ? Is that config-file
obsolete ? I'm copying mine since a long time from one distro to the
next, and it seems always working and necessary.
--
^^ Gauthier
(_____/°°-ç
| \_`-"
)/@mmm||
\nn \nn FOE-Belgium : http://www.amisdelaterre.be

On Fri, 10 Sep 2004 18:30:50 +0000, Gauthier wrote:
> Why are you saying "In modules.conf days" ? Is that config-file
> obsolete ? I'm copying mine since a long time from one distro to the
> next, and it seems always working and necessary.

I think the proper term would be "deprecated", in favour of
modprobe.conf, which is what the new modutils prefers. The term
"obsolete" would apply to "conf.modules", the use of which is no longer
supported.

The change was transparent to most users, but we're no longer using the
same old insmod and modprobe. I think in Slackware this happened with
9.1.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply