MEPIS Community Forum

appealsman, is the "sdc1" in the corrupted fstab a typo for "sdb1"?
Henry

That's my understanding too.

I've only seen the problem once, immediately after a kernel upgrade. I've never had dropbox.

Although dropbox could be one cause of the corruption, it cannot be the *only* one. When I was testing SM 11 in VirtualBox, I added a line above the #Dynamic line that automounted a shared folder on boot-up. That line would disappear on a regular basis, and I had to keep adding it back to fstab. There were no packages installed on that VM except those that came preinstalled on the Live DVD, so if a rogue package is causing this, then it must be one of the packages that came preinstalled on SM 11 (32-bit).

That's right. I don't have dropbox installed.

I think we can discount the Dropbox problem. I've checked exhaustively on 6 separate installations on 3 computers, wiping and reinstalling Dropbox to test every option.

Dropbox is indeed badly behaved and will corrupt fstab, but only if you provide the root password. The bad behaviour is that the prompt for the password gives no indication that fstab will be modified, and as far as I can see there is no need for Dropbox to do this. The prompt has the 'enable extended file attributes' ticked and then asks for the root password. If you untick it, the root password is not required and the fstab is not touched.

BTW, I haven't had any problem with synching, transferring or using any type of file without extended attributes enabled.

The Dropbox problem is something entirely outside Mepis.

Phil

It's copy-and-paste from a borked fstab, so it's maybe a system typo, but it's not a wetware problem on my end.

I had problem with fstab after upgrade to kde 4.6 from test repo ( not kde ), but I don`t know if it`s relevant because we talk about that in another post and it affected only NTFS partitions. Do you want to put it again?

Thanks, but probably not ATM.

(We may be back...)

If I read buildstab correctly, it's supposed to wipe the static entries clean when it finds errors. And add the the newly identified partitions to the dynamic part.
In appealsmans case sdb1 has suddenly been identified as sdc1. And buildstab does the right thing, cleans static and adds everything to the bottom.
As sdc1 doesn't exist, the install isn't working.
udev must be the culprit in this case.
As I figured it out in the middle of the night instead of sleeping, you have to excuse me if I'm completely wrong.
Goodnight.
Henry

Did not know I had a fstab problem until my email (thunderbird) lost all mail and folders this morning (11-18-2011). I found I could only recover by mounting sda6, which contains the saved emails.

I have upgraded each time the repositories are changed and the most recent (as I recall) was the cr repo for thunderbird 8.0


[/code]

My static entries are gone, gone, gone....please point me to how to correct...