ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007641ClearOSclearos-release-communitypublic2016-03-09 11:352016-03-10 09:51
Reporterdloper 
Assigned Touser2 
PrioritylowSeverityminorReproducibilityhave not tried
StatusclosedResolutionduplicate 
PlatformOSOS Version
Product Version7.2.0 
Target VersionFixed in Version 
Summary0007641: EFI boot mis-manages centos to clearos names for directories
DescriptionEFI boot mis-manages centos to clearos names for directories
Steps To Reproduce
Additional InformationInstalling ClearOS 7 on EFI hardware places packages in a centos directory when it should be clearos. Even if you work around the issue, updates will not work do to the discrepancy in the names.
TagsNo tags attached.
Relationships
duplicate of 0006871closed abylund Anaconda issues with UEFI 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-03-09 11:35dloperNew Issue
2016-03-09 12:57dloperNote Added: 0002791
2016-03-09 14:04user2Relationship addedduplicate of 0006871
2016-03-09 14:04user2Statusnew => closed
2016-03-09 14:04user2Assigned To => user2
2016-03-09 14:04user2Resolutionopen => duplicate
2016-03-10 09:51user2Target Version7.3.0 Beta 1 =>

Notes
(0002791)
dloper   
2016-03-09 12:57   
1. There is an issue with EFI install using ClearOS 7.1.0 or 7.2.0 media. Details below.

2. Issue 0000001 also caused yum update to fail later because it tries to write some files in the /boot/efi/EFI/centos directory instead of /boot/efi/EFI/clearos. Further, when you try to do a yum install kernel-devel it fails.

3. Installing 7 in EFI mode works after the work around I provided in 0000001 and appears to be stable. But I also tried it in BIOS mode and it installs fine but at least on our hardware when I reboot it locks up the device such that it has to be power-cycled. It also locks up sometimes during boot. Since we’re under a severe time crunch, I haven’t had time to check any logs and find the source of the problem. I did move the drive form the system that was locking up to another system and the issue followed, so it’s either a problem with the drive itself (SSD) or more likely a problem with 7 not being fully compatible with the hardware when run in BIOS mode. The same hardware was used for 7 in EFI mode and has been running fine for several days even through several reboots.