Bug 216175
| Summary: | udev-103-2 hangs boot sequence if media is present in a ZIP250 drive | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joseph Sacco <jsacco> |
| Component: | udev | Assignee: | Harald Hoyer <harald> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | powerpc | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 103-3 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-01-04 15:05:21 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: | |||
Problem seems to have vanished in udev-103-3 -Joseph |
udev-103-2 hangs the boot sequence if media is in a ZIP250 drive. When this occurs the zipdrive spins, and spins and spins with read light on. Ejecting the media allows udev start up to complete after which the boot sequence finishes. Inserting the media into the drive after the system is up does not cause the ZIP drive to be recognized as /dev/hdd4 has not yet been created. Mounting the drive as root mount /dev/hdd works and causes /dev/hdd4 to be created. Once the permissions for /dev/hdd4 are changed to the desktop owner, inserting and ejecting the media works as expected. As a side note... after a recent system update in the past 7-10 days, kudzu no longer runs; it segfaults. -Joseph