View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 3 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sat Apr 05, 2008 1:52 pm 
Offline
Joined: Tue Jan 23, 2007 1:38 pm
Posts: 237
Location: Sweden
Trying to set up a new R5F27 backend server I get the following error messages looping on startup until the kernel panics:
Quote:
insmod: insmod: error -1 inserting '/modules/aic7xxx.ko': file exists
insmod: insmod: error -1 inserting '/modules/ieee1394.ko': file exists
insmod: insmod: error -1 inserting '/modules/ohci1394.ko': file exists
insmod: insmod: error -1 inserting '/modules/sbp2.ko': file exists
insmod: insmod: error -1 inserting '/modules/usbcore.ko': file exists

I think the aic7xxx has to do with an on-board Adaptec controller I'm not using. The SCSI disks are controlled by an IBM Serveraid controller. This is hw-raid - KnoppMyth sees one disk, sda. HW is an old IBM eserver 342.

Googling on the issue turned up somebody getting similar results with KnoppMyth on VM-ware and with SCSI disks, but no solutions.
Can anyone point me in the right direction?

Thanks, /Chris

_________________
LinHES R8.2
BE: AMD64X4, 4GB, Hauppauge usb tuners
FE1: Gigabyte F2A85X-UP4, nVidia GT640
FE2: Gigabyte GA-MA69GM-S2H, AthlonX2 4850E 2.5 GHz, 1GB, ASUS GEFORCE 7200GS 256MB
FE3: Asus Chromebox CN60


Top
 Profile  
 
 Post subject:
PostPosted: Fri May 02, 2008 7:16 am 
Offline
Joined: Tue Jan 23, 2007 1:38 pm
Posts: 237
Location: Sweden
I've since circumvented this error by removing all scsi disks and doing an automatic install on an attached SATA disk.

Today, I got the same error again after adding a second SATA disk. LILO executed properly, Linux started to boot, and at some point in time the boot process went astray again. Booting off the Knoppmyth CD revealed that, although it was attached to port 2 on the controller, the second disk "presented itself" as sda, effectively moving my Knoppmyth system to sdb.
It appears that the bare system boots from the correct disk, but since the Knoppmyth installation is on a new device (sdb), the Knoppmyth boot will fail.

Conclusion:
This error is a result of device names changing after the Knoppmyth install. There appears to be references to device names within the Knoppmyth boot process and there appears to be situations where device names do change during the boot process without letting you know. This is kind of hard to see before a system is booted - especially when the boot fails.

Is this the cause for the discussion of using disk labels instead of device names?

Cheers,
/Chris

_________________
LinHES R8.2
BE: AMD64X4, 4GB, Hauppauge usb tuners
FE1: Gigabyte F2A85X-UP4, nVidia GT640
FE2: Gigabyte GA-MA69GM-S2H, AthlonX2 4850E 2.5 GHz, 1GB, ASUS GEFORCE 7200GS 256MB
FE3: Asus Chromebox CN60


Top
 Profile  
 
 Post subject:
PostPosted: Fri May 02, 2008 4:33 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
cahlfors wrote:
Is this the cause for the discussion of using disk labels instead of device names?

Certainly part of it. Labels work even when the device name changes on you for various reasons.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu