You are not logged in.
Pages: 1
Hi all,
Been learning linux the last couple weeks so pardon the obvious noobiness. Got sick of ubuntu quite quickly and decided to take the plunge to Arch, upgraded to a SSD soon after my first successful install of Arch and so now I'm trying to install with GPT and Grub2.
Done lots of reading etc, got to the point of chrooting into the installed system to install and configure grub2 but dont understand/know how to exit the chroot and unmount dev, proc, sys. When i try to umount I get a "device is busy" error. I've searched everywhere and am just lost.
Mike.
Offline
Hey mikeau,
in what order do you try to unmount the devices and filesystem? That matters a lot.
A helpful link may bei the wiki Chroot article, there you should see what I mean by "order matters".
P.S.: welcome to Arch Linux
Last edited by kritter (2012-01-16 14:41:25)
My try at blogging // IRC: kritztopf@freenode
Offline
Take a peek over this thread: https://bbs.archlinux.org/viewtopic.php?id=133170
Offline
By order do you mean unmounting the sub mounts first? Or is there an actual order as in unmounting proc before sys?
Took a look at the link Kaustic, that's pretty much exactly how I went about it, exited and then rebooted. But theres still mounts after the reboot i can't get rid of.
Offline
Just for clarity, are there normally meant to be any mounts present?
Offline
By order do you mean unmounting the sub mounts first? Or is there an actual order as in unmounting proc before sys?
Yes, I meant the submounts with order - submounts first, then the normal mounts.
After a reboot, running mount without parameters should yield in a relatively brief output where "only" /proc, /sys, /dev, /run and your file systems are mounted, your mileage may vary. Could you manage to paste the output of running mount?
Greetings
My try at blogging // IRC: kritztopf@freenode
Offline
The output from mount is:
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=480166,mode=775)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=775)
/dev/disk/by-uuid/51959e38-d39a-491c-856f-a74b6ee1499f on / type ext4 (rw,noatime,user_xattr,acl,barrier=1,data=ordered,discard)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
/dev/sda4 on /home type ext4 (rw,noatime,discard)
Offline
I can umount everything except proc, sys, dev, run and /, which i expect is normal. But after i reboot all the other mounts come back. Are there meant to be that many mounts or is it actually a problem with the chroot i done?
Offline
Looks pretty normal to me. My list is longer because I've got more partitions and there's something which seems to be related to fuse. Not that I know much but everything in your list corresponds to something in mine though not vice-versa!
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Oh lol, was that the problem? Yes, it's normal, this is my output:
mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
/sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=505871,mode=755)
/run on /run type tmpfs (rw,nosuid,nodev,relatime,size=10240k,mode=755)
/dev/sda3 on / type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
/dev/sda1 on /boot type ext2 (rw,relatime,errors=continue)
/dev/sda4 on /home type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
edit: this was a bog-standard install from the ncurses UI, no chrooting involved.
Last edited by Earnestly (2012-01-17 21:59:28)
Offline
Pages: 1