Mounting afp share via fstab crashes boot boot process but works after bootfstab not mounting a disk on...
Output with the same length always
How to think about joining a company whose business I do not understand?
Creating a 16x16 grid using JavaScript
Is a butterfly one or two animals?
How could Tony Stark wield the Infinity Nano Gauntlet - at all?
Unsolved Problems due to Lack of Computational Power
Nuclear decay triggers
Changing a TGV booking
Starships without computers?
Are there any legal requirements concerning airline pilots and their watches?
Can I submit a paper computer science conference using an alias if using my real name can cause legal trouble in my original country
Using は before 欲しい instead が
90s(?) book series about two people transported to a parallel medieval world, she joins city watch, he becomes wizard
Moons that can't see each other
What can I do to keep a threaded bolt from falling out of it’s slot
What happened after the end of the Truman Show?
Repurpose telephone line to ethernet
Does banks' profitability really suffer under low interest rates
Why should someone be willing to write a strong recommendation even if that means losing a undergraduate from their lab?
Do predators tend to have vertical slit pupils versus horizontal for prey animals?
Default camera device to show screen instead of physcial camera
How can I pack my food so it doesn't smell?
Why don't politicians push for fossil fuel reduction by pointing out their scarcity?
Syncing bitcoin node with multiple cores
Mounting afp share via fstab crashes boot boot process but works after boot
fstab not mounting a disk on bootHDD no longer able to mount after editing /etc/fstabDevice in fstab not mounting at bootMounting ExFAT on LinuxProblem mounting CIFS VFS via fstab at bootmounting a CIFS filesystem directly or via fstabNAS share not mounting on linux boot through /etc/fstabmysql service restarted during user being connected lead to failing serviceMount works manually but not in fstabsystemd: finish the execution of custom shell script before starting nginx
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I just migrated my NFS shares to AFP shares.
It looks like it works like it should so I added the records to my fstab:
afpfs#afp://username:password@192.168.1.100/Transfer /home/andy/NAS/Transfer fuse user=andy,group=fuse 0 0
When the system is running, I can mount the shares via sudo mount -all
[andy@archStd01 ~]$ sudo mount -all
Unknown option exec, skipping
Unknown option suid, skipping
Unknown option dev, skipping
Unknown option dev, skipping
Unknown option suid, skipping
The afpfs daemon does not appear to be running for uid 1000, let me start it for you
Mounting 192.168.1.100 from Transfer on /home/andy/NAS/Transfer
Mounting of volume Transfer of server DiskStation01 succeeded.
btw anyone knews this is:
Unknown option suid, skipping
Unknown option dev, skipping
Unknown option dev, skipping
Unknown option suid, skipping
something that I should worry about?
but when I reboot the system it crashes during the booting process while mounting the shares:

Text from "screenshot":
● home-andy-NAS-Transfer.mount - /home/andy/NAS/Transfer
Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-07-30 20:21:18 CEST; 26s ago
Where: /home/andy/NAS/Transfer
What: afpfs#afp://username:password@192.168.1.100/Transfer
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 525 ExecMount=/usr/bin/mount afpfs#afp://username:password@192.168.1.100/Transfer /home/andy/NAS/Transfer -t fuse -o user=andy,group=fuse (code=exited, status=2)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/home-andy-NAS-Transfer.mount
Jul 30 20:21:17 archStd01 systemd[1]: Mounting /home/andy/NAS/Transfer...
Jul 30 20:21:17 archStd01 [529]: Starting up AFPFS version 0.8.1
Jul 30 20:21:18 archStd01 systemd[1]: home-andy-NAS-Transfer.mount: Mount process exited, code=exited status=2
Jul 30 20:21:18 archStd01 systemd[1]: Failed to mount /home/andy/NAS/Transfer.
Jul 30 20:21:18 archStd01 systemd[1]: home-andy-NAS-Transfer.mount: Unit entered failed state.
has anyone an idea what might went wrong?
Im on ArchLinux and use community/afpfs-ng 0.8.1-10
Logfiles:
dmesg: https://ghostbin.com/paste/9jgg8
journalctl -r: https://ghostbin.com/paste/zfwdg
mount systemd fstab automounting
add a comment |
I just migrated my NFS shares to AFP shares.
It looks like it works like it should so I added the records to my fstab:
afpfs#afp://username:password@192.168.1.100/Transfer /home/andy/NAS/Transfer fuse user=andy,group=fuse 0 0
When the system is running, I can mount the shares via sudo mount -all
[andy@archStd01 ~]$ sudo mount -all
Unknown option exec, skipping
Unknown option suid, skipping
Unknown option dev, skipping
Unknown option dev, skipping
Unknown option suid, skipping
The afpfs daemon does not appear to be running for uid 1000, let me start it for you
Mounting 192.168.1.100 from Transfer on /home/andy/NAS/Transfer
Mounting of volume Transfer of server DiskStation01 succeeded.
btw anyone knews this is:
Unknown option suid, skipping
Unknown option dev, skipping
Unknown option dev, skipping
Unknown option suid, skipping
something that I should worry about?
but when I reboot the system it crashes during the booting process while mounting the shares:

Text from "screenshot":
● home-andy-NAS-Transfer.mount - /home/andy/NAS/Transfer
Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-07-30 20:21:18 CEST; 26s ago
Where: /home/andy/NAS/Transfer
What: afpfs#afp://username:password@192.168.1.100/Transfer
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 525 ExecMount=/usr/bin/mount afpfs#afp://username:password@192.168.1.100/Transfer /home/andy/NAS/Transfer -t fuse -o user=andy,group=fuse (code=exited, status=2)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/home-andy-NAS-Transfer.mount
Jul 30 20:21:17 archStd01 systemd[1]: Mounting /home/andy/NAS/Transfer...
Jul 30 20:21:17 archStd01 [529]: Starting up AFPFS version 0.8.1
Jul 30 20:21:18 archStd01 systemd[1]: home-andy-NAS-Transfer.mount: Mount process exited, code=exited status=2
Jul 30 20:21:18 archStd01 systemd[1]: Failed to mount /home/andy/NAS/Transfer.
Jul 30 20:21:18 archStd01 systemd[1]: home-andy-NAS-Transfer.mount: Unit entered failed state.
has anyone an idea what might went wrong?
Im on ArchLinux and use community/afpfs-ng 0.8.1-10
Logfiles:
dmesg: https://ghostbin.com/paste/9jgg8
journalctl -r: https://ghostbin.com/paste/zfwdg
mount systemd fstab automounting
Can you add the output ofdmesgand show the contents of/var/log/syslog
– Hunter.S.Thompson
Jul 30 '17 at 17:58
No need for screenshots. Just redirect the output ofsystemctl statusto a file. Make sure thatsystemctldoes not truncate the lines, because what has been chopped off the end of that output is important. The "unknown option" stuff is really a separate question; and we do one question per question here.
– JdeBP
Jul 30 '17 at 18:16
I just added dmesg and journalctl -r to my op. No syslog because im on systemd.
– rockZ
Jul 30 '17 at 18:18
@jdeBP I added the plaintext u needed. Thanks.
– rockZ
Jul 30 '17 at 18:26
About theUnknown option, my guess is that the mount tool reading fstab does have some defaults options (even when not using the option defaults), such as dev and suid. These options does not exist for AFPFS tool, so it skip these. -> Nothing to worry about.
– LittleWhite
2 days ago
add a comment |
I just migrated my NFS shares to AFP shares.
It looks like it works like it should so I added the records to my fstab:
afpfs#afp://username:password@192.168.1.100/Transfer /home/andy/NAS/Transfer fuse user=andy,group=fuse 0 0
When the system is running, I can mount the shares via sudo mount -all
[andy@archStd01 ~]$ sudo mount -all
Unknown option exec, skipping
Unknown option suid, skipping
Unknown option dev, skipping
Unknown option dev, skipping
Unknown option suid, skipping
The afpfs daemon does not appear to be running for uid 1000, let me start it for you
Mounting 192.168.1.100 from Transfer on /home/andy/NAS/Transfer
Mounting of volume Transfer of server DiskStation01 succeeded.
btw anyone knews this is:
Unknown option suid, skipping
Unknown option dev, skipping
Unknown option dev, skipping
Unknown option suid, skipping
something that I should worry about?
but when I reboot the system it crashes during the booting process while mounting the shares:

Text from "screenshot":
● home-andy-NAS-Transfer.mount - /home/andy/NAS/Transfer
Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-07-30 20:21:18 CEST; 26s ago
Where: /home/andy/NAS/Transfer
What: afpfs#afp://username:password@192.168.1.100/Transfer
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 525 ExecMount=/usr/bin/mount afpfs#afp://username:password@192.168.1.100/Transfer /home/andy/NAS/Transfer -t fuse -o user=andy,group=fuse (code=exited, status=2)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/home-andy-NAS-Transfer.mount
Jul 30 20:21:17 archStd01 systemd[1]: Mounting /home/andy/NAS/Transfer...
Jul 30 20:21:17 archStd01 [529]: Starting up AFPFS version 0.8.1
Jul 30 20:21:18 archStd01 systemd[1]: home-andy-NAS-Transfer.mount: Mount process exited, code=exited status=2
Jul 30 20:21:18 archStd01 systemd[1]: Failed to mount /home/andy/NAS/Transfer.
Jul 30 20:21:18 archStd01 systemd[1]: home-andy-NAS-Transfer.mount: Unit entered failed state.
has anyone an idea what might went wrong?
Im on ArchLinux and use community/afpfs-ng 0.8.1-10
Logfiles:
dmesg: https://ghostbin.com/paste/9jgg8
journalctl -r: https://ghostbin.com/paste/zfwdg
mount systemd fstab automounting
I just migrated my NFS shares to AFP shares.
It looks like it works like it should so I added the records to my fstab:
afpfs#afp://username:password@192.168.1.100/Transfer /home/andy/NAS/Transfer fuse user=andy,group=fuse 0 0
When the system is running, I can mount the shares via sudo mount -all
[andy@archStd01 ~]$ sudo mount -all
Unknown option exec, skipping
Unknown option suid, skipping
Unknown option dev, skipping
Unknown option dev, skipping
Unknown option suid, skipping
The afpfs daemon does not appear to be running for uid 1000, let me start it for you
Mounting 192.168.1.100 from Transfer on /home/andy/NAS/Transfer
Mounting of volume Transfer of server DiskStation01 succeeded.
btw anyone knews this is:
Unknown option suid, skipping
Unknown option dev, skipping
Unknown option dev, skipping
Unknown option suid, skipping
something that I should worry about?
but when I reboot the system it crashes during the booting process while mounting the shares:

Text from "screenshot":
● home-andy-NAS-Transfer.mount - /home/andy/NAS/Transfer
Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-07-30 20:21:18 CEST; 26s ago
Where: /home/andy/NAS/Transfer
What: afpfs#afp://username:password@192.168.1.100/Transfer
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 525 ExecMount=/usr/bin/mount afpfs#afp://username:password@192.168.1.100/Transfer /home/andy/NAS/Transfer -t fuse -o user=andy,group=fuse (code=exited, status=2)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/home-andy-NAS-Transfer.mount
Jul 30 20:21:17 archStd01 systemd[1]: Mounting /home/andy/NAS/Transfer...
Jul 30 20:21:17 archStd01 [529]: Starting up AFPFS version 0.8.1
Jul 30 20:21:18 archStd01 systemd[1]: home-andy-NAS-Transfer.mount: Mount process exited, code=exited status=2
Jul 30 20:21:18 archStd01 systemd[1]: Failed to mount /home/andy/NAS/Transfer.
Jul 30 20:21:18 archStd01 systemd[1]: home-andy-NAS-Transfer.mount: Unit entered failed state.
has anyone an idea what might went wrong?
Im on ArchLinux and use community/afpfs-ng 0.8.1-10
Logfiles:
dmesg: https://ghostbin.com/paste/9jgg8
journalctl -r: https://ghostbin.com/paste/zfwdg
mount systemd fstab automounting
mount systemd fstab automounting
edited Jul 30 '17 at 18:26
rockZ
asked Jul 30 '17 at 17:32
rockZrockZ
1521 gold badge3 silver badges10 bronze badges
1521 gold badge3 silver badges10 bronze badges
Can you add the output ofdmesgand show the contents of/var/log/syslog
– Hunter.S.Thompson
Jul 30 '17 at 17:58
No need for screenshots. Just redirect the output ofsystemctl statusto a file. Make sure thatsystemctldoes not truncate the lines, because what has been chopped off the end of that output is important. The "unknown option" stuff is really a separate question; and we do one question per question here.
– JdeBP
Jul 30 '17 at 18:16
I just added dmesg and journalctl -r to my op. No syslog because im on systemd.
– rockZ
Jul 30 '17 at 18:18
@jdeBP I added the plaintext u needed. Thanks.
– rockZ
Jul 30 '17 at 18:26
About theUnknown option, my guess is that the mount tool reading fstab does have some defaults options (even when not using the option defaults), such as dev and suid. These options does not exist for AFPFS tool, so it skip these. -> Nothing to worry about.
– LittleWhite
2 days ago
add a comment |
Can you add the output ofdmesgand show the contents of/var/log/syslog
– Hunter.S.Thompson
Jul 30 '17 at 17:58
No need for screenshots. Just redirect the output ofsystemctl statusto a file. Make sure thatsystemctldoes not truncate the lines, because what has been chopped off the end of that output is important. The "unknown option" stuff is really a separate question; and we do one question per question here.
– JdeBP
Jul 30 '17 at 18:16
I just added dmesg and journalctl -r to my op. No syslog because im on systemd.
– rockZ
Jul 30 '17 at 18:18
@jdeBP I added the plaintext u needed. Thanks.
– rockZ
Jul 30 '17 at 18:26
About theUnknown option, my guess is that the mount tool reading fstab does have some defaults options (even when not using the option defaults), such as dev and suid. These options does not exist for AFPFS tool, so it skip these. -> Nothing to worry about.
– LittleWhite
2 days ago
Can you add the output of
dmesg and show the contents of /var/log/syslog– Hunter.S.Thompson
Jul 30 '17 at 17:58
Can you add the output of
dmesg and show the contents of /var/log/syslog– Hunter.S.Thompson
Jul 30 '17 at 17:58
No need for screenshots. Just redirect the output of
systemctl status to a file. Make sure that systemctl does not truncate the lines, because what has been chopped off the end of that output is important. The "unknown option" stuff is really a separate question; and we do one question per question here.– JdeBP
Jul 30 '17 at 18:16
No need for screenshots. Just redirect the output of
systemctl status to a file. Make sure that systemctl does not truncate the lines, because what has been chopped off the end of that output is important. The "unknown option" stuff is really a separate question; and we do one question per question here.– JdeBP
Jul 30 '17 at 18:16
I just added dmesg and journalctl -r to my op. No syslog because im on systemd.
– rockZ
Jul 30 '17 at 18:18
I just added dmesg and journalctl -r to my op. No syslog because im on systemd.
– rockZ
Jul 30 '17 at 18:18
@jdeBP I added the plaintext u needed. Thanks.
– rockZ
Jul 30 '17 at 18:26
@jdeBP I added the plaintext u needed. Thanks.
– rockZ
Jul 30 '17 at 18:26
About the
Unknown option, my guess is that the mount tool reading fstab does have some defaults options (even when not using the option defaults), such as dev and suid. These options does not exist for AFPFS tool, so it skip these. -> Nothing to worry about.– LittleWhite
2 days ago
About the
Unknown option, my guess is that the mount tool reading fstab does have some defaults options (even when not using the option defaults), such as dev and suid. These options does not exist for AFPFS tool, so it skip these. -> Nothing to worry about.– LittleWhite
2 days ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f382781%2fmounting-afp-share-via-fstab-crashes-boot-boot-process-but-works-after-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f382781%2fmounting-afp-share-via-fstab-crashes-boot-boot-process-but-works-after-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you add the output of
dmesgand show the contents of/var/log/syslog– Hunter.S.Thompson
Jul 30 '17 at 17:58
No need for screenshots. Just redirect the output of
systemctl statusto a file. Make sure thatsystemctldoes not truncate the lines, because what has been chopped off the end of that output is important. The "unknown option" stuff is really a separate question; and we do one question per question here.– JdeBP
Jul 30 '17 at 18:16
I just added dmesg and journalctl -r to my op. No syslog because im on systemd.
– rockZ
Jul 30 '17 at 18:18
@jdeBP I added the plaintext u needed. Thanks.
– rockZ
Jul 30 '17 at 18:26
About the
Unknown option, my guess is that the mount tool reading fstab does have some defaults options (even when not using the option defaults), such as dev and suid. These options does not exist for AFPFS tool, so it skip these. -> Nothing to worry about.– LittleWhite
2 days ago