Dropbox is compatible with Ext4 but doesn't recognize ext4 drive?

Weird thing happend to me, which meant I was able to resolve this issue,
On 3 linux machines (2x Ubuntu 1x Ubuntu-Mate VM) all had this issue,
I thought ok well lets create a new partition for dropbox anyway.

When I used GParted and created a small partition of Ext4 if fixed the original
problem of dropbox not recognising my original partition as a valid file type.
After the repartition upon reboot into Linux dropbox started working again.
It must be something to do with a Ubuntu install not setting something quite
properly that then dropbox reads as not geninue. GParted seemed to fix it.

Now I have a spare partition on every machine I don't need :/
Anyway it was good to get it fixed.

Your workaround works for me with Ubuntu 18.04 fresh install

@pwang
What ... you needed to do the Gparted fiddle after your Ubuntu 18.04 install too ?

Reading updates on other posts, Dropbox users say it may have updated recently and started working again that way. So I'm still not 100% if it was what I did with Gparted or an update.
Good that it is working though on 3 of my Ubuntu machines.
Maybe I will do a test VM in the future with a fresh install and see when it works.

I think you're mistaken. When you create a new partition with gparted, it automatically mounts in /media/username/new-drive-label, hence three levels down the root. The problem is when you try to mount your new drive fewer than 3 levels down the root, ex. /media/new-drive-label.

So, I guess as it stands, the problem is not resolved yet.

This solution did the trick for me, too. Thanks @AminSadeghi 

Ah in the last 2 days the problem has magically returned again, after working with no problem for a month (it happened at the same time on 2 machines).

No idea what has changed. I presume it is a remotely activiated restriction. I'm sure I've not changed anything, after my gparted fiddle a month ago (posted earlier 11-13-2018 12:17 AM which fixed the problem on all 3 of my linux machines I use).

michelfeu Just to clarify, what solution did you try, there have been a couple mentioned, one of which (mine) stopped working, I was a bit confused by the 3-steps from root solution, like it wasn't clear if that was fixable by us somehow, but you mentioned something worked ?

---

l0ngman wrote:

michelfeu Just to clarify, what solution did you try, there have been a couple mentioned, one of which (mine) stopped working, I was a bit confused by the 3-steps from root solution, like it wasn't clear if that was fixable by us somehow, but you mentioned something worked ?

---

Hi, I created another director in /media/DropboxContainer, changed the permissions to user level (via chown) and redirected the Dropbox file to this location through the Dropbox menu. The program accepted it. 

I'm in the same boat. Paid sub, 16.04, mounted in /home/scaine/Misc/Dropbox (ext4). Got told a few months ago to move to an ext4 partition. So I moved it to /home/scaine/Dropbox, and it's been working fine since. Two or three days ago, I started getting nagged about unsupported file systems.

My sub is up on February, so I've that long to figure out how to run OwnCloud in AWS, or similar. Not a fan of this move by Dropbox at all - it wouldn't surprise me at all if this generates MORE support issues for them in the short term, but in the long term, they've driven all their Linux customers away, so long term gain for them? Who knows. Very frustrating experience though, so I'll look elsewhere now, I think.