Ok so here's my issue. I've had my NAS automounted through fstab since 10.04. And it's worked fine. It even worked fine in 11.10, until about 4 days ago, then it stopped working on ALL my computers the same day (updates?). I can mount it with
And it works fine. So I know fstab is correct, or it wouldn't mount. In affect a "sudo mount -a" is SUPPOSED to be done on fstab on boot anyway. But for some reason that's no longer happening.
But wait, the plot thickens. I wrote a script to the effect of running "mount -a" at startup.
I thought that was working, but after hours of playing with it I discovered it wasn't mounting till I ran ANYTHING sudo or gksudo, the the second I hit enter after entering the password it mounted. ANYTHING that asked for the user password would mount it, even if the command was "gksudo kate". How weird huh?
I've even turned off the use of passwords in sudoers, and it still does it. Except now what happens is the first time I sudo something it ask for a password, after that first time it just does it without asking. On a weird side note, gksudo doesn't ask for a password anymore, only sudo. But gksudo doesn't cause the drive to mount now that it's not asking for the password. But I have to enter a password, or enter through it asking that first time, or the drive won't mount. It's something about the startup script I think, it waits for the password to be entered, it doesn't matter how long it takes, it waits for it the be entered for anything then finally runs the "mount" in the startup script.
Course that issue still doesn't explain why fstab no longer autoloads it on startup itself, unless it's the same issue, just waiting on a password to be entered the first time after starteup. I'll disable my startup script and see.
Ideas?
Code:
sudo mount -a
But wait, the plot thickens. I wrote a script to the effect of running "mount -a" at startup.
I thought that was working, but after hours of playing with it I discovered it wasn't mounting till I ran ANYTHING sudo or gksudo, the the second I hit enter after entering the password it mounted. ANYTHING that asked for the user password would mount it, even if the command was "gksudo kate". How weird huh?
I've even turned off the use of passwords in sudoers, and it still does it. Except now what happens is the first time I sudo something it ask for a password, after that first time it just does it without asking. On a weird side note, gksudo doesn't ask for a password anymore, only sudo. But gksudo doesn't cause the drive to mount now that it's not asking for the password. But I have to enter a password, or enter through it asking that first time, or the drive won't mount. It's something about the startup script I think, it waits for the password to be entered, it doesn't matter how long it takes, it waits for it the be entered for anything then finally runs the "mount" in the startup script.
Course that issue still doesn't explain why fstab no longer autoloads it on startup itself, unless it's the same issue, just waiting on a password to be entered the first time after starteup. I'll disable my startup script and see.
Ideas?
Comment