Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[Solved] mdadm raid 0
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Sun Jul 21, 2019 9:26 am    Post subject: [Solved] mdadm raid 0 Reply with quote

Hello.

I'd like to install gentoo with software raid0.

There are my steps. is there a miss or a mistake?



Step 1. Boot a debian image

Disks prepare with cfdisk util.

Code:

/dev/sda disk label type dos
/dev/sdb disk label type dos

/dev/sda1 BIOS-Boot partition size: 2mb Type: no filesystem Mount point: none
/dev/sda2 /Boot partition     size: 512mb Type: Linux type ( EXT2) Mount point: /Boot
/dev/sda3 /Root partition     size: the rest of the disk type Linux Raid Autodetect" (fd) Mount point: /
/dev/sdb1 /Root partition     size: the entire hard disk space type Linux Raid Autodetect" (fd) Mount point: /


Step 2. Creation of RAID0 devices with file systems.

Code:


modprobe raid0
mdadm --create /dev/md/Gentoo_Raid --level=0 --raid-devices=2 /dev/sda3 /dev/sdb1
mkfs.ext4 /dev/md/Gentoo_Raid
mdadm --detail --scan > /etc/mdadm.conf


Step 3. Installing base gentoo system and kernel with raid support

Code:

proceed  with the standard installation.....
emerge mdadm
rc-update add mdraid boot

[*] Device Drivers  --->
    <*> Multiple devices driver support (RAID and LVM)
        <*> RAID support
            [*] Autodetect RAID arrays during kernel boot

            If you want to combine multiple disks or partitions to one (bigger) device:
                <*> Linear (append) mode

mdadm --detail --scan > /etc/mdadm.conf


Step 4. Installing Grub2 as a bootloader.

Code:

emerge sys-boot/grub
grub2-install /dev/sda2
grub2-mkconfig -o /boot/grub/grub.cfg

nano -w /boot/grub/grub.cfg

GRUB_CMDLINE_LINUX_DEFAULT="domdadm"


proceed with the standard installation


Last edited by Palme on Fri Aug 02, 2019 12:11 pm; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Sun Jul 21, 2019 12:22 pm    Post subject: Reply with quote

Palme,

There are a few traps for the unwary. For
Code:
[*] Autodetect RAID arrays during kernel boot

to work you must use raid metadata version 0.90. That's not the default with mdadm.

I have
Code:
# mdadm -E /dev/sda5
/dev/sda5:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 5e3cadd4:cfd2665d:96901ac7:6d8f5a5d
  Creation Time : Sat Apr 11 20:30:16 2009
...

Notice the Version : 0.90.00. If you have any other version, its probably 1.2, you have two choices.

1) make an initrd that assembles your raid
2) remake the raid set with version 0.90 which is destructive to your data in the raid set.

The initrd option is encouraged as raid auto assemble is depreciated.
That means that it will be removed form the kernel one day.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Mon Jul 22, 2019 8:01 am    Post subject: Reply with quote

if I am understanding it correctly

According to

https://raid.wiki.kernel.org/index.php/RAID_superblock_formats

https://wiki.gentoo.org/wiki/Gentoo_installation_tips_and_tricks

https://wiki.gentoo.org/wiki/Complete_Handbook/Software_RAID

there are two metadata versions version-0.90" and "version-1" Superblock formats
does mdadm provide both versions?

i have to use The version-0.90 Superblock Format to Create the raid without extra initrd etc..

and this can be set with this string in the command

--metadata=0.90

that would look like that: while creating the array


mdadm --create --verbose /dev/md1 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb1

is it theoretically correct? :?:
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Mon Jul 22, 2019 8:23 am    Post subject: Reply with quote

Palme,

As you say, there are two raid metadata versions.
mdadm works with both.

Code:
mdadm --create --verbose /dev/md1 --level=1 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb1

Is correct for a raid1 but you have been talking about raid0, so its not what you want, quite.

This does not get around raid auto assemble being depreciated.
Whatever metadata version you choose, you way need an initrd for root on raid.
You can do the initrd today, or postpone it until raid auto assemble is removed from the kernel.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Mon Jul 22, 2019 12:29 pm    Post subject: Reply with quote

oh my mistake i mean of course raid0



Gentoo_Raid0 ist the name /label of the Array

well i´d say I would wait until raid auto assemble is removed from the kernel to keep it Simpel and to reduce error sources since it will be my first installation with mdadm

Can someone please explain this command

what does mknod / dev / md1 b 9 1 stand for ? or rather

Code:
mknod /dev/md1 b 9 1
root #mknod /dev/md2 b 9 2
root #mknod /dev/md3 b 9 3

as shown here https://wiki.gentoo.org/wiki/Gentoo_installation_tips_and_tricks

the Command to Create the Array should it look like this right?

Code:
mdadm --create --verbose /dev/Gentoo_Raid0  --level=0 --raid-devices=2 --metadata=0.90 /dev/sda3 /dev/sdb1

thanks
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Mon Jul 22, 2019 3:37 pm    Post subject: Reply with quote

Palme,

Your create command is correct.

There are two sorts of raid0.
Linear, where mdadm appends all the elements together to make one big volume.
Interleaved, where chunks are written to each raid element in turn.
The latter is faster, as reads and writes can take place to every element at the same time.

RAID is an abbreviation for Redundant Array of Inexpensive Disks. With level0, its just AID :)
There is no redundancy.

mknod is the command used to manually make device special files. That's /dev entries.
Code:
mknod /dev/md1 b 9 1

Says to make the device special file /dev/md1 which is a block device with kernel major and minor numbers 9 1.
The kernel knows devices my their major and minor numbers.
You should not need the mknod steps. You will be using devtmpfs in the kernel, so your /dev/md* entries should just appear.

Don't use /dev/Gentoo_Raid0. You will get confused. Choose a /dev/mdX where X= 0..127
The Gentoo_Raid0 will not persist across reboots but you can write a udev rule to do renaming if you wish.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Wed Jul 24, 2019 4:40 pm    Post subject: Reply with quote

I successfully created a RAID by utilizing mdadm. However, after the grub menu mdadm seems to doesn't mount the raid Array

outputs from chroot

dmesg

http://dpaste.com/13M9BR7

mdadm --detail /dev/md0
Code:

mdadm --detail /dev/md0
/dev/md0:
           Version : 0.90
     Creation Time : Tue Jul 23 09:45:09 2019
        Raid Level : raid0
        Array Size : 3906500608 (3725.53 GiB 4000.26 GB)
      Raid Devices : 2
     Total Devices : 2
   Preferred Minor : 0
       Persistence : Superblock is persistent

       Update Time : Tue Jul 23 09:45:09 2019
             State : clean
    Active Devices : 2
   Working Devices : 2
    Failed Devices : 0
     Spare Devices : 0

        Chunk Size : 512K

Consistency Policy : none

              UUID : 8e986b98:5cdef20d:776c2c25:004bd7b2 (local to host rescue)
            Events : 0.1

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       1       8       17        1      active sync   /dev/sdb1


mdadm.conf

Code:

# mdadm configuration file
#
# mdadm will function properly without the use of a configuration file,
# but this file is useful for keeping track of arrays and member disks.
# In general, a mdadm.conf file is created, and updated, after arrays
# are created. This is the opposite behavior of /etc/raidtab which is
# created prior to array construction.
#
#
# the config file takes two types of lines:
#
#   DEVICE lines specify a list of devices of where to look for
#     potential member disks
#
#   ARRAY lines specify information about how to identify arrays so
#     so that they can be activated
#
# You can have more than one device line and use wild cards. The first
# example includes SCSI the first partition of SCSI disks /dev/sdb,
# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
# line looks for array slices on IDE disks.
#
#DEVICE /dev/sd[bcdjkl]1
#DEVICE /dev/hda1 /dev/hdb1
#
# If you mount devfs on /dev, then a suitable way to list all devices is:
#DEVICE /dev/discs/*/*
#
#
# The AUTO line can control which arrays get assembled by auto-assembly,
# meaing either "mdadm -As" when there are no 'ARRAY' lines in this file,
# or "mdadm --incremental" when the array found is not listed in this file.
# By default, all arrays that are found are assembled.
# If you want to ignore all DDF arrays (maybe they are managed by dmraid),
# and only assemble 1.x arrays if which are marked for 'this' homehost,
# but assemble all others, then use
#AUTO -ddf homehost -1.x +all
#
# ARRAY lines specify an array to assemble and a method of identification.
# Arrays can currently be identified by using a UUID, superblock minor number,
# or a listing of devices.
#
#   super-minor is usually the minor number of the metadevice
#   UUID is the Universally Unique Identifier for the array
# Each can be obtained using
#
#    mdadm -D <md>
#
#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
#ARRAY /dev/md1 super-minor=1
#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
#
# ARRAY lines can also specify a "spare-group" for each array.  mdadm --monitor
# will then move a spare between arrays in a spare-group if one array has a failed
# drive but no spare
#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
#
# When used in --follow (aka --monitor) mode, mdadm needs a
# mail address and/or a program.  This can be given with "mailaddr"
# and "program" lines to that monitoring can be started using
#    mdadm --follow --scan & echo $! > /run/mdadm/mon.pid
# If the lines are not found, mdadm will exit quietly
#MAILADDR root@mydomain.tld
#PROGRAM /usr/sbin/handle-mdadm-events


My fstab:
Code:

#LABEL=boot      /boot      ext4      noauto,noatime   1 2
#UUID=58e72203-57d1-4497-81ad-97655bd56494      /      ext4      noatime      0 1
#LABEL=swap      none      swap      sw      0 0
#/dev/cdrom      /mnt/cdrom   auto      noauto,ro   0 0
/dev/sda2      /boot      ext2      defaults      0      2
/dev/md0      /      ext4      defaults      0      1


blkid
Code:

/dev/loop0: UUID="40c4ea95-0ecc-4c51-9f3e-e49d8f62f160" TYPE="ext2"
/dev/sda2: LABEL="Boot" UUID="e84c3ca8-0cec-4303-af63-7604b1e71824" TYPE="ext2" PARTUUID="0f90f33d-02"
/dev/sda3: UUID="8e986b98-5cde-f20d-776c-2c25004bd7b2" TYPE="linux_raid_member" PARTUUID="0f90f33d-03"
/dev/sdb1: UUID="8e986b98-5cde-f20d-776c-2c25004bd7b2" TYPE="linux_raid_member" PARTUUID="50596596-01"
/dev/md0: LABEL="Gentoo" UUID="e0a7af0f-51b8-48d6-b30d-3c97a2049f96" TYPE="ext4"
/dev/sda1: PARTUUID="0f90f33d-01"


lsblk -f

Code:

NAME FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0
     ext2         40c4ea95-0ecc-4c51-9f3e-e49d8f62f160
sda
|-sda1
|
|-sda2
|    ext2   Boot  e84c3ca8-0cec-4303-af63-7604b1e71824  458,9M     4% /boot
`-sda3
     linux_       8e986b98-5cde-f20d-776c-2c25004bd7b2
  `-md0
     ext4   Gentoo
                  e0a7af0f-51b8-48d6-b30d-3c97a2049f96    3,4T     0% /
sdb
`-sdb1
     linux_       8e986b98-5cde-f20d-776c-2c25004bd7b2
  `-md0
     ext4   Gentoo
                  e0a7af0f-51b8-48d6-b30d-3c97a2049f96    3,4T     0% /


thanks
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Wed Jul 24, 2019 8:27 pm    Post subject: Reply with quote

Palme,

It all looks good. You should have /dev/md0 for your raid.

mdadm.conf is of no interest. Its all comments.
Also, as it is located on the root filesystem it cannot be used to assemble md0, since md0 needs to be assembled to read the filesystem where mdadm.conf is located.
Thats why you have an initrd or use Raid Autoassemble in the kernel.

Likewise, /etc/fstab is not read to find the location of the root filesystem.
The location of the root filesystem must be known, to mount the root filesystem to read /etc/fstab.

There are lots of logical loops like this in the boot process. The location of the root filesystem is given on the kernel command line.
That's what the root= tells the kernel.

Please post your grub.cfg, so we can see what you are telling the kernel.

I suspect that you get a kernel panic message about ... unable to mount rootfs unknown-block(X,Y)
What are the numbers X and Y?

It may say can't find root block device in
<list of detected block devices>
If the list is empty in will just say can't find root block device in. Which is a bit misleading.

Your raid set may get renumbered when its assembled. Just go with it.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Thu Jul 25, 2019 7:45 am    Post subject: Reply with quote

Hi

Thank you for your help. I greatly appreciate it.

grub.cfg

Code:


#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid09
insmod ext2
set root='mduuid/8e986b985cdef20d776c2c25004bd7b2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint='mduuid/8e986b985cdef20d776c2c25004bd7b2'  e0a7af0f-51b8-48d6-b30d-3c97a2049f96
else
  search --no-floppy --fs-uuid --set=root e0a7af0f-51b8-48d6-b30d-3c97a2049f96
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=de_DE@euro
  insmod gettext
fi
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Gentoo GNU/Linux' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e0a7af0f-51b8-48d6-b30d-3c97a2049f96' {
   load_video
   if [ "x$grub_platform" = xefi ]; then
      set gfxpayload=keep
   fi
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='hd0,msdos2'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  e84c3ca8-0cec-4303-af63-7604b1e71824
   else
     search --no-floppy --fs-uuid --set=root e84c3ca8-0cec-4303-af63-7604b1e71824
   fi
   echo   'Linux 4.19.57-gentoo wird geladen ...'
   linux   /vmlinuz-4.19.57-gentoo root=/dev/sda2 ro 
}
submenu 'Erweiterte Optionen für Gentoo GNU/Linux' $menuentry_id_option 'gnulinux-advanced-e0a7af0f-51b8-48d6-b30d-3c97a2049f96' {
   menuentry 'Gentoo GNU/Linux, mit Linux 4.19.57-gentoo' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.57-gentoo-advanced-e0a7af0f-51b8-48d6-b30d-3c97a2049f96' {
      load_video
      if [ "x$grub_platform" = xefi ]; then
         set gfxpayload=keep
      fi
      insmod gzio
      insmod part_msdos
      insmod ext2
      set root='hd0,msdos2'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  e84c3ca8-0cec-4303-af63-7604b1e71824
      else
        search --no-floppy --fs-uuid --set=root e84c3ca8-0cec-4303-af63-7604b1e71824
      fi
      echo   'Linux 4.19.57-gentoo wird geladen ...'
      linux   /vmlinuz-4.19.57-gentoo root=/dev/sda2 ro 
   }
   menuentry 'Gentoo GNU/Linux, mit Linux 4.19.57-gentoo (Wiederherstellungsmodus)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.57-gentoo-recovery-e0a7af0f-51b8-48d6-b30d-3c97a2049f96' {
      load_video
      if [ "x$grub_platform" = xefi ]; then
         set gfxpayload=keep
      fi
      insmod gzio
      insmod part_msdos
      insmod ext2
      set root='hd0,msdos2'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  e84c3ca8-0cec-4303-af63-7604b1e71824
      else
        search --no-floppy --fs-uuid --set=root e84c3ca8-0cec-4303-af63-7604b1e71824
      fi
      echo   'Linux 4.19.57-gentoo wird geladen ...'
      linux   /vmlinuz-4.19.57-gentoo root=/dev/sda2 ro single
   }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Thu Jul 25, 2019 8:47 pm    Post subject: Reply with quote

Palme,

Code:
   linux   /vmlinuz-4.19.57-gentoo root=/dev/sda2 ro

Everywhere the above line appears, the root=/dev/sda2 part needs to read root=/dev/md0
You have root on raid0 on /dev/md0, not on /dev/sda2

You can test this. Grub can edit the in memory grub.cfg file before continuing the boot process.
Choose the menu entry to boot but press 'e', not the enter key.
Follow the on screen instructions to make the edit, then boot.

What happens now?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Fri Jul 26, 2019 12:11 pm    Post subject: Reply with quote

Hi

i Deleted the old grub.cfg and created a new grub.cfg

Code:


grub-mkconfig -o /boot/grub/grub.cfg


Now all root= are set to
Code:

root=/dev/md0


cleared the current dmesg buffer.
Code:

 dmesg -c


then I tried to boot from hdd however im still Unable to connect to host via ssh...

so Rebooted in the rescue sys and chroot to the system
Code:

mkdir -p /mnt/gentoo/boot
 mdadm --assemble --auto=yes /dev/md0 /dev/sda3 /dev/sdb1
mount /dev/md0 /mnt/gentoo
mount /dev/sda2 /mnt/gentoo/boot
mount  -l
mount --types proc /proc /mnt/gentoo/proc
mount --rbind /sys /mnt/gentoo/sys
mount --make-rslave /mnt/gentoo/sys
mount --rbind /dev /mnt/gentoo/dev
mount --make-rslave /mnt/gentoo/dev
 test -L /dev/shm && rm /dev/shm && mkdir /dev/shm
mount --types tmpfs --options nosuid,nodev,noexec shm /dev/shm
chmod 1777 /dev/shm
chroot /mnt/gentoo /bin/bash
source /etc/profile
export PS1="(chroot) ${PS1}"


dmesg -T
http://dpaste.com/0E83QJ8

cat /proc/mdstat
Code:
Personalities : [raid1] [raid0]
md0 : active raid0 sda3[0] sdb1[1]
      3906500608 blocks 512k chunks

unused devices: <none>


rc-update -v show
Code:

               agetty |
               binfmt | boot
             bootlogd |
             bootmisc | boot
         busybox-ntpd |
     busybox-watchdog |
              cgroups |                                 sysinit
          consolefont |
                devfs |                                 sysinit
               dhcpcd |
                dmesg |                                 sysinit
                 fsck | boot
             hostname | boot
              hwclock | boot
            ip6tables |
             iptables |
              keymaps | boot
            killprocs |                        shutdown
    kmod-static-nodes |                                 sysinit
                local |      default nonetwork
           localmount | boot
             loopback | boot
                mdadm |
               mdraid | boot
              modules | boot
             mount-ro |                        shutdown
                 mtab | boot
           net-online |
               net.lo |
             netmount |      default
              numlock |
     opentmpfiles-dev |                                 sysinit
   opentmpfiles-setup | boot
              osclock |
              pciparm |
               procfs | boot
            pydoc-2.7 |
            pydoc-3.6 |
                 root | boot
               rsyncd |
             runsvdir |
            s6-svscan |
         save-keymaps | boot
    save-termencoding | boot
            savecache |                        shutdown
                 sshd |      default
                 swap | boot
              swclock |
               sysctl | boot
                sysfs |                                 sysinit
            syslog-ng |      default
         termencoding | boot
                 udev |                                 sysinit
          udev-settle |
         udev-trigger |                                 sysinit
              urandom | boot


Code:
cat /etc/ssh/sshd_config
#       $OpenBSD: sshd_config,v 1.103 2018/04/09 20:41:22 tj Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options override the
# default value.

Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key

# Ciphers and keying
#RekeyLimit default none

# Logging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin prohibit-password
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#PubkeyAuthentication yes

# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
# but this is overridden so installations will only check .ssh/authorized_keys
#AuthorizedKeysFile     .ssh/authorized_keys

#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
PrintMotd no
PrintLastLog no
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none

# no default banner path
#Banner none

# override default of no subsystems
Subsystem       sftp    /usr/lib64/misc/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#       X11Forwarding no
#       AllowTcpForwarding no
#       PermitTTY no
#       ForceCommand cvs server

# Allow client to pass locale environment variables. #367017
AcceptEnv LANG LC_ALL LC_COLLATE LC_CTYPE LC_MESSAGES LC_MONETARY LC_NUMERIC LC_TIME LANGUAGE LC_ADDRESS LC_IDENTIFICATION LC_MEASUREMENT LC_NAME LC_PAPER LC_TELEPHONE

# Allow client to pass COLORTERM to match TERM. #658540
AcceptEnv COLORTERM
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Fri Jul 26, 2019 10:24 pm    Post subject: Reply with quote

Palme,

Two things
Code:
rc-update -v show
is missing an net.eth0 entry in the default runlevel.
eth0 may still have started.

look at
Code:
ifconfig
on the console of your Gentoo.
Is your wired interface listed with an IP address?
What is the IP address?
I get.
Code:
$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.100.20  netmask 255.255.255.0  broadcast 192.168.100.255


If the address is in the form 169.254.x.y, it indicates that the system cannot reach a dhcp server.
Did you install dhcpcd or something like that?
Code:
busybox udhcpd eth0
may get you going.

You spotted
Code:
#PermitRootLogin prohibit-password
PermitRootLogin yes
Good
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Sat Jul 27, 2019 9:31 am    Post subject: Reply with quote

NeddySeagoon wrote:
Palme,
Did you install dhcpcd or something like that?


yes, this are all packages i directly installed

cat /var/lib/portage/world
Code:

app-admin/syslog-ng
app-portage/cpuid2cpuflags
app-portage/mirrorselect
net-misc/dhcpcd
net-misc/netifrc
sys-apps/pciutils
sys-apps/portage
sys-boot/grub:2
sys-fs/mdadm
sys-kernel/gentoo-sources


these are all installed packages

emerge world -ep

Code:


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] dev-lang/python-exec-2.4.6
[ebuild   R    ] virtual/libintl-0-r2
[ebuild   R    ] sys-libs/ncurses-6.1_p20181020
[ebuild   R    ] app-arch/bzip2-1.0.6-r11
[ebuild   R    ] sys-devel/gnuconfig-20170101
[ebuild   R    ] sys-apps/gentoo-functions-0.12
[ebuild   R    ] virtual/libiconv-0-r2
[ebuild   R    ] app-misc/c_rehash-1.7-r1
[ebuild   R    ] app-misc/mime-types-9
[ebuild   R    ] app-arch/gzip-1.9
[ebuild   R    ] sys-apps/debianutils-4.8.3
[ebuild   R    ] app-crypt/openpgp-keys-gentoo-release-20190427
[ebuild   R    ] sys-apps/install-xattr-0.5
[ebuild   R    ] net-libs/libmnl-1.0.4
[ebuild   R    ] app-misc/editor-wrapper-4
[ebuild   R    ] app-text/manpager-1
[ebuild   R    ] sys-apps/opentmpfiles-0.2
[ebuild   R    ] sys-apps/which-2.21
[ebuild   R    ] sys-apps/baselayout-2.6-r1
[ebuild   R    ] app-text/sgml-common-0.6.3-r6
[ebuild   R    ] sys-apps/tcp-wrappers-7.6.22-r1
[ebuild   R    ] sys-devel/automake-wrapper-11
[ebuild   R    ] sys-devel/autoconf-wrapper-13-r1
[ebuild   R    ] net-analyzer/netselect-0.4
[ebuild   R    ] dev-util/pkgconf-1.5.4
[ebuild   R    ] dev-util/gperf-3.1
[ebuild   R    ] app-portage/cpuid2cpuflags-5
[ebuild   R    ] sys-libs/timezone-data-2019a
[ebuild   R    ] sys-devel/gcc-config-2.0
[ebuild   R    ] sys-devel/binutils-config-5-r4
[ebuild   R    ] virtual/tmpfiles-0
[ebuild   R    ] virtual/pkgconfig-1
[ebuild   R    ] app-arch/unzip-6.0_p21-r2
[ebuild   R    ] sys-libs/readline-7.0_p5
[ebuild   R    ] sys-libs/e2fsprogs-libs-1.45.2
[ebuild   R    ] sys-process/procps-3.3.15-r1
[ebuild   R    ] app-shells/bash-4.4_p23-r1
[ebuild   R    ] virtual/os-headers-0
[ebuild   R    ] sys-apps/sysvinit-2.93
[ebuild   R    ] virtual/pam-0-r1
[ebuild   R    ] sys-apps/kbd-2.0.4
[ebuild   R    ] virtual/acl-0-r2
[ebuild   R    ] virtual/udev-217
[ebuild   R    ] sys-apps/hwids-20180917
[ebuild   R    ] sys-fs/udev-init-scripts-33
[ebuild   R    ] virtual/dev-manager-0-r2
[ebuild   R    ] net-misc/dhcpcd-7.1.1-r3
[ebuild   R    ] virtual/libffi-3.0.13-r1
[ebuild   R    ] virtual/man-0-r2
[ebuild   R    ] sys-apps/man-pages-posix-2013a
[ebuild   R    ] sys-apps/man-pages-5.00
[ebuild   R    ] app-eselect/eselect-python-20171204
[ebuild   R    ] virtual/shadow-0
[ebuild   R    ] net-misc/netifrc-0.5.1
[ebuild   R    ] app-eselect/eselect-pinentry-0.7
[ebuild   R    ] virtual/perl-ExtUtils-MakeMaker-7.340.0-r1
[ebuild   R    ] app-text/docbook-xsl-stylesheets-1.79.1-r2
[ebuild   R    ] virtual/yacc-0
[ebuild   R    ] app-text/docbook-xml-dtd-4.1.2-r6
[ebuild   R    ] virtual/perl-Parse-CPAN-Meta-2.150.10-r2
[ebuild   R    ] virtual/perl-File-Temp-0.230.400-r5
[ebuild   R    ] virtual/perl-CPAN-Meta-YAML-0.18.0-r4
[ebuild   R    ] virtual/perl-Test-Harness-3.420.0-r1
[ebuild   R    ] virtual/perl-File-Spec-3.740.0
[ebuild   R    ] virtual/perl-Data-Dumper-2.170.0
[ebuild   R    ] virtual/python-ipaddress-1.0-r1
[ebuild   R    ] app-admin/perl-cleaner-2.27
[ebuild   R    ] virtual/perl-version-0.992.300
[ebuild   R    ] virtual/perl-podlators-4.100.0
[ebuild   R    ] virtual/perl-Text-ParseWords-3.300.0-r5
[ebuild   R    ] virtual/perl-Perl-OSType-1.10.0-r2
[ebuild   R    ] virtual/perl-Module-Metadata-1.0.33-r1
[ebuild   R    ] virtual/perl-Getopt-Long-2.500.0-r1
[ebuild   R    ] virtual/perl-ExtUtils-ParseXS-3.390.0
[ebuild   R    ] virtual/perl-ExtUtils-Manifest-1.700.0-r5
[ebuild   R    ] virtual/perl-ExtUtils-Install-2.140.0-r1
[ebuild   R    ] virtual/perl-ExtUtils-CBuilder-0.280.230
[ebuild   R    ] virtual/perl-CPAN-Meta-2.150.10-r2
[ebuild   R    ] virtual/libelf-3
[ebuild   R    ] virtual/python-enum34-2
[ebuild   R    ] virtual/libudev-232
[ebuild   R    ] app-arch/xz-utils-5.2.4-r2
[ebuild   R    ] sys-apps/net-tools-1.60_p20180626073013
[ebuild   R    ] app-portage/elt-patches-20170815
[ebuild   R    ] sys-devel/m4-1.4.18-r1
[ebuild   R    ] dev-libs/libltdl-2.4.6
[ebuild   R    ] sys-libs/zlib-1.2.11-r2
[ebuild   R    ] dev-libs/gmp-6.1.2
[ebuild   R    ] dev-libs/libunistring-0.9.10
[ebuild   R    ] dev-libs/npth-1.3
[ebuild   R    ] dev-libs/libpipeline-1.4.2
[ebuild   R    ] dev-libs/libffi-3.2.1
[ebuild   R    ] dev-libs/libpcre-8.42
[ebuild   R    ] sys-apps/kmod-25
[ebuild   R    ] sys-apps/file-5.36
[ebuild   R    ] sys-libs/cracklib-2.9.6-r2
[ebuild   R    ] dev-libs/mpfr-3.1.6
[ebuild   R    ] media-libs/freetype-2.9.1-r3
[ebuild   R    ] sys-apps/less-531
[ebuild   R    ] dev-libs/mpc-1.0.3
[ebuild   R    ] virtual/modutils-0
[ebuild   R    ] sys-apps/pciutils-3.5.6
[ebuild   R    ] virtual/pager-0
[ebuild   R    ] dev-python/setuptools-40.6.3
[ebuild   R    ] sys-apps/attr-2.4.47-r2
[ebuild   R    ] sys-devel/patch-2.7.6-r3
[ebuild   R    ] dev-libs/openssl-1.0.2r
[ebuild   R    ] sys-kernel/linux-headers-4.19
[ebuild   R    ] sys-libs/libseccomp-2.4.0
[ebuild   R    ] net-firewall/iptables-1.6.1-r3
[ebuild   R    ] sys-apps/busybox-1.29.3
[ebuild   R    ] sys-libs/libcap-2.26-r2
[ebuild   R    ] app-misc/pax-utils-1.2.3
[ebuild   R    ] net-misc/iputils-20180629
[ebuild   R    ] sys-apps/sandbox-2.13
[ebuild   R    ] sys-apps/util-linux-2.33.2
[ebuild   R    ] sys-fs/mdadm-4.1
[ebuild   R    ] dev-libs/libgpg-error-1.36
[ebuild   R    ] dev-libs/libassuan-2.5.1
[ebuild   R    ] dev-libs/libksba-1.3.5-r1
[ebuild   R    ] sys-devel/binutils-2.32-r1
[ebuild   R    ] sys-apps/sed-4.5
[ebuild   R    ] dev-libs/expat-2.2.7
[ebuild   R    ] sys-libs/db-5.3.28-r2
[ebuild   R    ] sys-libs/gdbm-1.13-r2
[ebuild   R    ] dev-lang/perl-5.28.2-r1
[ebuild   R    ] sys-apps/groff-1.22.3
[ebuild   R    ] sys-devel/autoconf-2.69-r4
[ebuild   R    ] dev-perl/Module-Build-0.422.400
[ebuild   R    ] dev-util/gtk-doc-am-1.25-r1
[ebuild   R    ] dev-perl/XML-Parser-2.440.0
[ebuild   R    ] dev-perl/libintl-perl-1.280.0
[ebuild   R    ] dev-perl/Unicode-EastAsianWidth-1.330.0-r1
[ebuild   R    ] dev-perl/Text-Unidecode-1.300.0
[ebuild   R    ] dev-perl/TermReadKey-2.370.0
[ebuild   R    ] dev-perl/Text-CharWidth-0.40.0-r1
[ebuild   R    ] perl-core/File-Temp-0.230.400-r1
[ebuild   R    ] virtual/perl-JSON-PP-2.970.10
[ebuild   R    ] dev-perl/SGMLSpm-1.1-r1
[ebuild   R    ] dev-perl/Text-WrapI18N-0.60.0-r1
[ebuild   R    ] dev-util/intltool-0.51.0-r2
[ebuild   R    ] dev-lang/python-3.6.5
[ebuild   R    ] app-misc/ca-certificates-20190110.3.43
[ebuild   R    ] dev-lang/python-2.7.15
[ebuild   R    ] dev-python/certifi-2018.4.16
[ebuild   R    ] dev-python/pyblake2-1.1.2
[ebuild   R    ] dev-python/pyxattr-0.6.0-r1
[ebuild   R    ] dev-python/bz2file-0.98
[ebuild   R    ] dev-python/six-1.12.0
[ebuild   R    ] dev-python/idna-2.5
[ebuild   R    ] dev-python/pyasn1-0.4.2
[ebuild   R    ] dev-python/asn1crypto-0.22.0
[ebuild   R    ] dev-python/ply-3.9
[ebuild   R    ] dev-python/chardet-3.0.4
[ebuild   R    ] dev-python/PySocks-1.6.7
[ebuild   R    ] dev-python/ipaddress-1.0.22
[ebuild   R    ] dev-python/enum34-1.1.6-r1
[ebuild   R    ] dev-python/pycparser-2.14
[ebuild   R    ] dev-python/cffi-1.11.4
[ebuild   R    ] dev-python/cryptography-2.6.1
[ebuild   R    ] dev-python/pyopenssl-19.0.0
[ebuild   R    ] dev-python/ndg-httpsclient-0.4.0
[ebuild   R    ] dev-python/urllib3-1.24.2
[ebuild   R    ] dev-python/requests-2.21.0-r1
[ebuild   R    ] dev-python/ssl-fetch-0.4
[ebuild   R    ] app-portage/gemato-14.1
[ebuild   R    ] sys-auth/pambase-20150213-r2
[ebuild   R    ] dev-libs/libgcrypt-1.8.3
[ebuild   R    ] app-admin/eselect-1.4.14
[ebuild   R    ] app-eselect/eselect-lib-bin-symlink-0.1.1
[ebuild   R    ] sys-libs/glibc-2.29-r2
[ebuild   R    ] virtual/libc-1
[ebuild   R    ] sys-apps/acl-2.2.52-r1
[ebuild   R    ] sys-apps/coreutils-8.30
[ebuild   R    ] sys-devel/make-4.2.1-r4
[ebuild   R    ] sys-apps/portage-2.3.66-r1
[ebuild   R    ] virtual/package-manager-1
[ebuild   R    ] net-dns/libidn2-2.1.1a-r1
[ebuild   R    ] sys-apps/openrc-0.41.2
[ebuild   R    ] virtual/service-manager-0
[ebuild   R    ] dev-libs/popt-1.16-r2
[ebuild   R    ] net-misc/rsync-3.1.3
[ebuild   R    ] sys-libs/efivar-37
[ebuild   R    ] sys-boot/efibootmgr-16
[ebuild   R    ] sys-apps/findutils-4.6.0-r1
[ebuild   R    ] dev-libs/libpcre2-10.32
[ebuild   R    ] net-misc/curl-7.65.0
[ebuild   R    ] app-crypt/pinentry-1.1.0-r2
[ebuild   R    ] dev-libs/libtasn1-4.13
[ebuild   R    ] dev-libs/nettle-3.4.1
[ebuild   R    ] net-libs/gnutls-3.6.7
[ebuild   R    ] net-misc/openssh-7.9_p1-r4
[ebuild   R    ] virtual/ssh-0
[ebuild   R    ] app-editors/nano-4.2
[ebuild   R    ] virtual/editor-0-r2
[ebuild   R    ] sys-devel/automake-1.16.1-r1
[ebuild   R    ] sys-devel/libtool-2.4.6-r3
[ebuild   R    ] sys-fs/eudev-3.2.5
[ebuild   R    ] dev-libs/libxml2-2.9.9-r1
[ebuild   R    ] dev-libs/ivykis-0.42.3-r1
[ebuild   R    ] dev-libs/iniparser-3.1-r1
[ebuild   R    ] net-libs/libtirpc-1.0.2-r1
[ebuild   R    ] sys-devel/gettext-0.19.8.1
[ebuild   R    ] dev-libs/libxslt-1.1.33-r1
[ebuild   R    ] app-text/build-docbook-catalog-1.21
[ebuild   R    ] app-portage/portage-utils-0.74
[ebuild   R    ] net-libs/libnsl-1.2.0
[ebuild   R    ] app-crypt/gnupg-2.2.17
[ebuild   R    ] app-arch/tar-1.32
[ebuild   R    ] sys-process/psmisc-23.1-r1
[ebuild   R    ] sys-apps/shadow-4.6
[ebuild   R    ] sys-apps/grep-3.1-r1
[ebuild   R    ] net-misc/wget-1.20.3-r1
[ebuild   R    ] sys-apps/gawk-4.2.1-r1
[ebuild   R    ] sys-apps/diffutils-3.6-r1
[ebuild   R    ] sys-devel/flex-2.6.4-r1
[ebuild   R    ] dev-perl/Locale-gettext-1.70.0
[ebuild   R    ] sys-apps/texinfo-6.6-r1
[ebuild   R    ] dev-util/glib-utils-2.58.3
[ebuild   R    ] dev-util/dialog-1.3.20170131
[ebuild   R    ] app-text/opensp-1.5.2-r3
[ebuild   R    ] sys-libs/pam-1.3.0-r2
[ebuild   R    ] sys-fs/e2fsprogs-1.45.2
[ebuild   R    ] sys-devel/bison-3.1
[ebuild   R    ] sys-apps/help2man-1.47.6
[ebuild   R    ] sys-devel/bc-1.06.95-r2
[ebuild   R    ] app-text/openjade-1.3.2-r8
[ebuild   R    ] dev-libs/elfutils-0.176-r1
[ebuild   R    ] app-portage/mirrorselect-2.2.4-r1
[ebuild   R    ] sys-devel/gcc-8.3.0-r1
[ebuild   R    ] sys-apps/iproute2-4.19.0-r1
[ebuild   R    ] app-text/po4a-0.47-r1
[ebuild   R    ] sys-boot/grub-2.02-r4
[ebuild   R    ] sys-kernel/gentoo-sources-4.19.57
[ebuild   R    ] app-i18n/man-pages-de-2.12
[ebuild   R    ] sys-apps/man-db-2.7.6.1-r2
[ebuild   R    ] dev-libs/glib-2.58.3
[ebuild   R    ] x11-misc/shared-mime-info-1.10
[ebuild   R    ] app-admin/syslog-ng-3.17.2


ifconfig

Code:


eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 87.161.54.167  netmask 255.255.255.192  broadcast 87.161.54.191

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 8  bytes 400 (400.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 400 (400.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



ls -al /sys/class/net/

Code:


total 0
drwxr-xr-x  2 root root 0 26. Jul 13:31 .
drwxr-xr-x 40 root root 0 26. Jul 13:31 ..
lrwxrwxrwx  1 root root 0 26. Jul 13:32 eth0 -> ../../devices/pci0000:00/0000:00:1c.4/0000:02:00.0/net/eth0
lrwxrwxrwx  1 root root 0 26. Jul 13:31 lo -> ../../devices/virtual/net/lo
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Sun Jul 28, 2019 10:49 am    Post subject: Reply with quote

The following relevant information appears when i try to boot from the hard disk


Code:

md waiting for all devices to be available before autodetect
md if you don't use raid use raid=autodetect
md: Autodetecting RAID arrays
md: autorun ...
md: ... autorun DONE
ext4-fs (md0) unable to read superblock
ext4-fs (md0) unable to read superblock
ext4-fs (md0) unable to read superblock
fat fs md0 unable to read boot sector
Cannot open root device "md0" or unknown-block(9,0)
please append a correct root= boot option here are the available partitions
kernel panic not syncing vfs unable to mount root fs on unknown-block(9,0)


grub.cfg

http://dpaste.com/15MEN5G


Last edited by Palme on Sun Jul 28, 2019 11:25 am; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Sun Jul 28, 2019 11:24 am    Post subject: Reply with quote

Palme,

Your md0 did not assemble.
Code:
md: Autodetecting RAID arrays
md: autorun ...
md: ... autorun DONE
md0 should be listed in there.

Put your entire kernel .config onto a pastebin site and post the output of
Code:
fdisk -l

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Sun Jul 28, 2019 11:38 am    Post subject: Reply with quote

fdisk -l
Code:

Festplatte /dev/ram0: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram1: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram2: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram3: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram4: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram5: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram6: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram7: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram8: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram9: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram10: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram11: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram12: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram13: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram14: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/ram15: 64 MiB, 67108864 Bytes, 131072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Gr▒▒e (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/loop0: 4 GiB, 4294967296 Bytes, 8388608 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Gr▒▒e (minimal/optimal): 512 Bytes / 512 Bytes


Festplatte /dev/sda: 1,8 TiB, 2000398934016 Bytes, 3907029168 Sektoren
Festplattenmodell: WDC WD2000FYYZ-0
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Gr▒▒e (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x0f90f33d

Ger▒t      Boot  Anfang       Ende   Sektoren Gr▒▒e Kn Typ
/dev/sda1          2048       6143       4096    2M 83 Linux
/dev/sda2  *       6144    1054719    1048576  512M 83 Linux
/dev/sda3       1054720 3907029167 3905974448  1,8T 83 Linux


Festplatte /dev/sdb: 1,8 TiB, 2000398934016 Bytes, 3907029168 Sektoren
Festplattenmodell: WDC WD2000FYYZ-0
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Gr▒▒e (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x50596596

Ger▒t      Boot Anfang       Ende   Sektoren Gr▒▒e Kn Typ
/dev/sdb1         2048 3907029167 3907027120  1,8T 83 Linux


Festplatte /dev/md0: 3,7 TiB, 4000256622592 Bytes, 7813001216 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Gr▒▒e (minimal/optimal): 524288 Bytes / 1048576 Bytes


config-4.19.57-gentoo
http://dpaste.com/1MN70X1
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Sun Jul 28, 2019 12:02 pm    Post subject: Reply with quote

Palme,

I don't read German but no matter.
Code:
Festplatte /dev/sda: 1,8 TiB, 2000398934016 Bytes, 3907029168 Sektoren
Festplattenmodell: WDC WD2000FYYZ-0
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Gr▒▒e (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x0f90f33d

Ger▒t      Boot  Anfang       Ende   Sektoren Gr▒▒e Kn Typ
/dev/sda1          2048       6143       4096    2M 83 Linux
/dev/sda2  *       6144    1054719    1048576  512M 83 Linux
/dev/sda3       1054720 3907029167 3905974448  1,8T 83 Linux


Festplatte /dev/sdb: 1,8 TiB, 2000398934016 Bytes, 3907029168 Sektoren
Festplattenmodell: WDC WD2000FYYZ-0
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Gr▒▒e (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x50596596

Ger▒t      Boot Anfang       Ende   Sektoren Gr▒▒e Kn Typ
/dev/sdb1         2048 3907029167 3907027120  1,8T 83 Linux


Festplatte /dev/md0: 3,7 TiB, 4000256622592 Bytes, 7813001216 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgr▒▒e (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Gr▒▒e (minimal/optimal): 524288 Bytes / 1048576 Bytes


For raid auto assembly, the partitions that belong to raid sets must be marked type fd in the partition table.
I can see that yours are all 83, so they will not be considered for auto assembly.

-- edit --
Code:
CONFIG_MD_LINEAR=y
# CONFIG_MD_RAID0 is not set

I recall that you set up your raid as level 0, not linear. So that might be a problem.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Sun Jul 28, 2019 12:19 pm    Post subject: Reply with quote

can i convert my current RAID 0 to a Raid Linear .... .can I do this without loosing my data?

Last edited by Palme on Sun Jul 28, 2019 12:38 pm; edited 2 times in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Sun Jul 28, 2019 12:26 pm    Post subject: Reply with quote

Palme,

Conversion will destroy your data.
raid0 splits your data into chunks and writes chunks to each member of the set in turn.
This allows reads and writes to be paralleled, so its good for speed.
Linear joins the raid set members end to end.

With either, when one member of the set fails, you lose all your data.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Sun Jul 28, 2019 12:38 pm    Post subject: Reply with quote

that's my kernel configuration
Code:
[*] Device Drivers  --->
    <*> Multiple devices driver support (RAID and LVM)
        <*> RAID support
            [*] Autodetect RAID arrays during kernel boot
     <*> Linear (append) mode


Linear (append) mode is selected not RAID-0 (striping) mode
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43551
Location: 56N 3W

PostPosted: Sun Jul 28, 2019 12:43 pm    Post subject: Reply with quote

Palme,

I'm fairly sure you did not create your raid set in linear mode.
Try it, fix the partition types so auto assemble can work, then see if it does.

Code:
mdadm -E ...
will tell you.mdadm --detail /dev/md0

-- edit --

From a post of yours on Wed 24 July.
Code:
/dev/md0:
           Version : 0.90
     Creation Time : Tue Jul 23 09:45:09 2019
        Raid Level : raid0
        Array Size : 3906500608 (3725.53 GiB 4000.26 GB)
      Raid Devices : 2
     Total Devices : 2
   Preferred Minor : 0
       Persistence : Superblock is persistent

       Update Time : Tue Jul 23 09:45:09 2019
             State : clean
    Active Devices : 2
   Working Devices : 2
    Failed Devices : 0
     Spare Devices : 0

        Chunk Size : 512K


Chunk Size : 512K. Linear raid does not have a chunk size.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Wed Jul 31, 2019 11:49 am    Post subject: Reply with quote

Hi

I carried out the installation again but still have the same problems well not quite the same errors

Over SSH i still get putty fatal error network error connection timed out

Connection Over VKM works like a charm :roll:
Here's some outputs and config files:


dmesg -T

http://dpaste.com/1T6S6GJ

ifconfig -a
http://dpaste.com/2EGWBEZ

mdadm --detail /dev/md0

http://dpaste.com/0HDEQ3Y

grub.cfg

http://dpaste.com/3P3H5HK

fstab
http://dpaste.com/2B432J5

rc-update -v show

http://dpaste.com/2XBQXRG

make.conf

http://dpaste.com/0PG9MBB

kernel config file

http://dpaste.com/3S8Z6B5

emerge world -ep

http://dpaste.com/22MWJE7

cat /proc/mdstat
Code:

Personalities : [raid1] [linear]
md0 : active linear sda3[0] sdb1[1]
      3906500608 blocks 0k rounding

unused devices: <none>


blkid
Code:


/dev/loop0: UUID="40c4ea95-0ecc-4c51-9f3e-e49d8f62f160" TYPE="ext2"
/dev/sdb1: UUID="fc9f83bc-46a5-17b4-776c-2c25004bd7b2" TYPE="linux_raid_member" PARTUUID="6416989c-01"
/dev/sda1: PARTUUID="91d387ec-01"
/dev/sda2: LABEL="Boot" UUID="3c3fe08a-d518-4e5a-8ffd-cf987c4e396a" TYPE="ext2" PARTUUID="91d387ec-02"
/dev/sda3: UUID="fc9f83bc-46a5-17b4-776c-2c25004bd7b2" TYPE="linux_raid_member" PARTUUID="91d387ec-03"
/dev/md0: LABEL="Gentoo" UUID="a17da2d3-df91-4b39-853c-9395a177566d" TYPE="ext4"


lsblk -f

Code:

lsblk -f
NAME    FSTYPE            LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0   ext2                     40c4ea95-0ecc-4c51-9f3e-e49d8f62f160
sda
|-sda1
|-sda2  ext2              Boot   3c3fe08a-d518-4e5a-8ffd-cf987c4e396a  458.5M     4% /boot
`-sda3  linux_raid_member        fc9f83bc-46a5-17b4-776c-2c25004bd7b2
  `-md0 ext4              Gentoo a17da2d3-df91-4b39-853c-9395a177566d    3.4T     0% /
sdb
`-sdb1  linux_raid_member        fc9f83bc-46a5-17b4-776c-2c25004bd7b2
  `-md0 ext4              Gentoo a17da2d3-df91-4b39-853c-9395a177566d    3.4T     0% /


cat /var/lib/portage/world

Code:

app-admin/syslog-ng
app-portage/cpuid2cpuflags
app-portage/mirrorselect
net-misc/netifrc
sys-apps/pciutils
sys-boot/grub:2
sys-fs/mdadm
sys-kernel/gentoo-sources


according to the Boot logs it seems that eth0 and mdadm causes the problems

Boot logs

http://dpaste.com/2PX6HK9

I appreciate your help in advance because I am really at my wit's end
Back to top
View user's profile Send private message
rufnut
Apprentice
Apprentice


Joined: 16 May 2005
Posts: 205

PostPosted: Wed Jul 31, 2019 2:01 pm    Post subject: Reply with quote

NeddySeagoon wrote:

-- edit --
Code:
CONFIG_MD_LINEAR=y
# CONFIG_MD_RAID0 is not set

I recall that you set up your raid as level 0, not linear. So that might be a problem.



Well spotted NeddySeagoon, looks like palme may have to "mdadm --remove" to get the partitions free to assemble again too?

After he enables CONFIG_MD_RAID0 that is.
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Wed Jul 31, 2019 2:16 pm    Post subject: Reply with quote

Thanks rufnut but This information has meanwhile become obsolete because i performed a fresh installation and configuration

If you take a look at my post above, you'll see my current config
Back to top
View user's profile Send private message
Palme
Tux's lil' helper
Tux's lil' helper


Joined: 31 May 2014
Posts: 93

PostPosted: Fri Aug 02, 2019 12:11 pm    Post subject: Reply with quote

Hi
With a few tips from the IRC channel, I could pinpoint the problem

Code:

udevadm test-builtin net_id /sys/class/net/eth0

rc-update delete net.eth0 boot
rm /etc/init.d/net.eth0
ln -s /etc/init.d/net.lo /etc/init.d/net.enp2s0
rc-update add net.enp2s0 default


thank you all so much for your support
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
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