You are not logged in.
Pages: 1
How might /dev directory be populated in chroot?
Linux kernel x86_64 system.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Have you read https://wiki.archlinux.org/index.php/Chroot ?
Offline
Lots there to read! Will re-read same...
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
No specific info for /dev directory.
I have mounted the drives partitions, boot and root.
I have enabled the dns.
I have performed pacman -Syu.
I ran ...pacman -S udev...
I have no idea what is needed other than that.
uname -m says x86_64....correct!
uname -a says linux 3.0
Am chroot into the drive..
What else is new?
EDIT:I am still in chroot...................
Last edited by lilsirecho (2011-10-02 02:08:58)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Did you
mount -o bind /dev dev/?
Offline
Yowsah!!! All elements of chroot are present in the /mnt....including the boot partition...
EDIT: Does not udev populate the /dev directory?
Last edited by lilsirecho (2011-10-02 02:12:37)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Partial solution obtained after pacman -S udev.
Problem remains that the system fails to boot with error message cannot determine major-minor number of root device....
Using uuid and that is a correct number.
Directory /dev does not list the major -minor numbers of the uuid in block devices.
These numbers are 8 and 35 as determined by examining the system in another HDD in archlinux on the same machine.
In /dev ran ls -l sd* which lists all block dev numbers for every device connected to the system.(by partition id such as sdc3)
How can I insert the correct numbers in the /dev/block directory for the root partition to enable the boot to connect to the root uuid device partition?
EDIT: The /dev/block directory for the HDD which fails does not have the numbers 8;35 included!
Last edited by lilsirecho (2011-10-02 03:54:59)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
The following is my chroot data which shows no 8;35 listing for the HDD root partition sdi3.....
[root@n6re ~]# mount /dev/sdi3 /mnt/md
[root@n6re ~]# cd /mnt/md
[root@n6re md]# mount -t proc proc proc/
[root@n6re md]# mount -t sysfs sys sys/
[root@n6re md]# mount -o bind /dev dev/
[root@n6re md]# mount /dev/sdi1
[root@n6re md]# cp -L /etc/resolv.conf etc/resolv.conf
[root@n6re md]# chroot . /bin/bash
[root@n6re /]# mkinitcpio -p linux
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.0-ARCH
-> Parsing hook: [base]
-> Parsing hook: [udev]
-> Parsing hook: [autodetect]
-> Parsing hook: [pata]
-> Parsing hook: [scsi]
-> Parsing hook: [sata]
-> Parsing hook: [mdadm]
-> Parsing hook: [usb]
-> Parsing hook: [filesystems]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
7640 blocks
==> Image generation successful
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.0-ARCH
-> Parsing hook: [base]
-> Parsing hook: [udev]
-> Parsing hook: [pata]
-> Parsing hook: [scsi]
-> Parsing hook: [sata]
-> Parsing hook: [mdadm]
-> Parsing hook: [usb]
-> Parsing hook: [filesystems]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
25046 blocks
==> Image generation successful
[root@n6re /]# ls /dev
agpgart rtc snd tty42 vcs16 vcs54 vcsa34
autofs rtc0 stderr tty43 vcs17 vcs55 vcsa35
block sda stdin tty44 vcs18 vcs56 vcsa36
bsg sda1 stdout tty45 vcs19 vcs57 vcsa37
btrfs-control sda2 tty tty46 vcs2 vcs58 vcsa38
bus sda3 tty0 tty47 vcs20 vcs59 vcsa39
char sda4 tty1 tty48 vcs21 vcs6 vcsa4
console sdb tty10 tty49 vcs22 vcs60 vcsa40
core sdb1 tty11 tty5 vcs23 vcs61 vcsa41
cpu sdb2 tty12 tty50 vcs24 vcs62 vcsa42
cpu_dma_latency sdc tty13 tty51 vcs25 vcs63 vcsa43
disk sdc1 tty14 tty52 vcs26 vcs7 vcsa44
dri sdd tty15 tty53 vcs27 vcs8 vcsa45
fb0 sdd1 tty16 tty54 vcs28 vcs9 vcsa46
fd sdd2 tty17 tty55 vcs29 vcsa vcsa47
full sde tty18 tty56 vcs3 vcsa1 vcsa48
fuse sde1 tty19 tty57 vcs30 vcsa10 vcsa49
hidraw0 sde2 tty2 tty58 vcs31 vcsa11 vcsa5
hidraw1 sdf tty20 tty59 vcs32 vcsa12 vcsa50
hidraw2 sdf1 tty21 tty6 vcs33 vcsa13 vcsa51
hpet sdg tty22 tty60 vcs34 vcsa14 vcsa52
initctl sdg1 tty23 tty61 vcs35 vcsa15 vcsa53
input sdg2 tty24 tty62 vcs36 vcsa16 vcsa54
kmsg sdh tty25 tty63 vcs37 vcsa17 vcsa55
log sdh1 tty26 tty7 vcs38 vcsa18 vcsa56
loop0 sdh2 tty27 tty8 vcs39 vcsa19 vcsa57
mapper sdi tty28 tty9 vcs4 vcsa2 vcsa58
mcelog sdi1 tty29 ttyS0 vcs40 vcsa20 vcsa59
md sdi2 tty3 ttyS1 vcs41 vcsa21 vcsa6
md0 sdi3 tty30 ttyS2 vcs42 vcsa22 vcsa60
mem sdi4 tty31 ttyS3 vcs43 vcsa23 vcsa61
net sg0 tty32 uinput vcs44 vcsa24 vcsa62
network_latency sg1 tty33 urandom vcs45 vcsa25 vcsa63
network_throughput sg2 tty34 usb vcs46 vcsa26 vcsa7
null sg3 tty35 vcs vcs47 vcsa27 vcsa8
parport0 sg4 tty36 vcs1 vcs48 vcsa28 vcsa9
port sg5 tty37 vcs10 vcs49 vcsa29 vga_arbiter
ppp sg6 tty38 vcs11 vcs5 vcsa3 watchdog
psaux sg7 tty39 vcs12 vcs50 vcsa30 zero
ptmx sg8 tty4 vcs13 vcs51 vcsa31
pts shm tty40 vcs14 vcs52 vcsa32
random snapshot tty41 vcs15 vcs53 vcsa33
[root@n6re /]# ls /dev/block
8:0 8:113 8:129 8:132 8:18 8:32 8:48 8:64 8:80 8:97
8:1 8:114 8:130 8:16 8:2 8:33 8:49 8:65 8:81 8:98
8:112 8:128 8:131 8:17 8:3 8:4 8:50 8:66 8:96 9:0
[root@n6re /]# Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Ran a new search as follows for the sdi3 partition;
[root@n6re ~]# ls -l /dev/sdi3
brw-rw---- 1 root disk 8, 131 Oct 1 23:59 /dev/sdi3
[root@n6re ~]# This indicates a changing minor number for the subject HDD.
This search made in another boot by a second HDD on the same machine.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Pages: 1