Bug 662217
Summary: | during startup in messages log: file /bin/plymouthd seems to be deleted | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eddie Lania <eddie> |
Component: | plymouth | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | fedora, rstrode, thomasj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-03-24 14:58:19 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
Eddie Lania
2010-12-10 22:03:07 UTC
Okay, it seems to be solved by executing: plymouth-set-default-theme charge --rebuild-initrd But after a reboot with the newly generated initramfs a new problem arises: .%G.%G Welcome to .[0;34mFedora.[0;39m Press 'I' to enter interactive startup. Starting udev: .%G.[60G[.[0;32m OK .[0;39m] Setting hostname hestia.lania-intra.net: .[60G[.[0;32m OK .[0;39m] udevd-work[779]: setfilecon /dev/dm-3 failed: No such file or directory Investigation of the /var/log/messages results in: Feb 26 13:24:46 hestia kernel: dracut: Starting plymouth daemon Feb 26 13:24:46 hestia kernel: input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input3 Feb 26 13:24:46 hestia kernel: dracut: rd_NO_MD: removing MD RAID activation Feb 26 13:24:46 hestia kernel: pata_pdc2027x 0000:01:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 Feb 26 13:24:46 hestia kernel: pata_pdc2027x 0000:01:00.0: PLL input clock 16615 kHz Feb 26 13:24:46 hestia kernel: scsi4 : pata_pdc2027x Feb 26 13:24:46 hestia kernel: scsi5 : pata_pdc2027x Feb 26 13:24:46 hestia kernel: ata5: PATA max UDMA/133 mmio m65536@0xff8f0000 cmd 0xff8f17c0 irq 21 Feb 26 13:24:46 hestia kernel: ata6: PATA max UDMA/133 mmio m65536@0xff8f0000 cmd 0xff8f15c0 irq 21 Feb 26 13:24:46 hestia kernel: ata5.00: ATA-6: WDC WD800JB-00JJC0, 05.01C05, max UDMA/100 Feb 26 13:24:46 hestia kernel: ata5.00: 156301488 sectors, multi 16: LBA Feb 26 13:24:46 hestia kernel: ata5.00: configured for UDMA/100 Feb 26 13:24:46 hestia kernel: scsi 4:0:0:0: Direct-Access ATA WDC WD800JB-00JJ 05.0 PQ: 0 ANSI: 5 Feb 26 13:24:46 hestia kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0 Feb 26 13:24:46 hestia kernel: sd 4:0:0:0: [sda] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB) Feb 26 13:24:46 hestia kernel: sd 4:0:0:0: [sda] Write Protect is off Feb 26 13:24:46 hestia kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 26 13:24:46 hestia kernel: sda: sda1 sda2 Feb 26 13:24:46 hestia kernel: sd 4:0:0:0: [sda] Attached SCSI disk Feb 26 13:24:46 hestia kernel: ata6.00: ATA-6: WDC WD800JB-00JJC0, 05.01C05, max UDMA/100 Feb 26 13:24:46 hestia kernel: ata6.00: 156301488 sectors, multi 16: LBA Feb 26 13:24:46 hestia kernel: ata6.00: configured for UDMA/100 Feb 26 13:24:46 hestia kernel: scsi 5:0:0:0: Direct-Access ATA WDC WD800JB-00JJ 05.0 PQ: 0 ANSI: 5 Feb 26 13:24:46 hestia kernel: sd 5:0:0:0: [sdb] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB) Feb 26 13:24:46 hestia kernel: sd 5:0:0:0: [sdb] Write Protect is off Feb 26 13:24:46 hestia kernel: sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 26 13:24:46 hestia kernel: sdb: Feb 26 13:24:46 hestia kernel: sd 5:0:0:0: Attached scsi generic sg2 type 0 Feb 26 13:24:46 hestia kernel: sdb1 sdb2 Feb 26 13:24:46 hestia kernel: sd 5:0:0:0: [sdb] Attached SCSI disk Feb 26 13:24:46 hestia kernel: dracut: Scanning for dmraid devices pdc_babgifibfd Feb 26 13:24:46 hestia kernel: dracut: Found dmraid sets: Feb 26 13:24:46 hestia kernel: dracut: pdc_babgifibfd Feb 26 13:24:46 hestia kernel: dracut: Activating pdc_babgifibfd Feb 26 13:24:46 hestia kernel: device-mapper: ioctl: device doesn't appear to be in the dev hash table. Feb 26 13:24:46 hestia kernel: dracut: RAID set "pdc_babgifibfd" was activated Feb 26 13:24:46 hestia kernel: dracut: RAID set "pdc_babgifibfd" was not activated Feb 26 13:24:46 hestia kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode Feb 26 13:24:46 hestia kernel: dracut: Mounted root filesystem /dev/mapper/pdc_babgifibfdp1 Now how am I going to solve that "device-mapper: ioctl: device doesn't appear to be in the dev hash table" error? Regards, Eddie. |