Jump to content


Photo

Autofs does not start after reboot box


  • Please log in to reply
48 replies to this topic

Re: Autofs does not start after reboot box #41 andyblac

  • Senior Member
  • 465 posts

+18
Neutral

Posted 28 April 2014 - 09:59

Bug in autofs, it refuses to create /media/net for some reason. It will happily create many other directories though, so if you find out WHY it does not do as it's supposed to, it'd be good to file a bug report for the autofs folks.

irc, autofs can't 'share' the master mountpoint, in your case /media/net, as autofs needs this to be a mountpoint not a standard folder when using the --ghost option.

 

for this reason in oe-aliance we use '/media/autofs' if you run a 'mount' command in telnet you will see that /media/autofs is indeed a mount point, this means you can't have fstab and autofs mounting to the same location.

 

also we tweaked the standard config file to work better with offline servers, you are welcome to use our files.

 

https://github.com/o...-daemons/autofs



Re: Autofs does not start after reboot box #42 SpaceRat

  • Senior Member
  • 1,030 posts

+65
Good

Posted 28 April 2014 - 21:10


Bug in autofs, it refuses to create /media/net for some reason.


It will work if you create that directory manually, btw.

I've simply added "mkdir -p /media/net" to fix this:

start() {
echo -n "Starting $prog: "

mkdir -p /media/net
# Make sure autofs4 module is loaded
if ! grep -q autofs /proc/filesystems

Not elegant, but it works.
It wasn't necessary for autofs 4.x though ...

irc, autofs can't 'share' the master mountpoint, in your case /media/net, as autofs needs this to be a mountpoint not a standard folder when using the --ghost option.

Actually, Linux doesn't even know what a mount point is.
And the only problem with /media/net or whatever you set it up to use is, that autofs keeps deleting this directory (It's nothing but that) and doesn't recreate it when needes (autofs 4.x did).
1st box: Vu+ Ultimo 4k 4xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390

Re: Autofs does not start after reboot box #43 MiLo

  • PLi® Core member
  • 14,042 posts

+298
Excellent

Posted 29 April 2014 - 14:00

andyblac uses the same solution, create the path before the script runs. It does not matter whether you name it "net" or "autofs". andyblac's just uses a volatile config file to create it, which looks like a neat solution to the directory not being created.

Note that if you set the ghost dir to "/blabla/net" it DOES create the net directory. It's a bug in autofs, probably it has some relation to /media/ being a tmpfs filesystem.
Real musicians never die - they just decompose

Re: Autofs does not start after reboot box #44 Xana

  • Senior Member
  • 56 posts

0
Neutral

Posted 9 September 2014 - 21:06

Hi,

his there any news/development/solution, regarding this issues with autofs and mount points ?

 

Thanks



Re: Autofs does not start after reboot box #45 erkman

  • Senior Member
  • 90 posts

+2
Neutral

Posted 12 February 2015 - 16:19

Have a simliar Problem on my new et9200. when i start the box i must over telnet autofs restart to get my shares working. autofs daemon is already running but must restarted that everthing is fine.

have tried this

start)

start

restart

;;

but didnt work for me


ET9200 openpli 6.2 ET4000 openpli 4 Solo2 openpli 7.2


Re: Autofs does not start after reboot box #46 erkman

  • Senior Member
  • 90 posts

+2
Neutral

Posted 12 February 2015 - 18:21

found this in /var/log/messages

Jan  1 01:00:23 Wohnzimmer daemon.crit automount[555]: do_mount_autofs_indirect: failed to create autofs directory /media/net/Home-Server
Jan  1 01:00:23 Wohnzimmer daemon.crit automount[555]: handle_mounts: mount of /media/net/Home-Server failed!
Jan  1 01:00:23 Wohnzimmer daemon.err automount[555]: master_do_mount: failed to startup mount

ET9200 openpli 6.2 ET4000 openpli 4 Solo2 openpli 7.2


Re: Autofs does not start after reboot box #47 nietgiftig

  • Senior Member
  • 787 posts

+39
Good

Posted 12 February 2015 - 19:36

http://forums.openpl...ndpost&p=392418

 

 

cd /etc/init.d
and edit the file "autofs" there.
Between these lines

echo -n "Starting $prog: "

# Make sure autofs4 module is loaded

add "mkdir -p /media/net" to work around the problems a.) autofs forgets to create those dirs and b.) it will stupidly remove them again and again

The result should look like this:

echo -n "Starting $prog: "

mkdir -p /media/net
# Make sure autofs4 module is loaded

 Hardware: Master VU Uno 4K SE  1x Mut@nt HD51.4K & 2x ZgemmaH9T
Software : Pli (v7) (7.1rc) 2019 


Re: Autofs does not start after reboot box #48 erkman

  • Senior Member
  • 90 posts

+2
Neutral

Posted 12 February 2015 - 19:56

thanks, that solves my problem


ET9200 openpli 6.2 ET4000 openpli 4 Solo2 openpli 7.2


Re: Autofs does not start after reboot box #49 SpaceRat

  • Senior Member
  • 1,030 posts

+65
Good

Posted 12 February 2015 - 20:16

I wonder why it is still not inside the original autofs package or gets patched in during OpenPLi build ...

That post of mine is more than one year old and it's now almost a year that MiLo confirmed he knows this solution is part of OpenViX already.
He has done patches of external packages for less ...
1st box: Vu+ Ultimo 4k 4xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users