|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast2-Bootloader module starta with error 'Unknown udev device' | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Forgotten User clscCQKGhp <forgotten_clscCQKGhp> |
| Component: | YaST2 | Assignee: | systemd maintainers <systemd-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aschnell, chri, christian_haegele, fazerxlo, forgotten_3EC324wqaZ, forgotten_6Bw0Ifx-X6, forgotten_7bbI62VZki, forgotten_clscCQKGhp, forgotten_DAOOQRPXab, forgotten_dBpEIsMMD7, forgotten_NX4nrDp_bN, forgotten_PMIZxl2pGW, forgotten_xRcrmyYBVX, forgotten_zxeoRDWLI0, forgotten__01A_dEXgn, jreidinger, mpluskal, pastas4, philip.raets, rmilasan, stifi.s, strzol, thomi.schmid, trenn, tschaefer, varkoly, vovochka13 |
| Version: | 13.2 | Flags: | rmilasan:
needinfo?
(forgotten_clscCQKGhp) |
| Target Milestone: | --- | ||
| Hardware: | HP | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 902385 | ||
| Bug Blocks: | |||
| Attachments: |
several occurences of the error,
in YaST2 when bootloader module is used this error is thrown yast error log where the bootloader 'Unknown udev device' appears journalctl output zip packet of y2log files. output of: save_y2logs /tmp/y2logs.tgz |
||
|
Description
Forgotten User clscCQKGhp
2015-01-16 21:43:44 UTC
Created attachment 619898 [details]
in YaST2 when bootloader module is used this error is thrown
Created attachment 619902 [details]
yast error log where the bootloader 'Unknown udev device' appears
Disregard previous y2log attachment, please, was attached by mistake.
Errors related to this bug appears first 01 15 2015.
Hi Jiri, I will probably need complete logs as there is device /dev/disk/by-id/scsi-SHP_LOGICAL_VOLUME_PDNLH0BRH7K331-part2 used for booting, but it looks like such device do not exists. When it appear? during installation or on already installed system? And do you modify somehow your storage configuration? Created attachment 620036 [details]
journalctl output
journalctl output
by complete logs I mean yast ones - en.opensuse.org/openSUSE:Report_a_YaST_bug#I_reported_a_YaST2_bug.2C_and_now_I_am_asked_to_.22attach_y2logs.22_.28for_package_installation_also_.22libzypp_logging.22.29._What_does_that_mean.2C_and_how_do_I_do_that.3F Hello Josef, please tell me what exactely you need, i.e. what should I do to gather it. Appologize, I have rather basic opensuse knowledge only, same for Bugzilla (wrote the answer already and would like to attache the file, but the answer text gone!?). Basicaly I would like to test Xen virtualization on opensuse 13.2. After fresh installation Bootloader module was fine, but I was unable to setup VM guest. I posted this to opensuse forum - by the way: https://forums.opensuse.org/showthread.php/504096-Xen-opensuse-13-2-unable-to-install-vm-guest-quot-End-of-file-while-reading-data-Input-output-error-quot Then I added VirtualBox, which works fine, and after that I would like to change bootloader preference to desktop kernel. Dont know exactely when it appears, but after manipulation with VirtualBox it is no more possible to open Bootloader module with described ERROR. Both Xen and VirtualBox setting I did with GUI wizards, I did not changed storage configuration intentionaly. If I understand Your last message well, I should attach all y2logs and some libzypp. I have y2log-x.gz x=1-7 and where is libzypp ? I will add all y2log-x briefly. in link I post there is recommendation to use our tool to collect all needed logs by: save_y2logs /tmp/y2logs.tgz and then attach /tmp/y2logs.tgz that would be enough. Created attachment 620041 [details]
zip packet of y2log files.
Created attachment 620043 [details]
output of: save_y2logs /tmp/y2logs.tgz
arvin - any idea why /dev/disk/by-id/scsi-SHP_LOGICAL_VOLUME_PDNLH0BRH7K331-part2 disappeared? The links created by udev are incomplete. From the logs: 2015-01-16 22:21:11 <1> Osuse13(10772) [libstorage] DevAndSys.cc(probe):127 data[sda] -> scsi-0HP_LOGICAL_VOLUME_00000000 scsi-3600508b1001c8fb66b42c88e3c3ec2c6 wwn-0x600508b1001c8fb66b42c88e3c3ec2c6 2015-01-16 22:21:11 <1> Osuse13(10772) [libstorage] DevAndSys.cc(probe):127 data[sda1] -> scsi-0HP_LOGICAL_VOLUME_00000000-part1 scsi-3600508b1001c8fb66b42c88e3c3ec2c6-part1 wwn-0x600508b1001c8fb66b42c88e3c3ec2c6-part1 2015-01-16 22:21:11 <1> Osuse13(10772) [libstorage] DevAndSys.cc(probe):127 data[sda2] -> scsi-0HP_LOGICAL_VOLUME_00000000-part2 scsi-3600508b1001c8fb66b42c88e3c3ec2c6-part2 scsi-SHP_LOGICAL_VOLUME_PDNLH0BRH7K331-part2 wwn-0x600508b1001c8fb66b42c88e3c3ec2c6-part2 libstorage constructs the device names for partitions from the device names of the disk and there scsi-SHP_LOGICAL_VOLUME_PDNLH0BRH7K331 is missing. ok, so looks like problem of udev. Reassign to udev maintainer as udev link missing (In reply to Josef Reidinger from comment #12) Wrong maintainer: osc maintainer --email systemd Defined in package: Base:System/systemd bugowner of systemd : systemd-maintainers@suse.de maintainer of systemd : crrodriguez@opensuse.org, jjolly@suse.com, werner@suse.com, fcrozat@suse.com, rmilasan@suse.com, systemd-maintainers@suse.de, thomas.blume@suse.com (In reply to Dr. Werner Fink from comment #13) > (In reply to Josef Reidinger from comment #12) > > Wrong maintainer: > > osc maintainer --email systemd > Defined in package: Base:System/systemd > bugowner of systemd : > systemd-maintainers@suse.de > > maintainer of systemd : > crrodriguez@opensuse.org, jjolly@suse.com, werner@suse.com, > fcrozat@suse.com, rmilasan@suse.com, systemd-maintainers@suse.de, > thomas.blume@suse.com Sorry, my fault. What the hell is: scsi-SHP_LOGICAL_VOLUME_PDNLH0BRH7K331 ? (In reply to Robert Milasan from comment #15) Wild guess ... HP based device with HP based driver and HP based udev rules (or missed HP based rules) .. ?! Nevertheless enabling LogLevel=debug in /etc/systemd/system.conf might help a bit Ping! @ Jiří Krautwurm: any feedback on question in comment #15 This version of openSUSE changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or consider the bug still valid, please feel free to reopen this bug against that version, or open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime |