[LUNA] Partition question
John Price
jp31415926 at gmail.com
Sun Jun 23 16:41:04 CDT 2019
I always hold down the shift key.
On Sun, Jun 23, 2019 at 3:40 PM Bob Nance <bob.nance at novationsys.com> wrote:
> I forget what interrupts grub. It’s either that you hold down space, tab
> or escape ;)
>
> Bob Nance
> Novation Systems
> https://www.novationsys.com
> +1 256-534-4620
>
> A good review is the best form of flattery! Please take a moment to give
> us five stars on Google https://goo.gl/NGKxW9
> ________________________________
> From: LUNA <luna-bounces_bob.nance=novationsys.com at lunagroup.us> on
> behalf of Michael Hall <hallmw at att.net>
> Sent: Sunday, June 23, 2019 3:05:57 PM
> To: Linux Users of North Alabama Mailing List
> Subject: Re: [LUNA] Partition question
>
> Well brain is not working today. When I boot my system I am not seeing a
> grub menu. It just goes straight into the GUI. How do you stop the boot
> process. I do not see that in the link you sent. I will keep Googling.
>
> On Saturday, June 22, 2019, 5:01:49 PM CDT, Bob Nance <
> bob.nance at novationsys.com> wrote:
>
> Assuming the arguments are similar to other Eunices, stop the boot
> process and edit the boot argument to include “s” on the line that mentions
> the most arguments :)
>
> Here is an article about it. It looks like Ubuntu has a rescue mode that
> is single user.
>
>
> https://www.google.com/amp/s/www.linuxtechi.com/boot-ubuntu-18-04-debian-9-rescue-emergency-mode/amp/
>
> Be aware that some Linux/Unix bring up the root drive in read-only mode
> when booting into single-user mode. You may have to remount the drive in
> “read-write” mode to make the changes you need
>
> # mount -o remount,rw. /
>
> Should work.
>
>
>
> ———————
> Bob Nance
> Novation Systems
> https://www.novationsys.com
> +1 256-534-4620
>
> A good review is the best form of flattery! Please take a moment to give
> us five stars on Google https://goo.gl/NGKxW9
> ________________________________
> From: LUNA <luna-bounces_bob.nance=novationsys.com at lunagroup.us> on
> behalf of Michael Hall <hallmw at att.net>
> Sent: Saturday, June 22, 2019 4:52:20 PM
> To: Linux Users of North Alabama Mailing List
> Subject: Re: [LUNA] Partition question
>
> Well I have not done this much on my system as I have always set it up
> like I want it. I will have to find out how to know if I am in single user
> on this machine. I have nothing in the current home that I need so not a
> problem if I cannot access it. I will probably have more questions. Here
> is the result of the ls -al /dev/disk/by-uuid
> michael at michael-Alienware-15-R3:~$ sudo ls -al /dev/disk/by-uuid
> total 0
> drwxr-xr-x 2 root root 80 Jun 22 11:57 .
> drwxr-xr-x 6 root root 120 Jun 22 11:57 ..
> lrwxrwxrwx 1 root root 10 Jun 22 11:57
> 215b343b-67bd-4ba3-bb71-3b265d066630 -> ../../sda1
> lrwxrwxrwx 1 root root 15 Jun 22 11:57
> 71b2e519-0392-4af3-a567-35f24d408701 -> ../../nvme0n1p1
> I think I just need to get to single user mode, not sure if I remember.
> When I login with the account that gigaparts created, I see an icon on my
> desktop for the drive. If I bring up the file viewer I see under devices
> the 1TB drive with the icon to eject it. I am just mulling things over in
> my mind.
>
>
>
> On Saturday, June 22, 2019, 2:47:49 PM CDT, Bob Nance <
> bob.nance at novationsys.com> wrote:
>
> Yes. If it shows at the top level of the mount point, you can just simply
> change the mount point and everything should show up.
>
> Two things: 1) whatever is already at /home will be inaccessible. If
> you’ve been using it with your latest account, make sure you save
> everything to the drive you’re mounting before you change the mount point.
> 2) do this all in single user mode to make sure you don’t break any running
> processes that expect $HOME to have files and folders available to them
> while running.
>
> One more, if your UID number does not match you old number, make sure you
> perform the chown command I mentioned. But I put chmod instead of chown,
> sorry; you do the s// in my answer ;)
>
> Last thing, to be absolutely sure that no process is holding onto a
> non-existent file, inode, pipe, or anything else on the old /home, reboot.
> Easier to do on a single user system than re-unit any processes. Besides,
> then you have your test for the mount.
>
> ———————
> Bob Nance
> Novation Systems
> https://www.novationsys.com
> +1 256-534-4620
>
> A good review is the best form of flattery! Please take a moment to give
> us five stars on Google https://goo.gl/NGKxW9
> ________________________________
> From: LUNA <luna-bounces_bob.nance=novationsys.com at lunagroup.us> on
> behalf of Michael Hall <hallmw at att.net>
> Sent: Saturday, June 22, 2019 2:39:21 PM
> To: Linux Users of North Alabama Mailing List
> Subject: Re: [LUNA] Partition question
>
> Bob, Thanks for the reply. My old $HOME is showing up as
> /media/michael/UUID/hallmw when I click the HD. All my old data seems to
> be there. I thought that it was getting mounted as a removable drive.
> Just want to make sure I do this right and not screw this up since I just
> got it back. So does that mean I am good? I since it is showing up at
> that I should not have /home/home..... when I follow the steps?
>
> On Saturday, June 22, 2019, 1:07:21 PM CDT, Bob Nance <
> bob.nance at novationsys.com> wrote:
>
> I think that the "/media" implies that the OS thinks it's a removable
> drive. It is also mounting it in your user context and not under the
> system's auspices. Is your old $HOME showing up under
> /media/Michael/[UUID]/home/mwhall and reflecting what you think is the
> correct data? If that's the case, you're good. All your data is still
> available.
>
> Beware that I have really dug deep into the weeds in my answer. Please
> forgive an old man's ramblings.
>
> The first thing you need to do is determine the actual hardware device
> that the media manager is finding. You can pore through the kernel log,
> dmesg or the like. It may even be in the syslog. Since it's not mounting it
> until you login (I am 99% sure), it should be pretty easy to find; just
> look for the login messages and you should see events posted by "udisk" or
> some version of that name.
>
> If you want to discover which device is actually being mounted, you can,
> again, look at the disk messages in the kernel log, dmesg, or other logs.
> Another way is to stuff that UUID into your brain and then type:
>
> ls -al /dev/disk/by-uuid/
>
> And look for that UUID. The UUID will actually be a link to the relative
> hardware device. The name should look something like ../../sdc2. That last
> part is your actual relative hardware device name. (by the way, under the
> abstraction layer that the disk driver produces, you can actually trust the
> UUID information, since it is written in the volume label, it won't change
> and is unique, so you don't need to find the /dev/sdXn designator, if you
> don't want to).
>
> Now that you have that, you can tell the OS that you want to mount that
> drive onto the system at a specific location. The system mounts occur
> before you login, so "udisk" will not find an unmounted disk, so you don't
> have to worry about it mounting it before your file system initialization.
>
> The system stores the mounted drive information in the file /etc/fstab.
> Simply add the drive information into that file to force the system
> initialization to mount the volume before udisk can find it. Look at "man 5
> fstab" or just read the file to see what goes into it.
>
> There are two ways to enter the information into the fstab file.
>
> Use the hardware device name (white space can be spaces or tabs).
>
> /dev/sdc3 /home ext4 rw 0 0
>
> OR use the volume label to designate the disk volume
>
> LABEL=[UUID] /home ext4 defaults 0 0
>
> The first field is either the label or the device.
>
> The second field is the directory onto which you want to mount the volume.
>
> The third field is the file system format that determines which system
> driver will be used to talk to the volume.
>
> The fourth field is a comma-separated list of options for the file system.
> Here, I have listed "read-write" for a mounting option. You can also put
> any of these. Don't use spaces between commas and options. I stole this
> from the man page.
>
> defaults
> use default options: rw, suid, dev, exec, auto,
> nouser, and async.
>
> noauto do not mount when "mount -a" is given (e.g., at boot
> time)
>
> user allow a user to mount
>
> owner allow device owner to mount
>
> comment
> or x-<name> for use by fstab-maintaining programs
>
> nofail do not report errors for this device if it does not
> exist.
>
>
> The second to last number is what dump level you want to prescribe to it
> (don't back this up unless you are performing a "dump 0" is what's there
> now).
>
> The last number is what order you want this disk checked when an fsck is
> performed. If everyone is zero, the init process will simply check them in
> order that they appear in the file.
>
> CAVEAT EMPTOR
> Now that I completely over-explained this answer, let me warn you that, if
> the previous volume was formatted to be the "/" mounted drive, then it
> already has path information on it that will mess up the mount. If your
> home directory was on /home/mwhall and that drive was mounted as "/" AND
> you mount the drive as "/home" then you will find your home directory at
> "/home/home/mwhall" If you want it to appear at /home/mwhall, you will have
> to move it. I recommend at "piped tar" for moving data from one folder to
> another.
>
> # cd /home/home ; tar cf - mwhall | (cd /home ; tar xvf - )
>
> Also, be aware that it's possible that your own UID may be different on
> your new system than it was on the last. If that is the case, after you
> mount this drive, you will need to change ownership to match the new UID.
>
> # chmod -R mwhall.mwhall /home/mwhall
>
> will probably fix that for you.
>
>
> On 6/22/19, 12:22 PM, "LUNA on behalf of Michael Hall"
> <luna-bounces_bob.nance=novationsys.com at lunagroup.us on behalf of
> hallmw at att.net> wrote:
>
> I have my machine back up and running. Finally got fed up and took it
> to gigaparts to just check out the hardware. All that was ok. They put
> the latest of Ubuntu Mate (18.04) on the machine. I created my account
> that I was using. I noticed that my second drive a 1 TB HD is mounted as
> /media/michael/<some number that looks like a guid>. I want to mount this
> drive as /home and my old hallmw directory is on it with my data. Can
> someone help me out on how to do that and not loose my data. I am going to
> copy it to my USB stick before I start.
> Thanks,Michael
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lunagroup.us/pipermail/luna/attachments/20190622/07fc0049/attachment.html
> >
> _______________________________________________
> LUNA mailing list
> LUNA at lunagroup.us
> http://lunagroup.us/mailman/listinfo/luna
>
>
> _______________________________________________
> LUNA mailing list
> LUNA at lunagroup.us
> http://lunagroup.us/mailman/listinfo/luna
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lunagroup.us/pipermail/luna/attachments/20190622/84ab8d7f/attachment.html
> >
> _______________________________________________
> LUNA mailing list
> LUNA at lunagroup.us
> http://lunagroup.us/mailman/listinfo/luna
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lunagroup.us/pipermail/luna/attachments/20190622/747c7c89/attachment.html
> >
> _______________________________________________
> LUNA mailing list
> LUNA at lunagroup.us
> http://lunagroup.us/mailman/listinfo/luna
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lunagroup.us/pipermail/luna/attachments/20190622/af447c87/attachment.html
> >
> _______________________________________________
> LUNA mailing list
> LUNA at lunagroup.us
> http://lunagroup.us/mailman/listinfo/luna
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lunagroup.us/pipermail/luna/attachments/20190622/4cc7e36f/attachment.html
> >
> _______________________________________________
> LUNA mailing list
> LUNA at lunagroup.us
> http://lunagroup.us/mailman/listinfo/luna
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lunagroup.us/pipermail/luna/attachments/20190623/60548d0c/attachment.html
> >
> _______________________________________________
> LUNA mailing list
> LUNA at lunagroup.us
> http://lunagroup.us/mailman/listinfo/luna
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lunagroup.us/pipermail/luna/attachments/20190623/7608c8f9/attachment.html
> >
> _______________________________________________
> LUNA mailing list
> LUNA at lunagroup.us
> http://lunagroup.us/mailman/listinfo/luna
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lunagroup.us/pipermail/luna/attachments/20190623/1d483e47/attachment.html>
More information about the LUNA
mailing list