Bug 219
Summary: | Error with swapon in rc.sysinit when swap is on a device handled by kerneld | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Marc MERLIN <marc_soft> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1998-12-06 04:51:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marc MERLIN
1998-11-29 00:57:03 UTC
Fixed summary to say "Error with swapon in rc.sysinit when swap is on a device handled by kerneld" (quoted here just in case bugzilla doesn't let me change it) This is a valid point. Was this a device or swap partition that was added after the initial installation? If it is then the initrd.img is possible not loading the support for the device the swap file is one because the install creates the initial initrd.img file according to the hardware it detects (or you choose) during the installtion. You can create a new initrd.img with support for your new card and replace your current one. This should allow the first swapon -a to work. If this is not the case then your suggestion should also work. You are correct, the swap device was added by hand, after RH was installed. The kernel was custom compiled (without initrd), so that's why the scsi module is loaded later (the system boots on IDE). I hadn't realized that this will only hit people who install a card after the initial install and don't use the modular kernels, so even though the suggested change won't hurt, it's not really a bug. I see no point in removing a valid albeit harmless error message cosmetically. Add the device to the initrd. |