I think that Discourse (the forum engine) just assuming if you reply to the latest comment is clear that you are replying to the comment right above. 
Different is when you reply to a comment in the middle of the discussion.
1 Like
Testing @rugyada suggestion. @CharlesGibbsNam I think she may be right. 
I had been thinking I was losing my mind. I kept saying, “I know I clicked the right reply button.”
2 Likes
@CharlesGibbsNam we are sorry you encountered this problem. The suggestion to use KDE Partition Manager by @P_J is valid.
That is what the KDE Partition Manager does. It simply adds mount points to /etc/fstab. You do not create a new partition there is not formatting. There is no loss of data, I just checked this and it does work here.
In OMLx Cooker and ROME as of right now the KDE Partition Manager is only allowing to set mount point by Device Node. That works for me.
I just did that and checked, that partition is a system partition and it boots and everything is there.
1 Like
Hi Ben, Thanks, I am working through that as we speak, Was not doubting just did not know how or where to get what was needed. I am working through all this now…
Thanks for the input (and feedback)
Regards C
1 Like
I just discovered that Dolphin is still asking for a password to open that partition. That would seem to be a bug to me. I will change the entry to UUID in /etc/fstab and see what that does. But we are likely gonna need a bug report. I need to wait until an .iso download finishes to test further.
Hey Ben.
Yes i have found that to be the case as well, once I go elsewhere in Dolphin, as soon as I come back to that drive I need to enter my password again. For the bug report just “talk” me through it and I’ll do what I can.
Regards C
iHI @CharlesGibbsNam , did you use the same user name for both distros. I often have multiple distros on my laptop and share certain drive across them and have never had a problem, but i always use the same user name for each?
@CharlesGibbsNam First thanks a million times for doing this. This should help:
Plus when you onen New Issue>Bug report it will list some things to fill in, just fill them in as best and completely as you can. If anyone needs more info they will ask.
I will be able to confirm this as a valid “bug” or as I prefer “BUG”. There are 2 problems IMO. User should be able to use UUID in KDE Partition Manager. Second I am less positive of but unless some convention has changed in Linux or OMLx then using device node in /etc/fstab should result in a mounted partition and that is not happening. But the current situation is not achieving the desired results.
Edit: I should add that currently OM devs are buried trying to get a much needed new release out. As a practical matter one needs to manually set entry in /etc/fstab using UUID.
For me this works for my /Data partition which I use without formatting ofc in multiple system partitions.
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=1C54-AB1D /boot/efi vfat noatime,umask=0077 0 2
UUID=2b9f19dd-4588-43ac-bb06-a9a4199b54c6 /Data ext4 noatime 0 2
UUID=26365bee-8e68-4e8a-b7c0-f1db3fcd2856 / xfs noatime 0 1
UUID=4c3cce41-bf13-4a68-8c90-2cb7d2a00b8c /home xfs noatime 0 2
tmpfs /tmp tmpfs noatime,mode=1777 0 0
/dev/nvme0n1p8 /dev/nvme0n1p8 xfs nofail 0 0
/dev/nvme0n1p8 is the one added with KDE Partition Manager. I question that nofail also, perhaps should be noatime followed by 0 2.
Hi Ben, ok, something went VERY wrong with me dicking around in fstab… I’m on my cell now.
I added UUID=… The UUID of the drive which I got from blkid went into fstab removed the /dev/sda entry and pasted in the uuid wrote ojt the code saved and exited… I went to reboot and after a long while of having nothing but the splash screen I was greeted by grub I went into fstab from grub and removed the uuid and replaced it with the /dev/sda again but I still could not boot into the gui. Unplugging the drive had no effect.
So, I have had to reload the system but I am sure the same fault will be there. Just allow me some timeto get everything back up and if I still have time this evening I will submit the bug as directed… If I do not have time I will do it when I am home from work tomorrow.
Regards C
Hi Rich.
Yes I did. Login, username and password are all the same.
Regards C
Hey PJ no worries, I am good to learn how… Thanks though.
Regards C
No rush, no worries. You should be able to boot in console mode and remove or comment out what you need to from /etc/fstab. In grub2 menu go to Advanced Options Console Mode and at the control D prompt enter root password and do what you need to do,
This is more bleeped up than I initially realized.
Yip, no I did the whole ctrl-d thing with root password but it did not help… I’ll get there… Am busy with up dates now…
Regards C
The nofail option will still allow you to boot if that drive is not attached. As far as I understand, partition managers run as root and default to root for partition mount permissions. Adding user to the mount options in /etc/fstab allows it to be mounted as a normal user, including mounting at boot.
If you cant boot into OM, boot into linuxmint mount the OM root partition to /mnt and then you can edit /mnt/etc/fstab with nano or another text editor. either delete the offending line or comment out by placing a # at the begining.
Hi Lee,
Yes, it was setup by default as nofail but from what I saw there was some form or another of disk/dev timeout this is not the full error, but, as the meme goes… When I saw that I knew i’d bleeped up…
I am semi new to this so the chances of me messing stuff up is VERY VERY good… 'Nuff said… I am back up. Drive is still locking me out, so, I will now try again…
Regards C
Hey Rich Thanks. I suppose I could also use the live media of OM for that?
Regards C
Also, the chances of me messing something up is very good , let trudge this a bit… If it really is a problem I will come back to you…
Regards C
Yes, probably more simple for just edit a file.
I would do sudo update-grub2 in this system and in the distro you are booting from as well
(may be sudo update-grub, not sure but you should know)
Booting from the live usb should allow you to easily edit the /etc/fstab .
Would you need to update grub at all? I wouldn’t think so. Once /etc/fstab is fixed, it should boot up just fine. If updating grub is needed, you could chroot and do it, but I would say let the devs help with that.