Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
install gentoo over rste
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
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5452

PostPosted: Sun Dec 15, 2019 7:37 pm    Post subject: install gentoo over rste Reply with quote

Greetings,

I have a ubuntu install over intel rste which I want to replace with gentoo.
I've tried both latest sysrescuecd and the livecd but I'm unable to activate the fake raid, here are some inputs:
Code:
livecd ~ # lsmod | grep mod
dm_mod 110592 7
dm_raid,dm_crypt,dm_zero,dm_log,dm_snapshot,dm_mirror,dm_bufio
dax 20480 1 dm_mod
livecd ~ # dmraid -r
/dev/sda: isw, "isw_cacggjghbc", GROUP, ok, 156301486 sectors, data@ 0
/dev/sdb: isw, "isw_cacggjghbc", GROUP, ok, 312581806 sectors, data@ 0
livecd ~ # dmraid -ay
RAID set "isw_cacggjghbc_Volume0" was not activated
ERROR: device "isw_cacggjghbc_Volume0" could not be found
livecd ~ # mdadm --examine --scan >> /etc/mdadm.conf
livecd ~ # cat /etc/mdadm.conf
# 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
ARRAY metadata=imsm UUID=1116f714:57ba4d63:3b1ccb56:91beba00
ARRAY /dev/md/Volume0 container=1116f714:57ba4d63:3b1ccb56:91beba00
member=0 UUID=5b239b90:4e35d3e9:32e62c76:3f6eb8cd
ARRAY /dev/md/0 metadata=1.2 UUID=5509329e:48718c24:c923145c:d3df626f
name=localhost:0
livecd ~ # mdadm --assemble --scan -v
mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/sde1
mdadm: /dev/sde is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/sde
mdadm: no RAID superblock on /dev/sde
mdadm: /dev/sr0 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/sr0
mdadm: no RAID superblock on /dev/sr0
mdadm: /dev/sdc is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/sdc
mdadm: no RAID superblock on /dev/sdc
mdadm: no RAID superblock on /dev/sdb1
mdadm: No OROM/EFI properties for /dev/sdb
mdadm: no RAID superblock on /dev/sdb
mdadm: no RAID superblock on /dev/sda1
mdadm: No OROM/EFI properties for /dev/sda
mdadm: no RAID superblock on /dev/sda
mdadm: /dev/loop0 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/loop0
mdadm: no RAID superblock on /dev/loop0
mdadm: /dev/ram15 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram15
mdadm: no RAID superblock on /dev/ram15
mdadm: /dev/ram14 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram14
mdadm: no RAID superblock on /dev/ram14
mdadm: /dev/ram13 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram13
mdadm: no RAID superblock on /dev/ram13
mdadm: /dev/ram12 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram12
mdadm: no RAID superblock on /dev/ram12
mdadm: /dev/ram11 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram11
mdadm: no RAID superblock on /dev/ram11
mdadm: /dev/ram10 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram10
mdadm: no RAID superblock on /dev/ram10
mdadm: /dev/ram9 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram9
mdadm: no RAID superblock on /dev/ram9
mdadm: /dev/ram8 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram8
mdadm: no RAID superblock on /dev/ram8
mdadm: /dev/ram7 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram7
mdadm: no RAID superblock on /dev/ram7
mdadm: /dev/ram6 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram6
mdadm: no RAID superblock on /dev/ram6
mdadm: /dev/ram5 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram5
mdadm: no RAID superblock on /dev/ram5
mdadm: /dev/ram4 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram4
mdadm: no RAID superblock on /dev/ram4
mdadm: /dev/ram3 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram3
mdadm: no RAID superblock on /dev/ram3
mdadm: /dev/ram2 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram2
mdadm: no RAID superblock on /dev/ram2
mdadm: /dev/ram1 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram1
mdadm: no RAID superblock on /dev/ram1
mdadm: /dev/ram0 is not attached to Intel(R) RAID controller.
mdadm: No OROM/EFI properties for /dev/ram0
mdadm: no RAID superblock on /dev/ram0
mdadm: looking for devices for /dev/md/Volume0
mdadm: Cannot assemble mbr metadata on /dev/sde1
mdadm: Cannot assemble mbr metadata on /dev/sde
mdadm: no recogniseable superblock on /dev/sr0
mdadm: Cannot assemble mbr metadata on /dev/sdc
mdadm: /dev/sdb1 has wrong uuid.
mdadm: No OROM/EFI properties for /dev/sdb
mdadm: no RAID superblock on /dev/sdb
mdadm: no recogniseable superblock on /dev/sda1
mdadm: No OROM/EFI properties for /dev/sda
mdadm: no RAID superblock on /dev/sda
mdadm: no recogniseable superblock on /dev/loop0
mdadm: no recogniseable superblock on /dev/ram15
mdadm: no recogniseable superblock on /dev/ram14
mdadm: no recogniseable superblock on /dev/ram13
mdadm: no recogniseable superblock on /dev/ram12
mdadm: no recogniseable superblock on /dev/ram11
mdadm: no recogniseable superblock on /dev/ram10
mdadm: no recogniseable superblock on /dev/ram9
mdadm: no recogniseable superblock on /dev/ram8
mdadm: no recogniseable superblock on /dev/ram7
mdadm: no recogniseable superblock on /dev/ram6
mdadm: no recogniseable superblock on /dev/ram5
mdadm: no recogniseable superblock on /dev/ram4
mdadm: no recogniseable superblock on /dev/ram3
mdadm: no recogniseable superblock on /dev/ram2
mdadm: no recogniseable superblock on /dev/ram1
mdadm: no recogniseable superblock on /dev/ram0
mdadm: looking for devices for /dev/md/0
mdadm: No super block found on /dev/sde1 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/sde1
mdadm: No super block found on /dev/sde (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/sde
mdadm: No super block found on /dev/sr0 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/sr0
mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got
a0ddb71c)
mdadm: no RAID superblock on /dev/sdc
mdadm: /dev/sdb1 is busy - skipping
mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/sdb
mdadm: No super block found on /dev/sda1 (Expected magic a92b4efc, got
00008101)
mdadm: no RAID superblock on /dev/sda1
mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got
a0ddb71c)
mdadm: no RAID superblock on /dev/sda
mdadm: No super block found on /dev/loop0 (Expected magic a92b4efc, got
c8c8bc10)
mdadm: no RAID superblock on /dev/loop0
mdadm: No super block found on /dev/ram15 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram15
mdadm: No super block found on /dev/ram14 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram14
mdadm: No super block found on /dev/ram13 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram13
mdadm: No super block found on /dev/ram12 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram12
mdadm: No super block found on /dev/ram11 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram11
mdadm: No super block found on /dev/ram10 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram10
mdadm: No super block found on /dev/ram9 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram9
mdadm: No super block found on /dev/ram8 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram8
mdadm: No super block found on /dev/ram7 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram7
mdadm: No super block found on /dev/ram6 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram6
mdadm: No super block found on /dev/ram5 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram5
mdadm: No super block found on /dev/ram4 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram4
mdadm: No super block found on /dev/ram3 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram3
mdadm: No super block found on /dev/ram2 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram2
mdadm: No super block found on /dev/ram1 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram1
mdadm: No super block found on /dev/ram0 (Expected magic a92b4efc, got
00000000)
mdadm: no RAID superblock on /dev/ram0


any ideas how to activate the fakeraid?
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
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