[Solved] Can't mount former /home in fresh installed Arch_X86-64

mibadt · 2012-07-21 13:41:25

Hi,
Due to some problems I've decided to fresh install my Arch. During the fresh install I've created a new (temp) ext3 /home partition on USB memory stick and configured my new fstab to mount the former home as "old_home".
Although I can read that partition (and open files in it) while running a live ubuntu CD, Arch refuses to mount that partition (see terminal output below) maybe thinking it's ext4?
Please advise..

Thanks

----------copy of fstab and terminal output-------------------------

# cat /etc/fstab 
# 
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
tmpfs           /tmp    tmpfs   nodev,nosuid    0       0
UUID=102eb0bb-d99b-455f-af27-90e038694e92 / ext3 defaults 0 1
UUID=1265bb91-8151-4e8b-9841-5dd10909dc6a /boot ext2 defaults 0 1
UUID=19746a40-d8a0-45e4-8c4b-15c70d3c4dab swap swap defaults 0 0
UUID=27f96184-d728-4eba-b588-6ac8952ff37c /var ext3 defaults 0 1
UUID=2c92685d-050a-4023-aab2-b8a91f077f6b /images_sda xfs defaults 0 1
UUID=615ad9dc-34c5-4c20-b687-46de6f66f7a5 /lin_back xfs defaults 0 1
UUID=67AD726A113E664B /windows ntfs-3g defaults 0 1
UUID=71AF0020700759D6 /photos ntfs-3g defaults 0 1
UUID=9d6eb8a2-be83-477b-976e-e6d1ad560f8d /old_home ext3 defaults 0 1
UUID=aea9da03-1f4b-46dd-a814-a860be883204 /home ext3 defaults 0 1

[root@Miki_Arch miki]# mount /windows/

[root@Miki_Arch miki]# mount /photos/ 

[root@Miki_Arch miki]# mount /old_home/
mount: wrong fs type, bad option, bad superblock on /dev/sdb3,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
[root@Miki_Arch miki]# dmesg | tail
[   10.832851] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   14.462198] r8169 0000:06:00.0: eth1: link up
[   14.464524] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   24.660704] eth1: no IPv6 routers present
[   44.778743] EXT4-fs (sdb2): re-mounted. Opts: commit=0
[   45.410494] EXT4-fs (sda6): re-mounted. Opts: commit=0
[   47.089525] EXT4-fs (sdc1): re-mounted. Opts: commit=0
[   78.447668] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[  789.061538] fuse init (API version 7.18)
[  804.346209] EXT4-fs (sdb3): couldn't mount as ext3 due to feature incompatibilities

Last edited by mibadt (2012-07-22 01:56:24)

DSpider · 2012-07-21 14:01:58

Whenever you format a partition (or create one, in your case), a new UUID is also created. Check your /etc/fstab against these:

$ ls -lF /dev/disk/by-uuid/
$ blkid

And "mount something" isn't very accurate. It should be "mount something something".

Get the device name from "fdisk -l" (or from one of the above commands) and use:

# mount /dev/sdxY /old_home

Also, why are there so many users that add "1" at the end of every entry in their fstab? Where are you getting your information from? For fuck's sake, only the "/" entry needs "1". Everything else should have either "2" or "0". https://wiki.archlinux.org/index.php/Fs … efinitions

mibadt · 2012-07-21 14:16:49

Dear DSpider,
Thanks for the fast response.
my /old_home resides on sdb3, its UUID in fstab is CORRECT, and as you can see blkid recognizes it as ext4 -I'll recheck this, because I remember it's ext3.
BTW can I cause a permanent damage to that partition if I modify fstab to ext4 for that partition and try?
My fstab has been automatically created during installation (except for the ntfs-3g entries)...

----copy of terminal------

# ls -lF /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jul 21 16:18 102eb0bb-d99b-455f-af27-90e038694e92 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Jul 21 16:18 1265bb91-8151-4e8b-9841-5dd10909dc6a -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jul 21 16:18 19746a40-d8a0-45e4-8c4b-15c70d3c4dab -> ../../sda5
lrwxrwxrwx 1 root root 10 Jul 21 16:18 27f96184-d728-4eba-b588-6ac8952ff37c -> ../../sda6
lrwxrwxrwx 1 root root 10 Jul 21 16:18 2c92685d-050a-4023-aab2-b8a91f077f6b -> ../../sdb7
lrwxrwxrwx 1 root root 10 Jul 21 16:18 5367857732AD46CD -> ../../sdb5
lrwxrwxrwx 1 root root 10 Jul 21 16:18 5CA8EEAD5102AA5E -> ../../sdb6
lrwxrwxrwx 1 root root 10 Jul 21 16:18 615ad9dc-34c5-4c20-b687-46de6f66f7a5 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jul 21 16:18 67AD726A113E664B -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 21 16:18 71AF0020700759D6 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jul 21 16:18 9d6eb8a2-be83-477b-976e-e6d1ad560f8d -> ../../sdb3
lrwxrwxrwx 1 root root 10 Jul 21 16:18 aea9da03-1f4b-46dd-a814-a860be883204 -> ../../sdc1

[root@Miki_Arch etc]# blkid
/dev/sda1: LABEL="Windows" UUID="67AD726A113E664B" TYPE="ntfs" 
/dev/sda2: LABEL="Lin_Back" UUID="615ad9dc-34c5-4c20-b687-46de6f66f7a5" TYPE="xfs" 
/dev/sda3: LABEL="Photos" UUID="71AF0020700759D6" TYPE="ntfs" 
/dev/sda5: LABEL="SWAP" UUID="19746a40-d8a0-45e4-8c4b-15c70d3c4dab" TYPE="swap" 
/dev/sda6: LABEL="VAR" UUID="27f96184-d728-4eba-b588-6ac8952ff37c" TYPE="ext3" 
/dev/sdb1: LABEL="BOOT" UUID="1265bb91-8151-4e8b-9841-5dd10909dc6a" TYPE="ext2" 
/dev/sdb2: LABEL="ROOT" UUID="102eb0bb-d99b-455f-af27-90e038694e92" TYPE="ext3" 
/dev/sdb3: LABEL="HOME" UUID="9d6eb8a2-be83-477b-976e-e6d1ad560f8d" TYPE="ext4" 
/dev/sdb5: LABEL="LR_Cache" UUID="5367857732AD46CD" TYPE="ntfs" 
/dev/sdb6: LABEL="Win_Swap" UUID="5CA8EEAD5102AA5E" TYPE="ntfs" 
/dev/sdb7: LABEL="Images_sda" UUID="2c92685d-050a-4023-aab2-b8a91f077f6b" TYPE="xfs" 
/dev/sdc1: LABEL="HOME" UUID="aea9da03-1f4b-46dd-a814-a860be883204" TYPE="ext3"

mibadt · 2012-07-21 14:33:58

Thanks again.
My mistake. my /old_home has indeed been ext4>
Regards,

DSpider · 2012-07-21 14:55:11

By the way, you should consider adjusting your fstab (back it up first) to look more like the examples from the fstab wiki page. From a terminal, use the space bar and the Tab key to align them properly, because those entries are very difficult to read.

Here's mine:

# <file system>                <dir>           <type>  <options>                            <dump>  <pass>

tmpfs                          /tmp            tmpfs   nodev,nosuid,noexec                     0       0

/dev/sdb1                      /               ext4    defaults,noatime                        0       1
/dev/sdb3                      /media/Storage  ext4    defaults,noatime,noexec                 0       2
/dev/sda2                      /media/Backup   ext4    defaults,noatime,noexec                 0       2

Finally, reboot and see if there are any issues.

PS: Don't forget to mark it as solved.

mibadt · 2012-07-22 01:56:02

Thanks again!

Arch Linux

#1 2012-07-21 13:41:25

[Solved] Can't mount former /home in fresh installed Arch_X86-64

#2 2012-07-21 14:01:58

Re: [Solved] Can't mount former /home in fresh installed Arch_X86-64

#3 2012-07-21 14:16:49

Re: [Solved] Can't mount former /home in fresh installed Arch_X86-64

#4 2012-07-21 14:33:58

Re: [Solved] Can't mount former /home in fresh installed Arch_X86-64

#5 2012-07-21 14:55:11

Re: [Solved] Can't mount former /home in fresh installed Arch_X86-64

#6 2012-07-22 01:56:02

Re: [Solved] Can't mount former /home in fresh installed Arch_X86-64

Board footer