Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
grub2-mkconfig doesn't work because of filesystem '822`
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
tot-to
n00b
n00b


Joined: 09 Apr 2008
Posts: 21

PostPosted: Fri Aug 01, 2014 4:49 pm    Post subject: grub2-mkconfig doesn't work because of filesystem '822` Reply with quote

On the df -h listing I can see strange fiflesystem with `822' instead of path:
Code:

Filesystem      Size  Used Avail Use% Mounted on
rootfs           30G  3.0G   25G  11% /
822              30G  3.0G   25G  11% /
devtmpfs        7.7G     0  7.7G   0% /dev
tmpfs           1.6G  280K  1.6G   1% /run
shm             7.7G     0  7.7G   0% /dev/shm
[...]

I can't find any information about this entry in search engines.

Because of this filesystem i can't migrate to grub2:
Code:

# grub2-mkconfig -o /boot/grub/grub.cfg
/usr/sbin/grub2-probe: error: failed to get canonical path of `822'.


I've created this topic in "Installing Gentoo" because Grub2 installation is a part of default Gentoo installation now and this sub-forum looks to me the best for Grub2-related issues. But actually i'm migrating from lilo to grub2 now, not installing OS from scratch.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sat Aug 02, 2014 4:18 am    Post subject: Reply with quote

boot livecd/usb, mount the gentoo partitions, run
Code:
wgetpaste /mnt/gentoo/etc/fstab/
wgetpaste /proc/self/mountinfo
blkid | wgetpaste
parted -l | wgetpaste
post the url's returned
_________________
Defund the FCC.
Back to top
View user's profile Send private message
tot-to
n00b
n00b


Joined: 09 Apr 2008
Posts: 21

PostPosted: Sat Aug 02, 2014 9:28 am    Post subject: Reply with quote

Unfortunately, it's a remote computer and i can't boot with livecd right away, but i'll do it later.
Here it is from the installed system:
Code:

 # grep -v ^# /etc/fstab
UUID=3ae837ac-e067-4ead-a050-152629f6eb55   /boot      ext4   noatime,nodiratime,nodev,nosuid,noexec,discard,noauto      0 2 #sda1
UUID=ab5adb03-14a5-4803-a021-6d1a70aefdfa   /      ext4   noatime,nodiratime,nodev,rw               0 1 #sdc2
UUID=d281d9a3-1940-4c1e-b41a-b8d1d4c55ddf   /var      ext4   noatime,nodiratime,nodev,nosuid,noexec,discard         0 0 #md125
UUID=cc3c3767-65d1-47bc-9b70-b72a6e3f56b8   /home      ext4   noatime,nodiratime,nodev,nosuid,noexec,discard         0 0 #md126
UUID=a64c50e5-2e92-4b4f-a7c0-75037cd81d0c   /var/log   ext4   noatime,nodiratime,nodev,nosuid,noexec,discard,data=writeback   0 0 #sda5
UUID=6abe850f-e36e-4a84-ad21-297b07cd7399   /mnt/raid   ext4   noatime,nodiratime,nodev,nosuid,noexec            0 0
tmpfs      /tmp      tmpfs   noatime,nodiratime,nodev,nosuid,noexec,size=2G,mode=1777   0 0
tmpfs      /var/tmp   tmpfs   noatime,nodiratime,nodev,nosuid,noexec,size=8G,mode=1777   0 0
tmpfs      /var/spool   tmpfs   noatime,nodiratime,nodev,nosuid,noexec,size=2G,mode=0755   0 0

 # cat /proc/self/mountinfo
12 1 8:34 / / rw,nodev,noatime,nodiratime - ext4 822 rw,data=ordered
13 12 0:5 / /dev rw,relatime - devtmpfs devtmpfs rw,size=8048584k,nr_inodes=2012146,mode=755
14 12 0:3 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
15 12 0:11 / /run rw,nosuid,nodev,relatime - tmpfs tmpfs rw,size=1609980k,mode=755
16 13 0:10 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts rw,gid=5,mode=620
17 13 0:12 / /dev/shm rw,nosuid,nodev,noexec,relatime - tmpfs shm rw
18 12 0:13 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
19 18 0:7 / /sys/kernel/debug rw,nosuid,nodev,noexec,relatime - debugfs debugfs rw
20 12 9:125 / /var rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/md125 rw,discard,data=ordered
21 12 9:126 / /home rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/md126 rw,discard,data=ordered
22 20 8:5 / /var/log rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/sda5 rw,discard,data=writeback
23 12 9:124 / /mnt/raid rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/md124 rw,data=ordered
24 12 0:14 / /tmp rw,nosuid,nodev,noexec,noatime,nodiratime - tmpfs tmpfs rw,size=2097152k
25 20 0:15 / /var/tmp rw,nosuid,nodev,noexec,noatime,nodiratime - tmpfs tmpfs rw,size=8388608k
26 20 0:16 / /var/spool rw,nosuid,nodev,noexec,noatime,nodiratime - tmpfs tmpfs rw,size=2097152k,mode=755
28 12 8:1 / /boot rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/sda1 rw,discard,data=ordered

 # blkid
/dev/sda1: UUID="3ae837ac-e067-4ead-a050-152629f6eb55" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="048ac708-7ec3-4736-8c3a-e79e9ec4a38d"
/dev/sda2: UUID="4a780a2c-d4d6-1996-cb20-1669f728008a" TYPE="linux_raid_member" PARTLABEL="Linux filesystem" PARTUUID="04097f0c-8b5e-4ad8-88a3-aae3d123bd5a"
/dev/sda3: UUID="cb45cdf8-55f6-9d67-9680-c48e68f3d421" UUID_SUB="f286a7f0-8316-cad6-7580-7b2c92cfe945" LABEL="livecd:3" TYPE="linux_raid_member" PARTLABEL="Linux filesystem" PARTUUID="93c17abc-e6d9-4b62-a07b-6b178664f60b"
/dev/sda4: UUID="0cb2245c-1f3e-4b8e-cef0-4f6ec6bd9d68" UUID_SUB="973fc146-90f1-2d19-4220-397a9b141304" LABEL="livecd:4" TYPE="linux_raid_member" PARTLABEL="Linux filesystem" PARTUUID="5d8660a8-1166-44b7-9ac0-76d9055717ad"
/dev/sda5: UUID="a64c50e5-2e92-4b4f-a7c0-75037cd81d0c" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="cac7df85-baf6-4e04-ba4e-d56761b5cb9b"
/dev/sdc1: UUID="c71eb6db-557f-4b02-950e-c0cc3c5d2841" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="bd37a1b0-d366-44b0-91b7-a169fa60e301"
/dev/sdc2: UUID="ab5adb03-14a5-4803-a021-6d1a70aefdfa" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="71a8143d-2896-44e1-9d64-e65aa003cc0c"
/dev/sdc3: UUID="9376efd7-624b-4021-ae24-9c62d9d983c7" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="bd09911a-5b23-40f9-92b4-c3bb98f40e79"
/dev/sdc4: UUID="ef13e879-5122-4eef-a800-fa5d3bc13e1a" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="cb769200-fa5d-4724-a7f7-763dca0556a5"
/dev/sdc5: UUID="9a30e0d9-4198-4a31-845a-e02b5afe5c0b" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="8e5c0222-0b39-4f1b-bdf4-4abc57bc1310"
/dev/sdc6: UUID="315e16d0-831f-a8ea-7e96-d607b14e84e1" UUID_SUB="66a50314-5e94-d631-cfad-63599e362f45" LABEL="livecd:6" TYPE="linux_raid_member" PARTLABEL="Linux filesystem" PARTUUID="12338667-231b-4613-9e34-96b0cb1b9cf9"
/dev/sdb1: UUID="8146d1f5-27fe-46ab-9730-de4bdb5455f6" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="7631d17a-8b39-486d-8aa0-cf009b0716f7"
/dev/sdb2: UUID="4a780a2c-d4d6-1996-cb20-1669f728008a" TYPE="linux_raid_member" PARTLABEL="Linux filesystem" PARTUUID="b8c8250e-e9da-462d-acea-84581909c9b9"
/dev/sdb3: UUID="cb45cdf8-55f6-9d67-9680-c48e68f3d421" UUID_SUB="74d42ba0-5cd1-5bce-e8f6-8a42dc1792d2" LABEL="livecd:3" TYPE="linux_raid_member" PARTLABEL="Linux filesystem" PARTUUID="b946eb1f-7e25-4cf7-a6c9-756c0e027642"
/dev/sdb4: UUID="0cb2245c-1f3e-4b8e-cef0-4f6ec6bd9d68" UUID_SUB="5071c165-6a23-84b4-f8d2-347f725ab247" LABEL="livecd:4" TYPE="linux_raid_member" PARTLABEL="Linux filesystem" PARTUUID="22a02100-41a9-462b-af9b-f33eb1de3828"
/dev/sdb5: UUID="f46b1349-b50d-4bce-a18c-344d11bc171d" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="ba7fd086-133f-4f31-becc-2a4a08f8ae45"
/dev/sdb6: UUID="315e16d0-831f-a8ea-7e96-d607b14e84e1" UUID_SUB="a453d661-c719-8477-b42a-11805028445f" LABEL="livecd:6" TYPE="linux_raid_member" PARTLABEL="Linux filesystem" PARTUUID="b2e3ee07-7b57-49fb-83e5-a391810be3bf"
/dev/md127: UUID="bdbab0f8-bb68-4ae9-bacc-e14b992b12bc" TYPE="ext4"
/dev/md126: UUID="cc3c3767-65d1-47bc-9b70-b72a6e3f56b8" TYPE="ext4"
/dev/md125: UUID="d281d9a3-1940-4c1e-b41a-b8d1d4c55ddf" TYPE="ext4"
/dev/md124: UUID="6abe850f-e36e-4a84-ad21-297b07cd7399" TYPE="ext4"

 # parted -l
Model: ATA M4-CT256M4SSD2 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  66.1MB  65.0MB  ext4         Linux filesystem
 2      66.1MB  32.1GB  32.0GB  ext4         Linux filesystem
 3      32.1GB  250GB   218GB                Linux filesystem
 4      250GB   252GB   2147MB               Linux filesystem
 5      252GB   256GB   3851MB  ext4         Linux filesystem


Model: ATA ST3000NC002-1DY1 (scsi)
Disk /dev/sdb: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  66.1MB  65.0MB  ext4         Linux filesystem
 2      66.1MB  32.1GB  32.0GB  ext4         Linux filesystem
 3      32.1GB  250GB   218GB                Linux filesystem
 4      250GB   252GB   2147MB               Linux filesystem
 5      252GB   256GB   3851MB  ext4         Linux filesystem
 6      256GB   3001GB  2745GB               Linux filesystem


Model: ATA ST3000NC002-1DY1 (scsi)
Disk /dev/sdc: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  66.1MB  65.0MB  ext4         Linux filesystem
 2      66.1MB  32.1GB  32.0GB  ext4         Linux filesystem
 3      32.1GB  250GB   218GB   ext4         Linux filesystem
 4      250GB   252GB   2147MB  ext4         Linux filesystem
 5      252GB   256GB   3851MB  ext4         Linux filesystem
 6      256GB   3001GB  2745GB               Linux filesystem


Model: Linux Software RAID Array (md)
Disk /dev/md124: 2744GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags:

Number  Start  End     Size    File system  Flags
 1      0.00B  2744GB  2744GB  ext4


Model: Linux Software RAID Array (md)
Disk /dev/md125: 218GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags:

Number  Start  End    Size   File system  Flags
 1      0.00B  218GB  218GB  ext4


Model: Linux Software RAID Array (md)
Disk /dev/md126: 2146MB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags:

Number  Start  End     Size    File system  Flags
 1      0.00B  2146MB  2146MB  ext4


Model: Linux Software RAID Array (md)
Disk /dev/md127: 32.0GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags:

Number  Start  End     Size    File system  Flags
 1      0.00B  32.0GB  32.0GB  ext4

All filesystems exept / and /boot are on raid1.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sat Aug 02, 2014 4:34 pm    Post subject: Reply with quote

Quote:
# cat /proc/self/mountinfo
12 1 8:34 / / rw,nodev,noatime,nodiratime - ext4 822 rw,data=ordered
suspect udev renaming; as this is post udev. sdc2 or uuid is listed in the non-udev affected outputs
Code:
locate rules.d
usually /etc/udev/rules.d would be used for a user's renaming rule, /lib64/udev/rules.d for standing developer's rules, you may have to do a lot of reading to find or eliminate a stray rule as a cause
Code:
udevadm info --name=/dev/sdc2
produce output?
Code:
udevadm info --name=822
produce output?
if both have output, compare
Code:
dmesg | grep -i sdc2
produce output? any mention of renaming?
Quote:
ls /etc/udev/rules.d

_________________
Defund the FCC.
Back to top
View user's profile Send private message
tot-to
n00b
n00b


Joined: 09 Apr 2008
Posts: 21

PostPosted: Sat Aug 02, 2014 10:39 pm    Post subject: Reply with quote

Thanks for trying to help me. :)

About udev (or eudev to be precise), i should say, that the only thing i've done about it on this machine is adding it to the default runlevel.
In /etc/udev/rules.d there is only file 70-persistent-net.rules, which is as far as i understand it, the place where eudev remember's names of network interfaces.
In case of /lib64/udev/rules.d there are this files, that i've never changed:
Code:

40-gentoo.rules        60-persistent-alsa.rules          61-accelerometer.rules             75-probe_mtd.rules
42-usb-hid-pm.rules    60-persistent-input.rules         64-btrfs.rules                     75-tty-description.rules
50-firmware.rules      60-persistent-serial.rules        64-md-raid.rules                   78-sound-card.rules
50-udev-default.rules  60-persistent-storage-tape.rules  75-cd-aliases-generator.rules      80-drivers.rules
60-cdrom_id.rules      60-persistent-storage.rules       75-net-description.rules           90-network.rules
60-drm.rules           60-persistent-v4l.rules           75-persistent-net-generator.rules  95-udev-late.rules

udevadm info --name=822 just say's "device node not found".
The output of udevadm info --name=/dev/sdc2
Code:

P: /devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sdc/sdc2
N: sdc2
S: disk/by-id/ata-ST3000NC002-1DY166_Z1F22CYM-part2
S: disk/by-id/wwn-0x5000c5004f6d3d87-part2
S: disk/by-partlabel/Linux\x20filesystem
S: disk/by-partuuid/71a8143d-2896-44e1-9d64-e65aa003cc0c
S: disk/by-uuid/ab5adb03-14a5-4803-a021-6d1a70aefdfa
S: root
E: DEVLINKS=/dev/disk/by-id/ata-ST3000NC002-1DY166_Z1F22CYM-part2 /dev/disk/by-id/wwn-0x5000c5004f6d3d87-part2 /dev/disk/by-partlabel/Linux\x20filesystem /dev/disk/by-partuuid/71a8143d-2896-44e1-9d64-e65aa003cc0c /dev/disk/by-uuid/ab5adb03-14a5-4803-a021-6d1a70aefdfa /dev/root
E: DEVNAME=/dev/sdc2
E: DEVPATH=/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sdc/sdc2
E: DEVTYPE=partition
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=324
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=324
E: ID_ATA_FEATURE_SET_SECURITY_FROZEN=1
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_ROTATION_RATE_RPM=7200
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BUS=ata
E: ID_FS_TYPE=ext4
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=ab5adb03-14a5-4803-a021-6d1a70aefdfa
E: ID_FS_UUID_ENC=ab5adb03-14a5-4803-a021-6d1a70aefdfa
E: ID_FS_VERSION=1.0
E: ID_MODEL=ST3000NC002-1DY166
E: ID_MODEL_ENC=ST3000NC002-1DY166\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PART_ENTRY_DISK=8:32
E: ID_PART_ENTRY_NAME=Linux\x20filesystem
E: ID_PART_ENTRY_NUMBER=2
E: ID_PART_ENTRY_OFFSET=129024
E: ID_PART_ENTRY_SCHEME=gpt
E: ID_PART_ENTRY_SIZE=62500864
E: ID_PART_ENTRY_TYPE=0fc63daf-8483-4772-8e79-3d69d8477de4
E: ID_PART_ENTRY_UUID=71a8143d-2896-44e1-9d64-e65aa003cc0c
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=545cf9ae-3586-40f1-890c-fba34b6ed60a
E: ID_REVISION=CN01
E: ID_SERIAL=ST3000NC002-1DY166_Z1F22CYM
E: ID_SERIAL_SHORT=Z1F22CYM
E: ID_TYPE=disk
E: ID_WWN=0x5000c5004f6d3d87
E: ID_WWN_WITH_EXTENSION=0x5000c5004f6d3d87
E: MAJOR=8
E: MINOR=34
E: SUBSYSTEM=block
E: USEC_INITIALIZED=47622

and dmesg about sdc2:
Code:

# dmesg | grep -i sdc2
[    0.815213]  sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6
[    0.837310] EXT4-fs (sdc2): couldn't mount as ext3 due to feature incompatibilities
[    0.845629] EXT4-fs (sdc2): couldn't mount as ext2 due to feature incompatibilities
[    0.860409] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null)
[    2.764499] EXT4-fs (sdc2): re-mounted. Opts: (null)

So, nothing about renaming... :(
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sun Aug 03, 2014 1:38 am    Post subject: Reply with quote

Almost certain then that eudev is not the culprit.
Wonder if the nodev option in fstab could be involved?
Perhaps some experts will join?
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13845

PostPosted: Sun Aug 03, 2014 2:41 am    Post subject: Reply with quote

I use the nodev option on most filesystems and have not seen anything like this. According to the kernel source (fs/proc_namespace.c show_mountinfo) for /proc/self/mountinfo, that string comes from calling sb->s_op->show_devname if defined, else from calling mangle on the saved device name. Mangle is a simple text transformer, so either the saved device name is weird or sb->s_op->show_devname is defined and is weird.

I note that /dev/sdc2 has major number 8 and minor number 34, or in hex, 0x08 0x22 => 822.
Back to top
View user's profile Send private message
tot-to
n00b
n00b


Joined: 09 Apr 2008
Posts: 21

PostPosted: Sun Aug 03, 2014 2:17 pm    Post subject: Reply with quote

DONAHUE, is it still worth doing to boot with livecd and post the same outputs from livecd as you suggested to do in the begining?

Hu, i think your explanation about the origin of this number is true. I've checked other machines, that i have and there is another one with such an issue. But the number is 804, not 822. And in /proc/self/mountinfo i can see this line (it's configured to run with read-only root):
11 1 8:4 / / ro,relatime - ext4 804 ro,data=ordered
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sun Aug 03, 2014 3:35 pm    Post subject: Reply with quote

the 804 machine boots sda4??
Quote:
is it still worth doing
no, you got all the data via a "normal" boot -- maybe, we don't know if a livecd would see 804 or 822 type designations in mount run from the cd system or from the chroot
BTW what bootloader is currently in use?
suppose you altered the kernel cmdline to include init=/bin/bb and rebooted and checked mount output.
do the two machines showing 804 and 822 have some common hardware configuration that other machines do not?
would a manual grub.cfg serve your purpose? or grub legacy which now works with gpt.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Sun Aug 03, 2014 8:53 pm    Post subject: Reply with quote

Your 822 is as Hu said, the major minor of the device while it should be /dev/root

In your case, udev (eudev) show /dev/root was set
Code:
E: DEVLINKS=/dev/disk/by-id/ata-ST3000NC002-1DY166_Z1F22CYM-part2 /dev/disk/by-id/wwn-0x5000c5004f6d3d87-part2 /dev/disk/by-partlabel/Linux\x20filesystem /dev/disk/by-partuuid/71a8143d-2896-44e1-9d64-e65aa003cc0c /dev/disk/by-uuid/ab5adb03-14a5-4803-a021-6d1a70aefdfa /dev/root


Look at my / from mountinfo, note how it expose /dev/root as name
Code:
12 1 8:18 / / rw,noatime - ext3 /dev/root rw,errors=continue,barrier=1,data=ordered


And the problem is coming then from grub that stupidly browse /proc/self/mounts find the 822 device and think it's a valid one to use.

I don't know how to fix the 822 issue, you can try using the provided script /lib/udev/dev-root-link.sh that will create a rules to force the device having /dev/root symlink create (and it should update it, so the idea is that it might change 822 to /dev/root then) but i'm not sure it will help as you seems to have it properly set already. If it fix your issue, change rc_dev_root_symlink to YES in /etc/conf.d/udev to enable it.
Check your /proc/self/mounts show /dev/root to be sure, you should see rootfs + /dev/root from there.
Code:
cat /proc/self/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw,noatime,errors=continue,barrier=1,data=ordered 0 0
ls -l /dev/root
lrwxrwxrwx 1 root root 4  3 août  21:41 /dev/root -> sdb2

What you can try is create the symlink to 822 so the stupid grub2 will now have a real device to play with.
Code:
ln -s /dev/sdc2 /dev/822
Back to top
View user's profile Send private message
tot-to
n00b
n00b


Joined: 09 Apr 2008
Posts: 21

PostPosted: Thu Aug 07, 2014 4:10 pm    Post subject: Reply with quote

DONAHUE, yes, the second machine with 804 filesystem has root filesystem on sda4. Sorry for not mentioning it explicitly.
Both machines use lilo as a bootloader at the moment.

I have tried to boot my local machine (without such a filesystem) with init=/bin/bb option to the kernel and it looks to me that it doesn't start any services at all, including network and ssh daemon. So, this needs to be done with physical access which i'll have in about 2-3 weeks. Also, i'll check if the numbered filesystems are visible with livecd.

Both machines has quite different hardware configurations. Also, the second (804) machine has no raid. On the side of software they serve different purposes, but have been configured by the same person (myself) and as similar as possible.

The problem with grub1 and lilo is that they are not able to boot from UUID and i would like to move root on the first (822) machine to raid. The mdX devices change their numbers quite often with reboot and therefore i can't pass to kernel some exact md-device as root. That's why i migrate the first machine, but not the second.

It's good idea to try manual configuration. I'll do that. But normally i would prefer automatic to be sure that all entries are correct.

krinn, the /dev/root symbolic link exists already.

/proc/self/mount shows numbers instead of /dev/root. I don't think creating /dev/822 symlink can help since there is no "/dev/" in listings, only numbers. But i'll try anyway.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13845

PostPosted: Fri Aug 08, 2014 1:42 am    Post subject: Reply with quote

tot-to wrote:
I have tried to boot my local machine (without such a filesystem) with init=/bin/bb option to the kernel and it looks to me that it doesn't start any services at all, including network and ssh daemon.
That is expected. Services are started by your init system. If you set init=/bin/bb, then your init system is not run. Instead, /bin/bb is run and it is your responsibility to use /bin/bb to start any required services.
Back to top
View user's profile Send private message
tot-to
n00b
n00b


Joined: 09 Apr 2008
Posts: 21

PostPosted: Fri Aug 08, 2014 3:24 pm    Post subject: Reply with quote

creating /dev/822 -> sdc1 helped to grub2-mkconfig to work. Probably now i can migrate. But the reason of this renaming is still not clear.
Quote:
That is expected. Services are started by your init system. If you set init=/bin/bb, then your init system is not run. Instead, /bin/bb is run and it is your responsibility to use /bin/bb to start any required services.

Thanks for the explanation. I've realized that it's by intention. I was just checking if the computer will be reachable by ssh or not, because it's remote.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Fri Aug 08, 2014 8:03 pm    Post subject: Reply with quote

tot-to,

For lilo and grub1 to deal with root on raid, you really need an initrd.
With an initrd, adding mount by UUID for root is well documented.
_________________
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
freifunk_connewitz
Apprentice
Apprentice


Joined: 08 Feb 2006
Posts: 181

PostPosted: Tue Aug 12, 2014 10:27 am    Post subject: Reply with quote

hi all,

just to support the claim and to thank you all for the clarification so far: two of my machines are affected, too. 822 and 803 because root is at /dev/sdb2 resp. sda3.

but I have no problems with my bootloader. LILO did start to complain some time ago when issueing "dolilo", about some number "not found" but still completed the job and successfully updated the boot sector.

if this isn't an udev bug then it is an udev documentation bug, or what would you say?

cheers,
ffcw

btw: the problem's also mentioned here: https://forums.gentoo.org/viewtopic-t-997598.html
Back to top
View user's profile Send private message
tot-to
n00b
n00b


Joined: 09 Apr 2008
Posts: 21

PostPosted: Mon Aug 18, 2014 10:49 pm    Post subject: Reply with quote

There is an update on my case.

I've asked somebody who has physical access to boot the first computer with the gentoo minimal liveusb. Then i've mounted all my partitions to /mnt/gentoo together with it's subdirs and chrooted to /mnt/gentoo in the way described in the handbook.

The output of blkid and parted -l for both chrooted and non-chrooted shell are basically the same as in the installed system, but there are the differences:
Code:

livecd ~ # df
Filesystem     1K-blocks    Used Available Use% Mounted on
rootfs           8064428   60656   8003772   1% /
/dev               10240       4     10236   1% /mnt/gentoo/dev
tmpfs            8064428   60656   8003772   1% /
/dev/sdd1        7815240 5313660   2501580  68% /mnt/cdrom
/dev/loop0        162432  162432         0 100% /mnt/livecd
tmpfs            1612888     520   1612368   1% /run
shm              8064428       0   8064428   0% /dev/shm
tmpfs            8064428       0   8064428   0% /mnt/livecd/usr/portage
/dev/sdc2       30628800 3127040  25922856  11% /mnt/gentoo
livecd ~ # cat /proc/self/mountinfo
12 16 0:4 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
13 16 0:6 / /dev rw,nosuid,relatime - devtmpfs udev rw,size=10240k,nr_inodes=2015219,mode=755
14 13 0:11 / /dev/pts rw,relatime - devpts devpts rw,gid=5,mode=620
15 16 0:12 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
16 1 0:13 / / rw,relatime - tmpfs tmpfs rw
18 16 7:0 / /mnt/livecd ro,relatime - squashfs /dev/loop0 ro
19 16 8:49 / /mnt/cdrom ro,relatime - vfat /dev/sdd1 ro,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
20 16 0:14 / /run rw,nosuid,nodev,relatime - tmpfs tmpfs rw,size=1612888k,mode=755
21 13 0:15 / /dev/shm rw,nosuid,nodev,noexec,relatime - tmpfs shm rw
22 15 0:16 / /sys/fs/fuse/connections rw,nosuid,nodev,noexec,relatime - fusectl fusectl rw
23 18 0:17 / /mnt/livecd/usr/portage rw,relatime - tmpfs tmpfs rw
24 16 8:34 / /mnt/gentoo rw,relatime - ext4 /dev/sdc2 rw,data=ordered
25 24 0:4 / /mnt/gentoo/proc rw,relatime - proc proc rw
26 24 0:6 / /mnt/gentoo/dev rw,nosuid,relatime - devtmpfs udev rw,size=10240k,nr_inodes=2015219,mode=755
27 26 0:11 / /mnt/gentoo/dev/pts rw,relatime - devpts devpts rw,gid=5,mode=620
28 26 0:15 / /mnt/gentoo/dev/shm rw,nosuid,nodev,noexec,relatime - tmpfs shm rw
29 24 0:12 / /mnt/gentoo/sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
30 29 0:16 / /mnt/gentoo/sys/fs/fuse/connections rw,nosuid,nodev,noexec,relatime - fusectl fusectl rw
31 24 9:124 / /mnt/gentoo/var rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/md124 rw,discard,data=ordered
32 24 9:126 / /mnt/gentoo/home rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/md126 rw,discard,data=ordered
33 31 8:5 / /mnt/gentoo/var/log rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/sda5 rw,discard,data=writeback
34 24 9:125 / /mnt/gentoo/mnt/raid rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/md125 rw,discard,data=ordered
36 31 0:18 / /mnt/gentoo/var/tmp rw,nosuid,nodev,noatime,nodiratime - tmpfs tmpfs rw,size=8388608k
35 24 0:19 / /mnt/gentoo/tmp rw,nosuid,nodev,noatime,nodiratime - tmpfs tmpfs rw,size=2097152k

Code:

(chroot) livecd / # df
Filesystem      1K-blocks    Used  Available Use% Mounted on
rootfs           30628800 3127040   25922856  11% /
822              30628800 3127040   25922856  11% /
devtmpfs            10240       4      10236   1% /dev
/dev/sda1        30628800 3127040   25922856  11% /boot
/dev/md124     2637890216   76056 2503793952   1% /mnt/raid
/dev/md127      209283384 1649372  196979916   1% /var
/dev/sda5         3636508  271996    3160072   8% /var/log
/dev/md125        2030352    3132    1906036   1% /home
tmpfs             8388608      24    8388584   1% /var/tmp
tmpfs             2097152       0    2097152   0% /tmp
(chroot) livecd / # cat /proc/self/mountinfo
24 16 8:34 / / rw,relatime - ext4 /dev/sdc2 rw,data=ordered
25 24 0:4 / /proc rw,relatime - proc proc rw
26 24 0:6 / /dev rw,nosuid,relatime - devtmpfs udev rw,size=10240k,nr_inodes=2015219,mode=755
27 26 0:11 / /dev/pts rw,relatime - devpts devpts rw,gid=5,mode=620
28 26 0:15 / /dev/shm rw,nosuid,nodev,noexec,relatime - tmpfs shm rw
29 24 0:12 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
30 29 0:16 / /sys/fs/fuse/connections rw,nosuid,nodev,noexec,relatime - fusectl fusectl rw
31 24 9:124 / /var rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/md124 rw,discard,data=ordered
32 24 9:126 / /home rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/md126 rw,discard,data=ordered
33 31 8:5 / /var/log rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/sda5 rw,discard,data=writeback
34 24 9:125 / /mnt/raid rw,nosuid,nodev,noexec,noatime,nodiratime - ext4 /dev/md125 rw,discard,data=ordered
36 31 0:18 / /var/tmp rw,nosuid,nodev,noatime,nodiratime - tmpfs tmpfs rw,size=8388608k
35 24 0:19 / /tmp rw,nosuid,nodev,noatime,nodiratime - tmpfs tmpfs rw,size=2097152k


As one can see, the 822 disappeared from the mountinfo from both chrooted and non-chrooted shell and replaced with the correct name /dev/sdc2. But in the df output from the chrooted shell there is still 822 filesystem.

I've tried to run grub2-mkconfig -o /boot/grub/grub.cfg (without creation of any symlink) and then grub2-install /dev/sda and it succeed. I haven't try to reboot into installed system so far (i need a physically presence of someone there), but it looks like it should work. I'll post another update here when manage to reboot.

NeddySeagoon, thanks, i've read about that, but i've never used initrd and prefer not to start using it at least untill it'll be the only possible option.
Back to top
View user's profile Send private message
tot-to
n00b
n00b


Joined: 09 Apr 2008
Posts: 21

PostPosted: Tue Sep 16, 2014 6:13 pm    Post subject: Reply with quote

It seems like the software causing the renaming of root partition is lilo. After successful migration to grub2, df shows the normal path to partition: /dev/sdc2
So, problem kinda solved: at least I did what I wanted to do.
Back to top
View user's profile Send private message
tomaszg
n00b
n00b


Joined: 28 Oct 2008
Posts: 8

PostPosted: Wed Feb 18, 2015 6:46 pm    Post subject: Reply with quote

tot-to wrote:
creating /dev/822 -> sdc1 helped to grub2-mkconfig to work. Probably now i can migrate. But the reason of this renaming is still not clear.

Thanks for that workaround. Just saved my skin. Let me add that in my case, I had to create symlink in current directory, not in /dev.

BTW. I would still prefer to use LILO, but couldn't find a way to do it with partitions >2TB.
_________________
AMD II X3 245 | 2GB | GeForce 8800 | HDD 2.5TB w sumie | Asus Xonar DX | bez obudowy
Back to top
View user's profile Send private message
freifunk_connewitz
Apprentice
Apprentice


Joined: 08 Feb 2006
Posts: 181

PostPosted: Mon May 11, 2015 5:59 pm    Post subject: Reply with quote

for the sake of completeness: in my case some update solved the problem. /dev/root is displayed correctly in mountinfo and mounts or df -h. no hex numbers anymore.

my setup:
lilo-24.0-r1
openrc-0.13.11
kernel 3.18.11


@tot-to: as it seems to be solved for you, too > mark as solved?
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