[solved] After update,build new image, error: modprobe: invalid option

killnine · 2011-12-14 18:50:06

I am ultimately getting "Unable to find major/minor number of root..." after an Syu BUT
After researching and trying many solutions I've come to this:

With a new mirrorlist, a Syy, and then an Syu OR pacman -U [old.working.kernel] the image build keeps resulting in this:

==>Building image from preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==>Starting build: 3.1.5-1-ARCH
  -> Parsing hook: base
  -> Parsing hook: udev
  -> Parsing hook: autodetect
modprobe: invalid option --'d'
BusyBox v1.17.2 (2010-09-28 19:00:30 UTC) multi-call binary

Usage: modprobe [-qfwrsv] MODULE [symbol=value]...

Options:....
  -> Parsing pata
.....

So I think I need to upgrade BusyBox or mkinitcpio, does anyone agree?

BUT

pacman -S mkinitcpio mkinitcpio-busybox busybox

Shows all are up to date

Can I have some help in getting this fixed? What is going on?

edit- should i delete my previous post on the same-ish topic?

Last edited by killnine (2011-12-21 14:01:06)

falconindy · 2011-12-17 16:20:25

At some point you fubared something (maybe ran busybox --install?) and busybox is being called for modprobe. This binary doesn't belong to any of those things -- its module-init-tools. Look at the full path that's actually being called for depmod (type -P depmod). It should be /sbin/depmod, and it shouldn't be a symlink. If it's anything but a file in /sbin, delete it. Otherwise, reinstall module-init-tools.

killnine · 2011-12-17 18:11:13

[root@clc ~]# ls -l /sbin/depmod 
-rwxr-xr-x 1 root root 154328 Dec  3 23:51 /sbin/depmod

falconindy · 2011-12-17 20:17:23

That doesn't guarantee that there isn't a binary called depmod higher in your PATH.... run the command I gave you: type -P depmod.

killnine · 2011-12-19 14:16:27

My apologies. How is this

[root@clc ~]# type -P depmod
/sbin/depmod

falconindy · 2011-12-19 18:11:01

I'm an idiot. I'm asking for depmod and mkinitcpio is choking on modprobe... repeat for modprobe, please.

killnine · 2011-12-20 02:03:02

[root@clc ~]# type -P mkinitcpio
/usr/bin/mkinitcpio

falconindy · 2011-12-20 02:54:18

modprobe is not mkinitcpio.

killnine · 2011-12-20 17:52:47

Now I am the idiot..

[root@clc iscsi-conf-parse]# type -P modprobe
/bin/modprobe

..slowly, but surely getting there. Thank you for you help!

wonder · 2011-12-20 18:09:00

killnine wrote:

Now I am the idiot..
[root@clc iscsi-conf-parse]# type -P modprobe
/bin/modprobe
..slowly, but surely getting there. Thank you for you help!

that's the problem.

modprobe is in /sbin

pacman -Qo /bin/modprobe

tomegun · 2011-12-20 18:14:08

wonder wrote:

killnine wrote:
Now I am the idiot..
[root@clc iscsi-conf-parse]# type -P modprobe
/bin/modprobe
..slowly, but surely getting there. Thank you for you help!
that's the problem.
modprobe is in /sbin
pacman -Qo /bin/modprobe

What probably happened (as falconindy suggested) is that the user ran busybox --install by accident. Deleting this (and any other stray file) should fix your problem.

This problem would not be so hard to debug once we symlink /bin, /sbin and /usr/sbin to /usr/bin (then reinstalling module-init-tools would have fixed the problem). One of these days...

killnine · 2011-12-20 20:20:12

tomegun wrote:

wonder wrote:
that's the problem.
modprobe is in /sbin
pacman -Qo /bin/modprobe
What probably happened (as falconindy suggested) is that the user ran busybox --install by accident. Deleting this (and any other stray file) should fix your problem.
This problem would not be so hard to debug once we symlink /bin, /sbin and /usr/sbin to /usr/bin (then reinstalling module-init-tools would have fixed the problem). One of these days...

"Deleting this" ... busybox or ?

I ran

pacman -S module-init-tools

and retried

mkinitcpio -p linux

and still got the modprobe usage...

also..

[root@clc iscsi-conf-parse]# pacman -Qo /bin/modprobe
error: No package owns /bin/modprobe

Sorry I am not more help...

killnine · 2011-12-20 20:26:03

[root@clc iscsi-conf-parse]# ls -l /bin/modprobe 
lrwxrwxrwx 1 root root 7 Nov 23 12:28 /bin/modprobe -> busybox
[root@clc iscsi-conf-parse]# rm /bin/modprobe 
[root@clc iscsi-conf-parse]# type -P modprobe
/sbin/modprobe
[root@clc iscsi-conf-parse]# mkinitcpio -p linux
==> Building image from preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.1.5-1-ARCH
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [autodetect]
  -> Parsing hook: [pata]
  -> Parsing hook: [scsi]
  -> Parsing hook: [sata]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [usbinput]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.1.5-1-ARCH
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [pata]
  -> Parsing hook: [scsi]
  -> Parsing hook: [sata]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [usbinput]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

SCORE! .. will repost success or failure after a reboot.

thanks again!

tomegun · 2011-12-20 20:43:31

killnine wrote:

tomegun wrote:
What probably happened (as falconindy suggested) is that the user ran busybox --install by accident. Deleting this (and any other stray file) should fix your problem.
"Deleting this" ... busybox or ?

Deleting /bin/modprobe (and any other symlinks to busybox), as you already figured out

killnine wrote:

I ran

pacman -S module-init-tools

and retried

mkinitcpio -p linux

and still got the modprobe usage...

also..

[root@clc iscsi-conf-parse]# pacman -Qo /bin/modprobe
error: No package owns /bin/modprobe

Exatly, reinstalling the package does not work because the symlink is in /bin whereas your package installs the binary in /sbin...

Glad to see it worked out in the end.

killnine · 2011-12-21 13:59:34

Reboot was successful, I can now boot my normal arch.

Thank you again for all the help

Arch Linux

#1 2011-12-14 18:50:06

[solved] After update,build new image, error: modprobe: invalid option

#2 2011-12-17 16:20:25

Re: [solved] After update,build new image, error: modprobe: invalid option

#3 2011-12-17 18:11:13

Re: [solved] After update,build new image, error: modprobe: invalid option

#4 2011-12-17 20:17:23

Re: [solved] After update,build new image, error: modprobe: invalid option

#5 2011-12-19 14:16:27

Re: [solved] After update,build new image, error: modprobe: invalid option

#6 2011-12-19 18:11:01

Re: [solved] After update,build new image, error: modprobe: invalid option

#7 2011-12-20 02:03:02

Re: [solved] After update,build new image, error: modprobe: invalid option

#8 2011-12-20 02:54:18

Re: [solved] After update,build new image, error: modprobe: invalid option

#9 2011-12-20 17:52:47

Re: [solved] After update,build new image, error: modprobe: invalid option

#10 2011-12-20 18:09:00

Re: [solved] After update,build new image, error: modprobe: invalid option

#11 2011-12-20 18:14:08

Re: [solved] After update,build new image, error: modprobe: invalid option

#12 2011-12-20 20:20:12

Re: [solved] After update,build new image, error: modprobe: invalid option

#13 2011-12-20 20:26:03

Re: [solved] After update,build new image, error: modprobe: invalid option

#14 2011-12-20 20:43:31

Re: [solved] After update,build new image, error: modprobe: invalid option

#15 2011-12-21 13:59:34

Re: [solved] After update,build new image, error: modprobe: invalid option

Board footer