LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-14-2014, 06:08 AM   #1
paolo27957
LQ Newbie
 
Registered: Aug 2010
Location: Roma, Italy
Distribution: slackware
Posts: 12

Rep: Reputation: 2
mkinitrd oddities


On a server where i was updating slackware i had the need to use mkinitrd, because on this machine there was an hardware SCSI
controller (mtpspi kernel module) and an ext4 root partition, as usual i typed:
Code:
mkinitrd -c -k 3.10.30-smp -m mtpspi:ext4 -f ext4 -r /dev/sdb2 -l it -u
but after checking initrd-tree directory i found mtpspi* modules were missing.
Instead these were included if i typed:
Code:
mkinitrd -c -k 3.10.30-smp -m ext4:mtpspi -f ext4 -r /dev/sdb2 -l it -u
Perhaps modules searching (and dependencies) are affected by the alphabetical names.
This could be a big problem because there is a risk that a machine like this refuses to boot.

A quick look at the file /sbin/mkinitrd version 1.4.8 module search should be around line 624.
 
Old 03-14-2014, 06:29 AM   #2
mancha
Member
 
Registered: Aug 2012
Posts: 279

Rep: Reputation: Disabled
Are you sure it's not mptspi?

--mancha
 
Old 03-14-2014, 06:33 AM   #3
paolo27957
LQ Newbie
 
Registered: Aug 2010
Location: Roma, Italy
Distribution: slackware
Posts: 12

Original Poster
Rep: Reputation: 2
yes, I'm sorry I misspelled, but the problem remains.
 
Old 03-14-2014, 06:36 AM   #4
mancha
Member
 
Registered: Aug 2012
Posts: 279

Rep: Reputation: Disabled
I'm unable to reproduce your problem.
 
Old 03-14-2014, 07:02 AM   #5
mancha
Member
 
Registered: Aug 2012
Posts: 279

Rep: Reputation: Disabled
Can you run the following:

Code:
$ bash -x mkinitrd -c -k 3.10.30-smp -m mptspi:ext4 -f ext4 -r /dev/sdb2 -l it -u -o /tmp/remove >log1.txt 2>&1
$ bash -x mkinitrd -c -k 3.10.30-smp -m ext4:mptspi -f ext4 -r /dev/sdb2 -l it -u -o /tmp/remove >log2.txt 2>&1
and post log1.txt & log2.txt to a pastebin (e.g. dpaste.com)?

--mancha

Last edited by mancha; 03-14-2014 at 03:54 PM. Reason: Fix /dev/null mangling
 
Old 03-14-2014, 07:13 AM   #6
paolo27957
LQ Newbie
 
Registered: Aug 2010
Location: Roma, Italy
Distribution: slackware
Posts: 12

Original Poster
Rep: Reputation: 2
Quote:
Can you run the following:

Code:

$ bash -x mkinitrd -c -k 3.10.30-smp -m mptspi:ext4 -f ext4 -r /dev/sdb2 -l it -u -o /dev/null>log1.txt 2>&1
$ bash -x mkinitrd -c -k 3.10.30-smp -m ext4:mptspi -f ext4 -r /dev/sdb2 -l it -u -o /dev/null>log2.txt 2>&1

and post log1.txt & log2.txt to a pastebin (e.g. dpaste.com)?
No, I am sorry.
My job is behind a firewall that blocks certain sites.

Anyway oddity may be shown by temporarily renaming /boot/initrd.gz to /boot/initrd.gz.original and
/boot/initrd-tree to /boot/initrd-tree.original, then typing as I said in the first post
and checking /boot/initrd-tree/lib/modules/3.xx.xx/kernel.

Of course, don't forget to put back /boot/initrd.gz.original to /boot/initrd.gz.
 
Old 03-14-2014, 07:28 AM   #7
paolo27957
LQ Newbie
 
Registered: Aug 2010
Location: Roma, Italy
Distribution: slackware
Posts: 12

Original Poster
Rep: Reputation: 2
@ mkinitrd mantainers

it would not hurt if it were added to a dry-run option to the script mkinitrd to control his intentions before he does damage ...
 
Old 03-14-2014, 07:47 AM   #8
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 145Reputation: 145
Quote:
Originally Posted by paolo27957 View Post
Of course, don't forget to put back /boot/initrd.gz.original to /boot/initrd.gz.
Does it matter?

Quote:
Originally Posted by paolo27957 View Post
@ mkinitrd mantainers

it would not hurt if it were added to a dry-run option to the script mkinitrd to control his intentions before he does damage ...
Just run mkinitrd with proper -s and -o options.
 
1 members found this post helpful.
Old 03-14-2014, 08:07 AM   #9
paolo27957
LQ Newbie
 
Registered: Aug 2010
Location: Roma, Italy
Distribution: slackware
Posts: 12

Original Poster
Rep: Reputation: 2
Probably was my mistake (typed mtpspi instead mptspi), thank you all for the answers.
 
Old 03-14-2014, 03:54 PM   #10
mancha
Member
 
Registered: Aug 2012
Posts: 279

Rep: Reputation: Disabled
In post #5, the mkinitrd commands I originally posted to debug OP's issue mangle /dev/null.

For anyone who happened to run these, please fix your /dev/null with:

Code:
rm /dev/null; sh /etc/rc.d/rc.udev reload
I've edited that post since to remove the error.

--mancha
 
  


Reply

Tags
boot failure, initrd


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
sudo mkinitrd -o /boot/initrd.img-2.6.32.9 2.6.32.9 sudo: mkinitrd: command not foun vishwas181 Linux - Newbie 1 02-27-2010 01:16 AM
SU command oddities SGlassman Linux - General 2 07-23-2008 08:28 AM
Vi's oddities alienDog Linux - Software 4 08-08-2005 07:16 PM
The oddities of Linux LinuxPadawan Linux - Software 9 03-15-2005 10:11 PM
xmms oddities perryub Linux - Software 1 02-16-2005 11:09 AM


All times are GMT -5. The time now is 04:32 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration