| View previous topic :: View next topic |
| Author |
Message |
artvs
n00b
Joined: 01 Apr 2024
Posts: 19
|
 Posted: Mon Apr 08, 2024 9:40 am Post subject: [SOLVED] Unable to mount all RAID partitions. ro - root |
 |
|
I'm trying to install new Gentoo on a pre-assembled software RAID (there was my old system installed)
The structure: (running df -T from a Live CD, I can't copy from KVM):
| Code: |
df -T
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/md126 xfs 2101184 1549344 551840 74% /
/dev/md125 xfs 33536956 18048364 15488592 54% /usr
/dev/md124 xfs 33536956 33600 33503356 1% /tmp
/dev/md123 xfs 67075004 23481160 43593844 36% /var
/dev/md127 xfs 335105048 96269080 238835968 29% /home
|
My fstab
| Code: |
cat /etc/fstab
#<fs> <mountpoint> <type> <opts> <dump/pass>
UUID=741f0d48-c197-1d16-cb20-1669f728008a / xfs rw,noatime 0 1
#UUID=6a01b59d-ae3c-4d14-92f7-ae3aaa479e50 / xfs rw,noatime 0 1
UUID=837d5c37-1b23-4d64-a32e-bfea6d19f92d /tmp xfs rw 0 0
UUID=e2de3314-c5b1-403b-85c6-4dc7d7de224e /usr xfs rw 0 1
UUID=813d60e7-6419-4fd4-8fdf-9eca7b762856 /var xfs rw 0 2
UUID=f70c0512-e349-4a6b-9b3c-4c1706684365 /home xfs rw 0 0
|
If I execute mount -a, all disks mount correctly.
My mdadm.conf
| Code: |
cat /etc/mdadm.conf
#HOMEHOST fairseo
MAILADDR artvs@yandex.ru
MAILFROM mdadm@fairseo.ru
#PROGRAM /usr/sbin/handle-mdadm-events
DEVICE partitions
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=741f0d48:c1971d16:cb201669:f728008a
devices=/dev/sda1,/dev/sdc1
ARRAY /dev/md6 level=raid1 num-devices=2 metadata=1.2 name=livecd:6 UUID=8a59ac74:000cc86e:0b713127:5d9ad5ed
devices=/dev/sda6,/dev/sdc6
ARRAY /dev/md7 level=raid1 num-devices=2 metadata=1.2 name=livecd:7 UUID=9d525d9f:336864c0:27211b82:ef567804
devices=/dev/sda7,/dev/sdc7
ARRAY /dev/md5 level=raid1 num-devices=2 metadata=1.2 name=livecd:5 UUID=8977e19e:ec19b8c3:0456458d:e9daf960
devices=/dev/sda5,/dev/sdc5
ARRAY /dev/md8 level=raid1 num-devices=2 metadata=1.2 name=fairseo.ru:8 UUID=a09fab88:b0b841ff:fd57d3e4:ea81f84c
devices=/dev/sda8,/dev/sdc8
|
blkid (running from Live CD):
| Code: |
/dev/md127: UUID="f70c0512-e349-4a6b-9b3c-4c1706684365" BLOCK_SIZE="4096" TYPE="xfs"
/dev/sdb7: UUID="9d525d9f-3368-64c0-2721-1b82ef567804" UUID_SUB="eb38d637-3f6f-8f43-af8e-e1e9a80524c8" LABEL="livecd:7" TYPE="linux_raid_member"
/dev/sdb5: UUID="8977e19e-ec19-b8c3-0456-458de9daf960" UUID_SUB="57a0d31f-3bbf-9a45-b4d9-a4a0cd6c7770" LABEL="livecd:5" TYPE="linux_raid_member"
/dev/sdb1: UUID="741f0d48-c197-1d16-cb20-1669f728008a" TYPE="linux_raid_member"
/dev/sdb8: UUID="a09fab88-b0b8-41ff-fd57-d3e4ea81f84c" UUID_SUB="01edd0e9-f716-e2b1-9a38-d256f1a08375" LABEL="fairseo.ru:8" TYPE="linux_raid_member"
/dev/sdb6: UUID="8a59ac74-000c-c86e-0b71-31275d9ad5ed" UUID_SUB="781d2f5a-e8f5-1238-bb07-72dfc36bd904" LABEL="livecd:6" TYPE="linux_raid_member"
/dev/md125: UUID="e2de3314-c5b1-403b-85c6-4dc7d7de224e" BLOCK_SIZE="512" TYPE="xfs"
/dev/md123: UUID="813d60e7-6419-4fd4-8fdf-9eca7b762856" BLOCK_SIZE="512" TYPE="xfs"
/dev/md126: UUID="6a01b59d-ae3c-4d14-92f7-ae3aaa479e50" BLOCK_SIZE="512" TYPE="xfs"
/dev/sda7: UUID="9d525d9f-3368-64c0-2721-1b82ef567804" UUID_SUB="5c0327f9-b700-f871-21cb-14b887e1a9cd" LABEL="livecd:7" TYPE="linux_raid_member"
/dev/sda5: UUID="8977e19e-ec19-b8c3-0456-458de9daf960" UUID_SUB="34c71aa2-8a3f-13bb-3e11-fd8add0bf98a" LABEL="livecd:5" TYPE="linux_raid_member"
/dev/sda1: UUID="741f0d48-c197-1d16-cb20-1669f728008a" TYPE="linux_raid_member"
/dev/sda8: UUID="a09fab88-b0b8-41ff-fd57-d3e4ea81f84c" UUID_SUB="980ede7f-d380-d7e5-e442-fb8ea51639c7" LABEL="fairseo.ru:8" TYPE="linux_raid_member"
/dev/sda6: UUID="8a59ac74-000c-c86e-0b71-31275d9ad5ed" UUID_SUB="67cb4653-6d25-7381-6dc4-fb4f180a3f66" LABEL="livecd:6" TYPE="linux_raid_member"
/dev/md124: UUID="837d5c37-1b23-4d64-a32e-bfea6d19f92d" BLOCK_SIZE="512" TYPE="xfs"
|
cat /proc/mdstat (running from Live CD):
| Code: |
cat /proc/mdstat
Personalities : [raid1]
md123 : active raid1 sdb7[1] sda7[0]
67107768 blocks super 1.2 [2/2] [UU]
md124 : active raid1 sdb5[1] sda5[0]
33553336 blocks super 1.2 [2/2] [UU]
md125 : active raid1 sdb6[1] sda6[0]
33553336 blocks super 1.2 [2/2] [UU]
md126 : active raid1 sdb1[1] sda1[0]
2111424 blocks [2/2] [UU]
md127 : active (auto-read-only) raid1 sdb8[1] sda8[0]
335268752 blocks super 1.2 [2/2] [UU]
unused devices: <none>
|
Typically, only two partitions are mounted at boot time, /dev/md126 (root) and /dev/md125 (/usr), but read-only (ro). The other partitions do not mount!
What's strange: once root was mounted in rw mode. Why?
My assumption is that the RAID devices do not have enough time to initialize correctly before mounting.
What should I do?
Last edited by artvs on Tue Apr 09, 2024 2:55 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54272
Location: 56N 3W
|
| Posted: Mon Apr 08, 2024 9:53 am Post subject: |
|
|
artvs,
| Code: | cat /etc/fstab
#<fs> <mountpoint> <type> <opts> <dump/pass>
UUID=741f0d48-c197-1d16-cb20-1669f728008a / xfs rw,noatime 0 1
#UUID=6a01b59d-ae3c-4d14-92f7-ae3aaa479e50 / xfs rw,noatime 0 1
UUID=837d5c37-1b23-4d64-a32e-bfea6d19f92d /tmp xfs rw 0 0
UUID=e2de3314-c5b1-403b-85c6-4dc7d7de224e /usr xfs rw 0 1
UUID=813d60e7-6419-4fd4-8fdf-9eca7b762856 /var xfs rw 0 2
UUID=f70c0512-e349-4a6b-9b3c-4c1706684365 /home xfs rw 0 0 |
Your pass column looks wrong.
| man fstab: | The sixth field (fs_passno).
This field is used by fsck(8) to determine the order in which
filesystem checks are done at boot time. The root filesystem should be
specified with a fs_passno of 1. Other filesystems should have a
fs_passno of 2. Filesystems within a drive will be checked
sequentially, but filesystems on different drives will be checked at
the same time to utilize parallelism available in the hardware.
Defaults to zero (don’t check the filesystem) if not present. |
Where is /usr mounted?
It should be checked and mounted in the initrd as some of the binaries needed to get started are in /usr now.
See News item | Code: | | 2024-01-05 Separate /usr now requires an initramfs |
Why is /tmp on a HDD?
Its usually in tmpfs these days.
If xfs is a journal fs, I think it is, a passno of 0 is OK everywhere except / as mount will do a journal replay if the filesystem is not clean.
That is, don't run fsck.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
artvs
n00b
Joined: 01 Apr 2024
Posts: 19
|
| Posted: Mon Apr 08, 2024 10:34 am Post subject: |
|
|
I didn't assemble this system, and it was done back in 2012. Therefore, I don't know why.
Possibly they were trying to save memory.
Another point. The old system had Grub Legacy, and there was a line
raid=noautodetect md=0,/dev/sda1,/dev/sdb1 root=/dev/md0
I also don't know why. Is such a line necessary in Grub2?
I added only
GRUB_CMDLINE_LINUX_DEFAULT="domdadm"
Changing the pass parameters didn't help.
I added to fstab and commented out the previous line about the /tmp partition
tmpfs /tmp tmpfs defaults,noatime,nosuid,nodev 0 0
that didn't help either - two partitions are read-only. Two others are not present.
And I have lots of errors: can't exec /etc/init.d/mtab - no such file or directory
but these files are actually here. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54272
Location: 56N 3W
|
| Posted: Mon Apr 08, 2024 11:29 am Post subject: |
|
|
artvs,
Raid autodetect only works for metadata 0.90 raid sets. That looks like your /boot as grub legacy was not raid aware.
| Code: | | md=0,/dev/sda1,/dev/sdb1 root=/dev/md0 |
Says to assemble /dev/md0 from dev/sda1 /dev/sdb1 and use it as root.
You don't have an md0.
| Code: | df -T
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/md126 xfs 2101184 1549344 551840 74% /
/dev/md125 xfs 33536956 18048364 15488592 54% /usr
/dev/md124 xfs 33536956 33600 33503356 1% /tmp
/dev/md123 xfs 67075004 23481160 43593844 36% /var
/dev/md127 xfs 335105048 96269080 238835968 29% /home |
Your mounted raid sets cannot be auto assembled as the are metadata 1.2.
Your initrd must be assembling and mounting root but we don't know how yet. That's the next step.
How did you make your initrd?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
artvs
n00b
Joined: 01 Apr 2024
Posts: 19
|
| Posted: Mon Apr 08, 2024 12:44 pm Post subject: |
|
|
| NeddySeagoon wrote: | artvs,
Raid autodetect only works for metadata 0.90 raid sets. That looks like your /boot as grub legacy was not raid aware.
|
My root device has metadata 0.9
| NeddySeagoon wrote: |
| Code: | | md=0,/dev/sda1,/dev/sdb1 root=/dev/md0 |
Says to assemble /dev/md0 from dev/sda1 /dev/sdb1 and use it as root.
You don't have an md0.
|
Yes, and that's why I'm using UUID now.
| NeddySeagoon wrote: | artvs,
How did you make your initrd? |
first time genkernell all
second time genkernel --mdadm --install initramfs
I think that namely initrd loads the root and /usr in read-only mode. |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1666
|
| Posted: Mon Apr 08, 2024 12:58 pm Post subject: |
|
|
| artvs wrote: | | Code: |
cat /etc/fstab
#<fs> <mountpoint> <type> <opts> <dump/pass>
UUID=741f0d48-c197-1d16-cb20-1669f728008a / xfs rw,noatime 0 1
#UUID=6a01b59d-ae3c-4d14-92f7-ae3aaa479e50 / xfs rw,noatime 0 1
...
|
blkid (running from Live CD):
| Code: |
...
/dev/sdb1: UUID="741f0d48-c197-1d16-cb20-1669f728008a" TYPE="linux_raid_member"
...
/dev/md126: UUID="6a01b59d-ae3c-4d14-92f7-ae3aaa479e50" BLOCK_SIZE="512" TYPE="xfs"
...
|
|
In order for the rootfs to remount to rw, the correct fstab entry must match (which it appears to be pointing to the wrong value).
Then, the /etc/init.d/root service runs mount -n -o remount,rw /
| artvs wrote: | | And I have lots of errors: can't exec /etc/init.d/mtab - no such file or directory |
This is critical as they are the services which remount rootfs and /usr read-write as well as mount the supplementary file systems.
What does namei -l /etc/init.d/{mtab,root} (from the booted system, not live env) say?
Try to solve this above all others.
Edit: also from the booted system, what does cat /proc/self/mounts say? |
|
| Back to top |
|
|
artvs
n00b
Joined: 01 Apr 2024
Posts: 19
|
| Posted: Mon Apr 08, 2024 3:29 pm Post subject: |
|
|
| grknight wrote: |
What does namei -l /etc/init.d/{mtab,root} (from the booted system, not live env) say?
Try to solve this above all others.
|
Thank you, you've saved me several years of life.
Those files were missing. It seems I've removed them using emerge --depclean. Previously, this command always executed with the --ask option by default 
What I did:
| Code: |
wget https://distfiles.gentoo.org/releases/amd64/autobuilds/20240324T164906Z/stage3-amd64-openrc-20240324T164906Z.tar.xz
tar xpf stage3* --xattrs -C /
reboot
|
I didn't consider that tar would overwrite my /etc/fstab.
And everything (well, almost) worked - the services started, except for mdadm.
That is, my root mounted in rw mode!
sshd started and I was even able to connect to the server, but for some reason, the password for root doesn't work
At the very least, I'll try running syslog-ng to see the error log.
| grknight wrote: |
Edit: also from the booted system, what does cat /proc/self/mounts say? |
Now I can only place screenshot here, because have only iKVM access to the booted system.
https://paste.pics/QPKES
/md5.../md7 was mounted manually
If I restore the fstab back, regardless of the specified UUID for root, I still get the same errors for commands from /etc/init.d/.
And root is mount read-only.
Can it happens because of metadata 0.9?
P.S.: syslog-ng can not start because error in code |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1666
|
| Posted: Mon Apr 08, 2024 3:50 pm Post subject: |
|
|
| artvs wrote: | | sshd started and I was even able to connect to the server, but for some reason, the password for root doesn't work |
The default of modern sshd is to deny all root access directly. This is a security feature. Better to sign in as a user then become root later with su -l |
|
| Back to top |
|
|
artvs
n00b
Joined: 01 Apr 2024
Posts: 19
|
| Posted: Mon Apr 08, 2024 4:25 pm Post subject: |
|
|
| grknight wrote: | | artvs wrote: | | sshd started and I was even able to connect to the server, but for some reason, the password for root doesn't work |
The default of modern sshd is to deny all root access directly. This is a security feature. Better to sign in as a user then become root later with su -l |
Thanks a lot.
So. With empty fstab I can somewhat start system (without mdadm and syslogs-ng. cause latest have error in config file.
| Code: |
log { source(src); destination(console_all); };
|
command not found
there is cat /proc/self/mounts
| Code: |
cat /proc/self/mounts
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
none /run tmpfs rw,nosuid,nodev,relatime,mode=755,inode64 0 0
udev /dev devtmpfs rw,nosuid,noexec,relatime,size=10240k,nr_inodes=2043406,mode=755,inode64 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,inode64 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
/dev/md1 / xfs rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
none /sys/fs/cgroup cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
|
|
|
| Back to top |
|
|
artvs
n00b
Joined: 01 Apr 2024
Posts: 19
|
| Posted: Mon Apr 08, 2024 4:40 pm Post subject: |
|
|
./mountall
(mounts all devices by UUUD except root, cause it is already here)
/etc/init.d/mdadm start - success
so, real question is:
how to start mdadm automatically with empty fstab
or
what to write into the fstab? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54272
Location: 56N 3W
|
| Posted: Mon Apr 08, 2024 4:54 pm Post subject: |
|
|
artvs,
| cat /etc/fstab: |
#<fs> <mountpoint> <type> <opts> <dump/pass>
UUID=741f0d48-c197-1d16-cb20-1669f728008a / xfs rw,noatime 0 1
#UUID=6a01b59d-ae3c-4d14-92f7-ae3aaa479e50 / xfs rw,noatime 0 1
UUID=837d5c37-1b23-4d64-a32e-bfea6d19f92d /tmp xfs rw 0 0
UUID=e2de3314-c5b1-403b-85c6-4dc7d7de224e /usr xfs rw 0 1
UUID=813d60e7-6419-4fd4-8fdf-9eca7b762856 /var xfs rw 0 2
UUID=f70c0512-e349-4a6b-9b3c-4c1706684365 /home xfs rw 0 0 |
was what you started with.
Use that but check the UUIDs, Set passno to 0 except for root.
mdadm will use /etc/mdadm.conf to start your raid sets. See
The initrd must start some though, or root would not exist.
mdahm has to run before localmount, so that the raid sets are there when mount does its thing. OpenRC takes care of that.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
artvs
n00b
Joined: 01 Apr 2024
Posts: 19
|
| Posted: Mon Apr 08, 2024 9:46 pm Post subject: |
|
|
All the bad stuff (read-only, can not exec /etc/init.d/ ) happens when I add the /usr partition to fstab.
Now my maximally working fstab is as follows:
| Code: |
cat /etc/fstab
#<fs> <mountpoint> <type> <opts> <dump/pass>
UUID=741f0d48-c197-1d16-cb20-1669f728008a / xfs rw,noatime 0 1
UUID=813d60e7-6419-4fd4-8fdf-9eca7b762856 /var xfs rw 0 0
#UUID=e2de3314-c5b1-403b-85c6-4dc7d7de224e /usr xfs rw 0 0
UUID=f70c0512-e349-4a6b-9b3c-4c1706684365 /home xfs rw 0 0
UUID=837d5c37-1b23-4d64-a32e-bfea6d19f92d /tmp xfs rw 0 0
|
I don’t think I’m confusing the UUID for /usr because I copied it, for example, from findmnt. Perhaps the issue is some other settings.
| Code: |
findmnt -o TARGET,SOURCE,FSTYPE,UUID
TARGET SOURCE FSTYPE UUID
/ /dev/md127 xfs 6a01b59d-ae3c-4d14-92f7-ae3aaa479e50
├─/proc proc proc
│ └─/proc/sys/fs/binfmt_misc binfmt_misc binfmt_misc
├─/run none tmpfs
├─/dev udev devtmpfs
│ ├─/dev/pts devpts devpts
│ ├─/dev/shm tmpfs tmpfs
│ └─/dev/mqueue mqueue mqueue
├─/sys sysfs sysfs
│ ├─/sys/kernel/security securityfs securityfs
│ ├─/sys/kernel/debug debugfs debugfs
│ ├─/sys/fs/selinux selinuxfs selinuxfs
│ ├─/sys/fs/pstore pstore pstore
│ └─/sys/fs/cgroup none cgroup2
├─/var /dev/md126 xfs 813d60e7-6419-4fd4-8fdf-9eca7b762856
├─/home /dev/md8 xfs f70c0512-e349-4a6b-9b3c-4c1706684365
├─/tmp /dev/md5 xfs 837d5c37-1b23-4d64-a32e-bfea6d19f92d
└─/usr /dev/md6 xfs e2de3314-c5b1-403b-85c6-4dc7d7de224e
|
It's strange that the device numbers for root and /var have changed, while they remain the same for the others.
| Code: |
mdadm --detail --scan
ARRAY /dev/md127 metadata=0.90 UUID=741f0d48:c1971d16:cb201669:f728008a
ARRAY /dev/md6 metadata=1.2 name=livecd:6 UUID=8a59ac74:000cc86e:0b713127:5d9ad5ed
ARRAY /dev/md5 metadata=1.2 name=livecd:5 UUID=8977e19e:ec19b8c3:0456458d:e9daf960
ARRAY /dev/md126 metadata=1.2 name=livecd:7 UUID=9d525d9f:336864c0:27211b82:ef567804
ARRAY /dev/md8 metadata=1.2 name=fairseo.ru:8 UUID=a09fab88:b0b841ff:fd57d3e4:ea81f84c
|
I've regenerated the initramfs just in case...
| NeddySeagoon wrote: | artvs,
| cat /etc/fstab: |
#<fs> <mountpoint> <type> <opts> <dump/pass>
UUID=741f0d48-c197-1d16-cb20-1669f728008a / xfs rw,noatime 0 1
#UUID=6a01b59d-ae3c-4d14-92f7-ae3aaa479e50 / xfs rw,noatime 0 1
UUID=837d5c37-1b23-4d64-a32e-bfea6d19f92d /tmp xfs rw 0 0
UUID=e2de3314-c5b1-403b-85c6-4dc7d7de224e /usr xfs rw 0 1
UUID=813d60e7-6419-4fd4-8fdf-9eca7b762856 /var xfs rw 0 2
UUID=f70c0512-e349-4a6b-9b3c-4c1706684365 /home xfs rw 0 0 |
was what you started with.
Use that but check the UUIDs, Set passno to 0 except for root.
mdadm will use /etc/mdadm.conf to start your raid sets. See
The initrd must start some though, or root would not exist.
mdahm has to run before localmount, so that the raid sets are there when mount does its thing. OpenRC takes care of that. |
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54272
Location: 56N 3W
|
| Posted: Tue Apr 09, 2024 12:26 pm Post subject: |
|
|
artvs,
I suspect that your working /usr is a directory on /, not a separate filesystem, or its mounted by the initrd.
Do | Code: | mkdir /tmp/usr
mount -o ro UUID=e2de3314-c5b1-403b-85c6-4dc7d7de224e /tmp/usr |
Readonly so bad things don't happen, although, mount should shout at you if the filesystem is already mounted.
Compare a few file datestamps in /usr with the same files in /tmp/usr.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
artvs
n00b
Joined: 01 Apr 2024
Posts: 19
|
| Posted: Tue Apr 09, 2024 1:45 pm Post subject: |
|
|
I think all the trouble starts when there is confusion between a split-usr and merged-usr profile.
So /usr from the root device is working (merged), but /usr from the other device is not, because it remains split.
Now, I've tried to merge /usr from the old device using 'merge-usr'. (old device is manually mounted via the same UUID)
And at this moment, command emerge --emptytree @world is being executed.
I've already noticed several error messages in the acct-user category. So, I shall also need to try and recover these packages.
Can the /usr folder on the root device prevent the mounting of the /usr folder from the old device? |
|
| Back to top |
|
|
artvs
n00b
Joined: 01 Apr 2024
Posts: 19
|
| Posted: Tue Apr 09, 2024 2:32 pm Post subject: |
|
|
SOLVED!!!
I have finally completed the migration from Gentoo 3.3.18 profile 17.0 split-usr to Gentoo 6.6.21 profile 23 merged-usr!
All that's left is to configure the custom software.
Should I change topic name?
Thanks a lot! |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54272
Location: 56N 3W
|
| Posted: Tue Apr 09, 2024 2:42 pm Post subject: |
|
|
artvs,
You may add [solved] to the title of the opening post if you wish.
Take care to keep the title less than 80 characters.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
