[Solved] Harddisk fstab

Hi, i got 2 Harddisk's
1 x SSD with Archlinux
1 x HDD for Musik, pictures etc.
when i dont write it at Fstab (HDD) i must ever when i wanna enter it give in the root pw. this sucks.
when i write it into fstab, i cant enter it? Oo
Harddisk : ntfs
(Sorry for bad english :S)
Last edited by Keta (2011-10-22 07:13:19)

jasonwryan wrote:
To mark a thread as solved, please edit the first post in the thread and prepend [Solved] to the title.
For editing the daemons line in your rc.conf, see https://wiki.archlinux.org/index.php/Be … NS_section
yes, i know but i dont know where i must enter "fuse" or is that wayne?
when i enter it bevor @alsa?

Similar Messages

(solved) /etc/fstab does not list all the discs

there are too usb discs: /dev/sdc1 and /dev/sdd1
besides there are two hd too: /dev/sdb and /dev/sda
arch linux has been installed on /dev/sdb
1) the /etc/fstab is like this - no /dev/sda, no /dev/sdc1 neither /dev/sdd1 listed
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=6ea90d2a-f445-4dc2-88ae-cdedcd2be530
/dev/sdb1 / ext4 rw,relatime 0$
# UUID=6b1c3042-97aa-46b6-a6cb-b2b9837748a9
/dev/sdb2 /home ext4 rw,relatime 0$
# UUID=d039ad96-6474-4492-a9b0-abaf45a8f8c3
/dev/sdb3 none swap defaults 0$
2) the result of # lsblk -f is:
[root@arch cezar]# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs 9C7AC58F7AC5671C
├─sda2 ext4 33e515b1-4f01-4d50-a0c3-91621b80dbcc
└─sda3 swap 5b3657af-7363-4f08-be60-7cdcfb277cfb
sdb
├─sdb1 ext4 6ea90d2a-f445-4dc2-88ae-cdedcd2be530 /
├─sdb2 ext4 6b1c3042-97aa-46b6-a6cb-b2b9837748a9 /home
└─sdb3 swap d039ad96-6474-4492-a9b0-abaf45a8f8c3 [SWAP]
sdc
└─sdc1 ntfs SAMSUNG 0E604C85604C758D /run/media/cezar
sdd
└─sdd1 ntfs 083818523818415C /run/media/cezar
sr0
3) I tried to add all the discs on /etc/fstab by hand, but the system crashed and I had to comment the lines I had added
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=9C7AC58F7AC5671C
#/dev/sda1 /mnt/win7 ntfs defaults 0 0
# UUID=33e515b1-4f01-4d50-a0c3-91621b80dbcc
#/dev/sda2 / ext4 auto,rw,relatime,users 0 1
# UUID=5b3657af-7363-4f08-be60-7cdcfb277cfb
#/dev/sda3 none swap defaults 0 0
# UUID=6ea90d2a-f445-4dc2-88ae-cdedcd2be530
/dev/sdb1 / ext4 rw,relatime 0 1
# UUID=6b1c3042-97aa-46b6-a6cb-b2b9837748a9
/dev/sdb2 /home ext4 rw,relatime 0 2
# UUID=d039ad96-6474-4492-a9b0-abaf45a8f8c3
/dev/sdb3 none swap defaults 0 0
# UUID=0E604C85604C758D
#/dev/sdc1 /run/media/cezar ntfs auto,rw,relatime,users 0 1
# UUID=083818523818415C
#/dev/sdd1 /run/media/cezar ntfs auto,rw,relatime,users 0 1
how can that be fixed in order to all the discs be listed? thanks
Last edited by cezarrangel (2014-06-25 18:23:24)

ok trilby concerning swap. I will check the /run/media/cezar because these are the two differente usb discs. thank you so much.
That is it Trilby, it has been solved: #mkdir /mnt/samsung1 for /dev/sdc1 and #mkdir /mnt/samsung2 for /dev/sdd1; I have also #cfdisk /dev/sda and deleted the swap partition over there.
Last edited by cezarrangel (2014-06-25 18:22:55)

[SOLVED] Systemd-fstab-generator: Out of memory...

Hello using multilib lib32-systemd 208-1 and systemd208-1... I have a problem where I will boot and it hangs at mounting drives:
systemd-fstab-generator[135]: Out of Memory.
systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
I have chrooted in and upgrade stuff and modified my fstab and grub config stuff a bit since I was getting the /root read only problem.. (changed to rw) and it works... However I cannot seem to find where this problem is coming from and the only thing that I can think is that systemd cannot parse /etc/fstab correctly.. My fstab has labels like: Label=/home, Label=/, Label=/var, Label=/boot, etc... it was fine till a couple days ago... Using kernel 3.11.3 x86_64...
Last edited by adramalech (2013-10-06 20:50:20)

Okay so here is my fstab:
tmpfs /dev/shm tmpfs defaults,noatime 0 0
none /tmp tmpfs defaults,noatimenodev,nosuid,mode=1777 0 0
/dev/sdd2 none swap sw 0 0
proc /proc proc nodev,noexec,nosuid 0 0
# /dev/sdc2 UUID=0cf15f7d-a6e0-4b4b-8ca0-e3fa32ca79f5
LABEL=/ / ext4 errors=remount-ro,defaults,rw,discard,noatime,data=ordered 0 1
# /dev/sdc1 UUID=22cee2cf-55fa-4721-b3da-68191c477643
LABEL=/boot /boot ext2 defaults 0 0
# /dev/sdc3 UUID=79bcca95-af9a-4f9f-99ab-78020a3960da
LABEL=/home /home ext4 errors=remount-ro,defaults,rw,noatime,discard,data=ordered 0 1
/dev/sdd3 /var ext4 errors=remount-ro,defaults,rw,relatime,data=ordered 0 2
LABEL=Storage /media/Storage ext4 errors=remount-ro,defaults,rw,relatime,data=ordered 0 2
***EDIT#1***
Storage is a WD 2TB Caviar green, same with /var and swap, /boot, /home, / are on an M4 128GB SSD, and the rest are just stuff put in tmpfs and proc like normal... Tried keeping the heavily read/write data off of the ssd to conservative with writes
I am wondering if I can not just update my damn Labels in fstab and through gparted and call it a day...
***EDIT#2***
Okay so I only went through and thought to update packages that needed updating since that might have fixed the problem... I saw an update for lib32-systemd 208-1 and some other non-essentials stuff so updated rebooted and still same problem I have used this fstab for a considerable amount of years using arch and then back using gentoo for a couple years with no problems... Wondering if now it is being picky with labels...
Last edited by adramalech (2013-10-06 19:19:49)

[SOLVED]systemd-fstab-generator and syslog error?

here is the bootup error message:
Nov 2 07:27:58 localhost [ 9.207762] systemd-fstab-generator[151]: Failed to create unit file: File exists
Nov 2 07:27:58 localhost [ 10.119699] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
Nov 2 07:27:58 localhost [ 10.544789] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 07:27:58 localhost [ 10.544974] systemd[1]: Failed to listen on Syslog Socket.
and my fstab is here:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb5 / jfs defaults 0 1
/dev/sdb6 /home ext4 defaults,user_xattr 0 1
/dev/sdb7 /var reiserfs defaults 0 1
/dev/sdb8 /tmp reiserfs defaults 0 1
Last edited by frat (2012-11-02 03:21:07)

systemd-fstab-generator is fixed,thank you.
syslog errors still:
Nov 2 10:29:44 localhost [ 10.051816] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 10:29:44 localhost [ 10.052000] systemd[1]: Failed to listen on Syslog Socket.
#systemctl status syslog
syslog.service
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)
#systemctl status syslog.socket
syslog.socket - Syslog Socket
   Loaded: loaded (/usr/lib/systemd/system/syslog.socket; static)
   Active: inactive (dead)
   Docs: man:systemd.special(7)
   http://www.freedesktop.org/wiki/Software/systemd/syslog
   CGroup: name=systemd:/system/syslog.socket
any advice?
Last edited by frat (2012-11-02 02:56:37)

[Solved] Harddisks: lot of output in both dmesg and kernel.log

Situation:
Since a few weeks I'm having a new little home server. An intel atom d525 cpu with 2gb ram, which seems to be a nice compromise between speed, price and power consumption. I'm wanting to use this server mainly as file server (backup, bulk data), download server, automatic backups, video streaming for the TV and my computer, mpd server and just for some experiments.
For the data I've got 2 disks, 2Tb each in a mdadm raid1 set with a layer of lvm and ext4 as the filesystem. I've used a brand new usb stick of 8Gb for the / filesystem. I know usb sticks are not made to be used as a / filesystem, but it should work and when the stick wears out (years?) I can replace it easily and cheap.
First signs of problems:
After the arch install I went ahead and installed some services. Everything seemed to be fine and I was really happy with the new server. Until after 2-3 days uptime it 'crashed'. I didn't bother looking in the logs or whatever, so I just gave it a fine reset and it went up without troubles. Again 2-3 days later it crashed again. I plugged in the monitor again and it seemed to be the / file system giving some troubles. After some io errors on the / it remounted itself read only, which gives me an unusable server. After some ext4 checks, it happened again the reboot after.
After that I decided it must be either the usb stick or the usb controller be doing something fishy. I've put the / on an old 2gb usb stick and since then it seems to be running fine (uptime now a weak).
Untill the / is full:
Strange, the 2gb / is full whilst a week ago when moving the arch install from the old usb stick, it only used about 1300Mb. After some smart usage of du and find I found out that the logs were to blame. Both the kernel.log en everything.log were 300+mb.
I hope there is somebody here who can help me figure out why the logs are getting filled with these messages and how to fix it. And to tell me if there is a serious problem with the raid1 set (mounted on /home), since I need to be able to rely on it to some extends.
raid set:
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
/dev/sdc1 is the usb stick mounted on /
dmesg:
nmbd(11212): dirtied inode 801 (wins.dat.11212) on sdc1
nmbd(11212): dirtied inode 801 (wins.dat.11212) on sdc1
jbd2/sdc1-8(725): WRITE block 1584712 on sdc1
nmbd(11212): dirtied inode 72329 (?) on sdc1
flush-8:32(1309): WRITE block 3072016 on sdc1
jbd2/sdc1-8(725): WRITE block 1584720 on sdc1
jbd2/sdc1-8(725): WRITE block 1584728 on sdc1
jbd2/sdc1-8(725): WRITE block 1584736 on sdc1
jbd2/sdc1-8(725): WRITE block 1584744 on sdc1
jbd2/sdc1-8(725): WRITE block 1584752 on sdc1
jbd2/sdc1-8(725): WRITE block 1584760 on sdc1
jbd2/sdc1-8(725): WRITE block 1584768 on sdc1
jbd2/sdc1-8(725): WRITE block 1584776 on sdc1
jbd2/sdc1-8(725): WRITE block 1584784 on sdc1
jbd2/sdc1-8(725): WRITE block 1584792 on sdc1
jbd2/sdc1-8(725): WRITE block 1584800 on sdc1
syslog-ng(1224): dirtied inode 5027 (syslog-ng.persist) on sdc1
syslog-ng(1224): dirtied inode 5027 (syslog-ng.persist) on sdc1
jbd2/sdc1-8(725): WRITE block 1584808 on sdc1
flush-8:32(1309): WRITE block 3668432 on sdc1
flush-8:32(1309): WRITE block 3668440 on sdc1
flush-8:32(1309): WRITE block 3668448 on sdc1
flush-8:32(1309): WRITE block 3668456 on sdc1
flush-8:32(1309): WRITE block 3668464 on sdc1
flush-8:32(1309): WRITE block 3668472 on sdc1
flush-8:32(1309): WRITE block 3668480 on sdc1
flush-8:32(1309): WRITE block 3668488 on sdc1
flush-8:32(1309): WRITE block 3668496 on sdc1
syslog-ng(1224): dirtied inode 72847 (kernel.log) on sdc1
syslog-ng(1224): dirtied inode 72847 (kernel.log) on sdc1
flush-8:32(1309): WRITE block 3684888 on sdc1
flush-8:32(1309): WRITE block 3684896 on sdc1
flush-8:32(1309): WRITE block 3684904 on sdc1
flush-8:32(1309): WRITE block 3684912 on sdc1
flush-8:32(1309): WRITE block 3684920 on sdc1
flush-8:32(1309): WRITE block 3684928 on sdc1
flush-8:32(1309): WRITE block 3684936 on sdc1
flush-8:32(1309): WRITE block 3684944 on sdc1
flush-8:32(1309): WRITE block 3684952 on sdc1
flush-8:32(1309): WRITE block 1309280 on sdc1
flush-8:32(1309): WRITE block 1136 on sdc1
syslog-ng(1224): dirtied inode 72851 (everything.log) on sdc1
syslog-ng(1224): dirtied inode 72851 (everything.log) on sdc1
syslog-ng(1224): dirtied inode 72851 (everything.log) on sdc1
dmesg(11213): READ block 265816 on sdc1
kernel.log
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407424 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407432 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407440 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407448 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407456 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407464 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407472 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407480 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407488 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407496 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407504 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407512 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407520 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407528 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407536 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407544 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407552 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407560 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407568 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407576 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407584 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407592 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407600 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407608 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407616 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407624 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407632 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407640 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407648 on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 40370181 (sabnzbd.log) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 40370181 (sabnzbd.log) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 40370181 (sabnzbd.log) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 46139255 (flying.wild.alaska.s01e02.720p.hdtv.x264-momentum.part18.rar) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 46139255 (flying.wild.alaska.s01e02.720p.hdtv.x264-momentum.part18.rar) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 46139255 (flying.wild.alaska.s01e02.720p.hdtv.x264-momentum.part18.rar) on dm-0
Jan 24 19:34:58 nas kernel: md127_raid1(1074): WRITE block 8 on sdb1
Jan 24 19:34:58 nas kernel: md127_raid1(1074): WRITE block 8 on sda1
Jan 24 19:34:59 nas kernel: bash(11231): READ block 916240 on sdc1
Jan 24 19:34:59 nas kernel: tail(11231): READ block 916272 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 3692640 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 3709104 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588128 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588136 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588144 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588152 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588160 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588168 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588176 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588184 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588192 on sdc1
Especially the lines with 'dirtied inode' do worry me .
Ps: I do know that running archlinux on a server is not 'smart'. Same for using a usb flash device for /. Both are not considered smart choices, but for a home server which doesn't need to have a 100% uptime not always a bad choice and are not the topic of discussion .
Last edited by evert_ (2011-01-24 21:21:55)

There are both log entries about the flash disk and the raid 1 set. The flash disk (sdc) entries don't seem to be critical, but I have no clue why they appeared...
I make a regular backup of my / to protect myself against loss of data due to wear some day. I've ran a little server in the past on a 4gb usb flash medium for several years, without any problems what so ever.
Last edited by evert_ (2011-01-24 18:52:54)

[SOLVED] FSTAB and File Permissions

Hi Guru's
I'm a new Arch user migrating from Ubuntu.
I have one hard drive partitioned as follows:
SDA1 NTFS
SDA2 / ext3
SDA3 / swap
SDA4 NTFS
I also have a semi permanent USB Hard Drive and various other USB devices which seem to be mounting fine under autofs. When / if, I solve my fstab problem, I will look into Udev to give these devices static names.
My problem is that no matter what I try, I cannot make the two NTFS drives accessible by a normal user (me). The following is from my current fstab file:
/dev/sda1 /mnt/sda1 ntfs rw,user,auto,uid=1000,gid=100,sync,umask=000 # my uid and the users group
/dev/sda4 /mnt/sda4 ntfs rw,user,auto,uid=1000,gid=100,sync,umask=000
This is one of dozens of combinations I have tried based on research and "RTFM". I just keep getting more confused. The directory entries show me as the owner, rw permissions and belonging to the user group, the only problem is that I can not write to those partitions as a normal user.
Any suggestions would be greatly appreciated.
Any suggestions for links that tie in how fstab, autofs, udev and hal work together. I have seen links on all of them, but would like to see a brief overview on how they work together. As you can see, I'm one of those linux noobs.
Thanks
Larry
Last edited by ljshap (2008-05-27 11:04:44)

Hi luca,
Thanks for the link. I made the following changes:
/dev/sda1 /mnt/sda1 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_PH.utf8 0 0
/dev/sda4 /mnt/sda4 ntfs-3g users,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_PH.utf8 0 0
Except for the locale, its working great. I still have to mount sda1 as root, which is probably a good idea for the other OSes partition. If I change it to auto it does mount automatically but thats flirting with danger
On to Udev
Thanks Again
Larry

Windows partition permissions problem

i have a fat32 partition that i use to be able to see files whenever i'm on windows or linux. my fstab is as follow:
/dev/discs/disc0/part4 /mnt/windows vfat rw,user,auto 0 0
but if i do
[nbcjr@universo ~]$ touch /mnt/windows/lin
touch: cannot touch `/mnt/windows/lin': Permission denied
what's going on?? how do i set this partition to be mounted automatically and to permit any user (or at least my main user) to write any file on it???
thanks!

hi!
i also have a ntfs partition that sometimes i want to get something from. i mount it as read only, but only root has permission to acess it. i don't know how to solve this.
fstab
/dev/discs/disc0/part1 /mnt/ntfs ntfs ro,user,noauto,unhide 0 0
windows is my fat partition, ntfs is the ntfs one.
[nbcjr@universo mnt]$ ls -lah
total 42K
drwxr-xr-x 10 root root 248 2005-09-20 02:15 .
drwxr-xr-x 19 root root 464 2005-09-18 23:07 ..
drwxr-xr-x 2 root root 48 2005-06-17 02:43 captive-noname
dr-xr-xr-x 2 root root 2.0K 2005-09-30 12:07 cd
drwxr-xr-x 2 root root 48 2005-08-24 17:58 dvd
drwxr-xr-x 2 root root 48 2005-08-24 17:58 fl
drwxr-xr-x 2 root root 48 2005-06-22 22:00 floppy
dr-x------ 1 root root 8.0K 2005-09-21 23:39 ntfs
drwxr-xr-x 2 root root 48 2005-09-20 02:15 usb
drwxr-xr-x 9 nbcjr root 32K 1969-12-31 21:00 windows
even after
[root@universo nbcjr]# chmod 755 /mnt/ntfs/
chmod: changing permissions of `/mnt/ntfs/': Read-only file system
it stays like that. thanks a lot!

How to mount a CIFS file system in fstab?[SOLVED]

I want a CIFS share to be auto mounted on linux startup.
If I add a line to /etc/rc.local, it works well:
mount -t cifs //192.168.0.10/alien /home/alien -o user=alien,passowrd=alien,uid=1000,gid=1000
But, if I append a line to /etc/fstab, it doesn't work:
//192.168.0.10/alien /home/alien cifs _netdev,users,user=alien,passowrd=alien,uid=1000,gid=1000 0 0
I think may be fstab is before network available. But I am not sure, since I notice some other
linux system has NFS entry in fstab and works well.
Any ideas?
Last edited by vistastar (2011-12-23 11:00:29)

Please mark solved thread as [SOLVED]. Thanks.
https://wiki.archlinux.org/index.php/Fo … ow_to_Post

[Solved] Inconsistency in device naming concerning mount/fstab

This is not a problem that needs to be solved, but rather a gap in my understanding of a mechanism.
I have several partitions mounted in my fstab, they are identified by UUID.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump><pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
UUID=0767c51a-0ba8-405e-ac98-106182fe4d83 /tmp ext4 noexec,rw,noatime,nodiratime 0 2
UUID=0ba14b78-1b36-4857-92ae-8b1ca41264b6 /boot ext2 defaults 0 1
UUID=4eb07abb-25b0-4683-badf-8d556b536d9c / ext4 defaults 0 1
UUID=e3fe5429-379b-4b6d-a01e-e30aa85784e2 /home ext4 defaults 0 1
UUID=e7fda340-ca00-4c4c-b42e-cfba13a3abbe swap swap defaults 0 0
UUID=e3ae11a4-b602-4ea2-bbf7-8c8c9dea52a6 /mnt/Esther ext4 defaults,rw,noatime,nodiratime 0 2
UUID=55525a1b-386b-4390-8f47-b078b0b2c06e /mnt/Ballamb ext4 defaults,rw,noatime,nodiratime 0 2
UUID=b71cfb8d-a4eb-4ded-a65b-fbc2db102332 /mnt/Galbadia ext4 defaults,rw,noatime,nodiratime 0 2
When all drives are mounted, they show up as mounted by device name (/dev/sd*), only / is displayed as mounted by UUID.
$ 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=386283,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c on / type ext4 (rw,relatime,barrier=1,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
/dev/sdc2 on /tmp type ext4 (rw,noexec,noatime,nodiratime)
/dev/sda1 on /boot type ext2 (rw)
/dev/sda4 on /home type ext4 (rw)
/dev/sdb1 on /mnt/Esther type ext4 (rw,noatime,nodiratime)
/dev/sdc1 on /mnt/Ballamb type ext4 (rw,noatime,nodiratime)
/dev/sdd1 on /mnt/Galbadia type ext4 (rw,noatime,nodiratime)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/xy/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=xy)
$ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
udev 10M 0 10M 0% /dev
run 10M 192K 9,9M 2% /run
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c 68G 8,5G 56G 14% /
shm 1,5G 4,0K 1,5G 1% /dev/shm
/dev/sdc2 289G 194M 274G 1% /tmp
/dev/sda1 251M 17M 222M 7% /boot
/dev/sda4 849G 62G 745G 8% /home
/dev/sdb1 1,8T 1,5T 223G 88% /mnt/Esther
/dev/sdc1 1,1T 223G 810G 22% /mnt/Ballamb
/dev/sdd1 1,8T 390G 1,4T 23% /mnt/Galbadia
Now I feel the urge to know why. Neither the mount nor the fstab manfile gave me insight on this one. So, what's behind this?
Last edited by Awebb (2011-10-08 17:51:26)

Now I feel stupid for not searching properly. Solved. Thanks, karol.
EDIT: So, in other words, if the UUID is passed by Grub, it shows as UUID in the system,
http://projects.archlinux.org/mkinitcpi … 3afd7e0001
So it was solved about a year ago? Well...
Last edited by Awebb (2011-05-29 14:12:06)

Systemd and fstab[solved easily]

hey guys,
another computer, another question about the switch to systemd.
My computer won't boot if there is anything in fstab besides / .
anything else in there (mostly removable stuff by uuid), and boot hangs. I'm once again missing something obvious, I'm sure.
As far as I can tell everything else is error-free and working fine.
any ideas? thanks!
Last edited by scrawler (2012-10-29 02:11:23)

WorMzy wrote:Posting your fstab might help..
+1
Solved or not, providing more info will very likely help others finding this thread via a search. Please post your before and after /etc/fstab to the thread when you get a chance.
Last edited by graysky (2012-10-29 14:06:01)

[Solved] systemd and fstab with /var bind

I'm having some troubles migrating to systemd. I have the following in my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid,size=8G 0 0
UUID=2bedbb1a-015f-4c46-ab48-f3ffc55b154b /boot ext2 defaults 0 1
#UUID=2c5f02a3-c8a1-45ed-92f4-dc09e56c09d7 /var ext4 discard,noatime 0 1
UUID=2c5f02a3-c8a1-45ed-92f4-dc09e56c09d7 /mnt/mythtv ext4 discard,noatime 0 1
UUID=910898cb-2d67-4689-ba51-358d94b2531d swap swap defaults 0 0
UUID=cac6ccea-456a-4c09-a1db-57cec02b238d / ext4 discard,noatime 0 1
/dev/mapper/VolGroupArray-lvmedia /mnt/media ext4 auto 0 0
mnt/media/var /var bind defaults,bind 0 0
(/dev/sda is an ssd disk so I decided to move /var to my software raid and lvm disks)
However this doesn't seem to work anymore with systemd as it doesn't get mounted automatically anymore. I've setup a debug console, there I can mount it by simply typing mount /var and then I can manually start the services that failed.
didn't actually solve the bind stuff, but decided to make a new partition on the lvm disk and mount /var there.
Last edited by blahbla77 (2012-11-18 13:58:13)

Are you really missing a leading / from the last line?

Multiple /dev designator fstab(solved in udev rules)

Is it possible to enable multiple USB ID's in fstab as follows;
/dev/sc[0-9] /cdrom iso9660 ro,users,noauto 0 0
The cdrom is connected on an IDE-USB cable.
The idea is to enable audio CD regardless of the state of the USB selection process.
Adding an entry for each USB designator is an option.

Entered the following in CD Symlinks;
==============================================================
BUS=="scsi", KERNEL="scd[0-9]", ACTION=="add", IMPORT="/sbin/cdrom_id --export $tempnode"
=============================================================
This seems to have solved the selection for audio cd's in USB-cdrom, regardless of the designator.

[solved] fstab entry for user mounting of iso files?

fstab entry for user mounting of iso files?
I've seen it before but I can't seem to find it again.
Last edited by eilenbeb (2010-03-21 20:11:40)

I did, but couldn't find what I was looking for.
I got fuseiso to work, and that will do the trick, so I'm marking this one solved.
(I simply had to give 'others' write access to the mount point)
Last edited by eilenbeb (2010-03-21 20:15:09)

[SOLVED] Copy whole harddisk content to bigger one

Hello,
till now in my little homeserver there is a 80GB harddisk, recently I found a 200GB one and want to switch it, without having to reinstall archlinux.
I read about "dd" which can copy a whole harddisk byte-by-byte.
How do I use it?
Do I have to format the bigger harddisk first?
Do I have to switch runlevel to 1, so that no programms or e.g. random cronjobs run in that dd process? Or do I have to do it via a live-linux-cd, so that no virtual proc directories are mounted which would also be copied?
Or can I just attach the bigger disk and run dd from normal runlevel?
After copying I assume I have to resize the partition on the new harddisk? (Otherwise it still will be 80GB right?)
Thanks
Last edited by cyberius (2011-04-11 20:24:53)

I issue in such cases the following command:
rsync -Sax /source/dir /dest/dir
Works like a charm as long as you remember to update fstab and menu.lst / grub.cfg with new paths (that's important if you use UUIDs or change your partition layout). Anyway, looking inside those file is recommended.

[SOLVED] NFS in fstab doesn't work

Hi,
after reading the wiki for several hours I am stuck:
etc/fstab:
192.168.0.233:/mnt/z1 /mnt nfs user 0 0
Note that file system is nsf, not nfs4 because the server doesn't support it. I also tried the server name instead of the IP and options like noauto or _netdev to retain the mounting until the network is up. Doesn't matter, the result is always the same:
journalctl -b:
mount.nfs: mount system call failed
mnt.mount mount process exited, code=exited status=32
Failed to mount /mnt.
Dependency failed for Remote File Systems.
Unit mnt.mount entered failed state.
Of course restarting mnt.mount works like a charm, as does mounting manually.
I also tried autofs, which worked fine until I plugged in a 3 GB usb drive, so I would prefer to get mounting via fstab working instead of fixing the autofs issue.
Thanks!
Last edited by AKL (2014-03-24 16:57:17)

I was looking at the same issue in a post that has been closed now. Try these options in fstab
noauto,x-systemd.automount
ip.address.of.host:/export/path/to/sharename /path/to/mount/sharename nfs noauto,x-systemd.automount 0 0
Last edited by Walston_Tempest (2014-03-23 20:22:52)

[Solved] Harddisk fstab

Similar Messages

Maybe you are looking for