I'm using Debian 9.5 StretchI had a disk (1tb) mounted as /home/myuname/x1. The x1 disk failed. The disk's data is unimportant. But, I do need more space. Ergo, I got a new disk (4tb); I intended to replace the disk and use gparted to intialize and partition the new disk but, I have been unable to re-enter the gui.

Upon boot, following grub, I am automatically placed in emergency mode (I suspect init 2, with no external services). I logged-in as root. I deleted the /home/myuname/x1 directory. Rebooted, then successfully reestablished the mount point using the same name /home/myuname/x1. Then I attempted to mount /dev/sda /home/myuname/x1. No Joy.

I haven't partitioned the disk, only initialized it as a gpt disk. Since it has no partitions (e.g, sda1 -system disk is sdb) I can't get it to mount. gparted would make quick work of this but since I cannot access the gui and can only log in in emergency mode, I cannot use gparted.

Still, I don't understand why a failed mount point in my home directory -a non-system data disk- would cause the whole os to fail into emergency mode. I want to access the gui to fix this problem. Any suggestions for entering the gui (init 5)?

Well, in Linux there are tools and there are GUI frontends to these tools. Note, you do not need the GUI to use the tools. But you can't use the GUI without tools.Now, you do not mount partitions, you mount filesystems. Filesystems reside on hard drive, in case there is two or more filesystems in one drive you need to wrap them into partitions. Thus, the simplest case is when you want to use the whole drive for one filesystem, just create it, no partitioning needed.

The post doesn't make a lot of sense, especially "mount /dev/sda /home/myuname/x1. No Joy."

You can't mount /dev/sda because it's the device node for the disk, not the partition with a filesystem on it.

I'd think if you want help, you could post your /etc/fstab and the output of fdisk -l (blkid is good too) so maybe something will jump out and someone will see what's going on. Long stories are hard to read, just the facts from a terminal. In code tags is nice.

If you have to use gparted, that's cool, it's probably on one of the live disks? or a rescue cd or something.

I advise against such practice. It can lead to confusion. Creating a partition table and a partition, even if it uses all the space, is less confusing. Did you notice that even USB sticks come with a partition table ?

bw123 wrote:The post doesn't make a lot of sense, especially "mount /dev/sda /home/myuname/x1. No Joy." You can't mount /dev/sda because it's the device node for the disk, not the partition with a filesystem on it.

I'd think if you want help, you could post your /etc/fstab and the output of fdisk -l (blkid is good too) so maybe something will jump out and someone will see what's going on. Long stories are hard to read, just the facts from a terminal. In code tags is nice. If you have to use gparted, that's cool, it's probably on one of the live disks? or a rescue cd or something.

Thanks for your response bw123. That's right. I was acknowledging my sketchy memory when I refered to needing sda1 wich is correct but not complete. I'm just getting my feet wet again with 'nix. It's been a while. Your /etc/fstab suggestion is definitely useful, but I'm really just trying to get back into the gui at this moment. Thanks for your suggestions. Every piece of the puzzle helps to reignite the memory.

p.H wrote:Because the mount is present without the option "nofail" in /etc/fstab, so the system considers it is mandatory for proper operation.

Perfect. Thank you. I'm pretty sure this is precisely what I am looking for. I'll edit /etc/fstab and apply the "nofail" option to the line for that mount. Better yet, I'll remove the reference try a reboot, then run gparted, then I'll ensure and reinitiate a line for the new drive. I was concerned it might have something to do with the registration of the drive with a specific [system] serial number and I think that threw me from pursuing it properly. I remember mounting it with a particular UUID(?) I think. I'm slowly getting back to the cl progs and apps. but I'm presently still in that phase where my memory is not practiced -and the systems have changed enough- so that I question myself. Also, I havent found a good installation reference sheet that I can use for each installation, which would have helped.

Segfault wrote:when you want to use the whole drive for one filesystem, just create it, no partitioning needed.

I advise against such practice. It can lead to confusion. Creating a partition table and a partition, even if it uses all the space, is less confusing. Did you notice that even USB sticks come with a partition table ?[/quote]Yes, I have noticed that. And yes, I agree about not mounting the whole drive that way. Also, I want 4 partitions for this disk.

Thanks again, p.H, I appreciate it.

Last edited by Loci.Cantos on 2018-12-22 12:31, edited 1 time in total.