Bug 449299
| Summary: | after system restore, could not find filesystem | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gene Czarcinski <gczarcinski> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 9 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-06-06 18:19:30 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: | |||||||
| Attachments: |
|
||||||
|
Description
Gene Czarcinski
2008-06-01 23:11:23 UTC
Created attachment 307324 [details]
vmware console showing error messages on test8
problem duplicated on real hardware The UUID changed when you created a new paritition and used mke2fs to create the filesystem... OK, ... WOW .... and where is this documented? I tried changing /etc/fstab to us the device (dev/sda6) rather than the UUID .... same problem. And what utility can I use to display/change the UUID on a partition?? I know I can fiddle with UUIDs in LVM but how about a regular partition? (In reply to comment #4) > OK, ... WOW .... and where is this documented? > > I tried changing /etc/fstab to us the device (dev/sda6) rather than the UUID > .... same problem. > > And what utility can I use to display/change the UUID on a partition?? I know I > can fiddle with UUIDs in LVM but how about a regular partition? tune2fs -U OK, it is kind of hard to argue with success ... I got it to work using tune2fs ... BUT, it would be more than nice if some of this was documented somewhere [if it is, I could not find it] ... and it still leaves the question of some command to DISPLAY the current UUID on a device ... I did find the "findfs" command which will display a device given a UUID but not the reverse of displaying the UUID given a device. I still want to try editing the grub kernel line to say root=/dev/sda6 to see if that would have given me a running system. But, that will not work with "/" on an LVM Logical Volume ... that will need the UUID. With the emphasis that Fedora (and I assume RHEL) is putting on using LVM and UUID, someone knowledgeable of UUID ins-and-outs needs to create some "tips and tricks" on UUID related matters. While I might be able to write something, as I demonstrated, I am not that knowledgeable! Arrgh ... I just did a quick test where I have a minimal install (like on sda6) but this time on a LVM Logical Volume. What I found is that root=UUID= on grub kernel line is different than the LVM Logical Volume's UUID AND you need both ... you still need to do a tune2fs -U on the Logical Volume's ext3 filesystem. I know that you folks at Red Hat are busy and that it is not your (Chuck's) responsibility to get the right documentation written and posted in the appropriate place and/or manual such as for RHEL. So, whose chain do I pull to get some doc out there (besides this BZ report)? Something tells me that this information needs to be available so that someone is not in a panic when they are trying to restore a system from bare-metal. Yes, they can always reinstall but, if someone has taken the time and effort to create real backups, a reinstall does not look appealing. fedora-documentation docs-request: https://bugzilla.redhat.com/show_bug.cgi?id=450331 closing this as notabug since I consider it to be a lack of documentation rather than a software problem. |