Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This post is more of a post-fix root cause hunting expedition. The problem was fixed by a reboot. :-D The box in question is a RHEL 7.6 server. Technically Oracle Linux Server 7.6. I have a 1TB disk that I partitioned using fdisk into 3 partitions. 2 of which are getting used as raw Oracle ASM disks, and the other one is a 100GB partition that I wanted mount up as an xfs file system. I ran mkfs on the partition, put it in the fstab, and tried to mount it. No errors. Exit code is zero. But it didn't mount. Mount command does not show it mounted at all. I tried reformatting as ext4, same problem. I was trying to mount it using the UUID, which I checked with blkid and verified was correct. I tried mounting it using just the path to the disk, nothing would fix it.
And so I figured what the heck I'm probably forgetting some command that would probably get run on boot, so I rebooted. And it mounts up just fine.
So the question is what was I missing that a reboot fixed? I can unmount and remount it to my hearts content now with no issues.
And to piggyback on my own post, if anyone happens to know, those two ASM disks that I created don't seem to persist on reboot. Using mknod, I created them in /dev/oracleasm/disks, but when I reboot, they go away. I assume I am missing some oracleasm command or config in a file somewhere. As you can tell, Redhat is not my strong suit. I am an HPUX admin mostly, but hey we all have to work on systems we're not comfy with. Thanks for your time!
As a multibooter who does a lot of repartitioning and cloning as part of OS testing and as backup routine, I think this describes what happens to me on irritatingly frequent occasions, particularly when Fedora is involved. Rather than trying to figure out why a silent mount failure occurs, I just reboot and get on with life. If this happens to you again, give partprobe a try. I think the problem is whatever is supposed to is not keeping device names, UUIDs, Labels and symlinks in /dev/disk/ all in sync when partition tables are manipulated. Mount thinks it succeeds whether or not it actually does, or mount succeeds, but the storage device driver and/or kernel don't get the message.
And to piggyback on my own post, if anyone happens to know, those two ASM disks that I created don't seem to persist on reboot.
/dev is REcreated at every reboot (by udev), so any user-created device files are lost AT those reboots.
You should create extra rules for them in the /etc/udev/rules.d directory for udev to know that they should be created again.
As a multibooter who does a lot of repartitioning and cloning as part of OS testing and as backup routine, I think this describes what happens to me on irritatingly frequent occasions, particularly when Fedora is involved. Rather than trying to figure out why a silent mount failure occurs, I just reboot and get on with life. If this happens to you again, give partprobe a try. I think the problem is whatever is supposed to is not keeping device names, UUIDs, Labels and symlinks in /dev/disk/ all in sync when partition tables are manipulated. Mount thinks it succeeds whether or not it actually does, or mount succeeds, but the storage device driver and/or kernel don't get the message.
Yeah I suspect the same thing, no real answer. Good to know I'm not alone in this lol. Thanks for your input!
Quote:
Originally Posted by ehartman
/dev is REcreated at every reboot (by udev), so any user-created device files are lost AT those reboots.
You should create extra rules for them in the /etc/udev/rules.d directory for udev to know that they should be created again.
Ah thank you! I actually suspected it could be the udev rules, but hadn't looked into it yet. Thanks!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.