Copy sda home to sdb home

borgward · 03-23-2021, 09:18 PM

Booted Live.

mount /dev/sdb6
mount: /dev/sdb6: can't find in /etc/fstab.

mint@mint:/etc$ cat fstab
overlay / overlay rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0

michaelk · 03-23-2021, 09:22 PM

Code:

sudo mount -t ext4 /dev/sdb6 /mnt/mount_point

Where mount_point is an existing directory or create one if necessary.

Since you are running a live version

Code:

sudo mount -t ext4 /dev/sdb6 /mnt/

borgward · 03-23-2021, 10:17 PM

Mounted sdb6. All I am seeing is 12 .wav files
int@mint:/media/usb_hdd/tom$ ls
'Track 1.wav' 'Track 12.wav' 'Track 4.wav' 'Track 7.wav'
'Track 10.wav' 'Track 2.wav' 'Track 5.wav' 'Track 8.wav'
'Track 11.wav' 'Track 3.wav' 'Track 6.wav' 'Track 9.wav'

I can play them. That's a total of 467.0*MB. The Disks gui shows dev/sdb6 966GB 558GB free (42.3% full) That's a lot more than the 12 .wav tracks.

rnturn · 03-23-2021, 11:24 PM

Quote:

Originally Posted by borgward

Booted Live.

mount /dev/sdb6
mount: /dev/sdb6: can't find in /etc/fstab.

mint@mint:/etc$ cat fstab
overlay / overlay rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0

If you're booting from a Live CD, you won't have an /etc/fstab that knows anything about the various disk drives/partitions you have in the system. You will have to be explicit when you issue the mount command. I.e. something like:

Code:

$ sudo mount -t ext4 /dev/sdb6 /mnt

HTH...

Sorry michaelk... I didn't see your reply.

rnturn · 03-23-2021, 11:30 PM

Quote:

Originally Posted by borgward

Mounted sdb6. All I am seeing is 12 .wav files
int@mint:/media/usb_hdd/tom$ ls
'Track 1.wav' 'Track 12.wav' 'Track 4.wav' 'Track 7.wav'
'Track 10.wav' 'Track 2.wav' 'Track 5.wav' 'Track 8.wav'
'Track 11.wav' 'Track 3.wav' 'Track 6.wav' 'Track 9.wav'

I can play them. That's a total of 467.0*MB. The Disks gui shows dev/sdb6 966GB 558GB free (42.3% full) That's a lot more than the 12 .wav tracks.

Try:

Code:

$ ls -a

The "-a" switch will list everything in that directory.
I suspect you have a lot more files sitting in hidden subdirectories.

HTH...

borgward · 03-24-2021, 12:06 AM

mint@mint:/media/mint/9983149b-3a05-462b-96a6-939625e6c7b6/tom$ ls -a
. 'Track 10.wav' 'Track 2.wav' 'Track 5.wav' 'Track 8.wav'
.. 'Track 11.wav' 'Track 3.wav' 'Track 6.wav' 'Track 9.wav'
'Track 1.wav' 'Track 12.wav' 'Track 4.wav' 'Track 7.wav'

borgward · 03-24-2021, 04:34 PM

I reinstalled 20.1 on the 1TB drive. Running rsync to copy home to sdb6.
sudo rsync --recursive /home/tom /media/tom/fd63654b-ef04-49a8-afaf-dfdd53052a2
Getting skipping non-regular file "tom/.config/chromium/SingletonCookie" and about 10 more similar ones. What's with that? Everything seems to be progressing nicely. Is there a better way to run rsync?

michaelk · 03-24-2021, 05:16 PM

I would guess a link.
Per the man page

Quote:

Three basic behaviors are possible when rsync encounters a symbolic
link in the source directory.

By default, symbolic links are not transferred at all. A message
"skipping non-regular" file is emitted for any symlinks that exist.

If --links is specified, then symlinks are recreated with the same tar-
get on the destination. Note that --archive implies --links.

If --copy-links is specified, then symlinks are "collapsed" by copying
their referent, rather than the symlink.

Rsync can also distinguish "safe" and "unsafe" symbolic links. An
example where this might be used is a web site mirror that wishes to
ensure that the rsync module that is copied does not include symbolic
links to /etc/passwd in the public section of the site. Using
--copy-unsafe-links will cause any links to be copied as the file they
point to on the destination. Using --safe-links will cause unsafe
links to be omitted altogether. (Note that you must specify --links
for --safe-links to have any effect.)

Symbolic links are considered unsafe if they are absolute symlinks
(start with /), empty, or if they contain enough ".." components to
ascend from the directory being copied.

Here's a summary of how the symlink options are interpreted. The list
is in order of precedence, so if your combination of options isn't men-
tioned, use the first line that is a complete subset of your options:

--copy-links
Turn all symlinks into normal files (leaving no symlinks for any
other options to affect).

--links --copy-unsafe-links
Turn all unsafe symlinks into files and duplicate all safe sym-
links.

--copy-unsafe-links
Turn all unsafe symlinks into files, noisily skip all safe sym-
links.

--links --safe-links
Duplicate safe symlinks and skip unsafe ones.

--links
Duplicate all symlinks.

borgward · 03-24-2021, 08:46 PM

Completed rsync. 20.1 now only boots to login page. After I enter password the login prompt returns. I opened terminal which would accept the password. 20.1 did bot normally before running rsync. Maybe I need to do rsync over again:
rsync --lnks --recursive ... Will that work, or do I have to choose one or the other?

michaelk · 03-24-2021, 09:23 PM

Are you rsyncing from 18 to 20? There could be differences between configuration files among other things that could have be overwritten that is causing the login problem. Could be permission problems with your .Xauthority file. Could be problems with the login manager which depends on what desktop you are running.

borgward · 03-24-2021, 10:07 PM

Yes from 18 to 20. Booted 20.1. went to terminal changed ownership of .Xauthority. Went back to login page. Still will not take my password.

Maybe use gparted to wipe home and then rsync --link from 18 to 20 or renistall and then rsync --link. Maybe not configure anything until I do rsync.