URGENT problem with Multipath partitions not present on reboot - CentOS 7
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
What I was saying by "entire disk" meant the disk without using ANY partitions. (In this context by "disk" I mean each LUN presented from your Array.) What you show in fdisk -luc output is that you did create partitions so are not using the "entire disk". My previous point was if you're using LVM for the devices you don't need to put a partition on them as you can use the entire disk as a PV rather than having to use a single partition that has all the space.
You say you used fdisk to parition the sd device then used parted on the mpath. Both fdisk and parted are partitioning tools. I was saying I found issues partitioning the mpath device and on researching it when I ran into it the suggestion was to NOT partition the mpath device but instead partition the underlying sd device then use partprobe and the flush to make sure all related devices see the partitions created that way.
Your fdisk -luc shows a couple of disks where the partition type is "Microsoft basic primary". I'm wondering if those are the ones you're having an issue with. If you notice your other partitions are type "Linux filesyste" instead.
Sorry for the miss understanding. So from what you are saying then potentially it is the way that I created the partitions that could be the issue
No the Microsoft Partitions are from where I connected the iSCSI to a Windows Server and formatted the disks using Windows NTFS for some file storage. The others are VMFS5, I have the same issue with all of them
Just to be clear I wasn't saying you can't use partitions. You can. I was just saying it isn't necessary if your intent is to use the entire disk as an LVM PV in a single VG. Having a partition in and of itself isn't a problem but does complicate the setup a bit so I was saying you could do without the single partition.
IF you do use a partition (which again I'm saying shouldn't be necessary), the rest of what I was saying about was saying to create only using the /dev/sd* device and NOT the /dev/mapper/mpath* or /dev/dm-* devices. Using the partprobe and the flushbufs should make the partitions automatically populate for the /dev/mapper/mpath* and /dev/dm-* devices from what is discovered in the associated /dev/sd* device. You should not have to be creating any links yourself.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.