Arch Linux

Expez

Member

Registered: 2012-03-31

Posts: 14

Samba: "Windows can't access this disc. The disc might be corrupt..."

I've been happily sharing a folder with a windows laptop for a long time.  After moving from wired to wireless yesterday I suddenly get this error, when attempting to mount the folder:

Windows can't access this disc. The disc might be corrupt. Make sure that the disc uses a format that Windows recognizes. If the disc is unformatted, you need to format it before using it.

I'm accessing the drive, and the shared folders, like normal on the linux box so Window's guess of what's wrong is a bit off.

smb.conf:
[global]
   workgroup = MYGROUP
   server string = Samba Server
   printcap name = /etc/printcap
   load printers = yes
   log file = /var/log/samba/%m.log
   max log size = 50
   security = user
   dns proxy = no 

[downloads]
   path = /home/expez/downloads
   available = yes
   valid users = expez
   read only = no
   browsable = yes
   public = yes
   writable = yes

Some guy on SO appears to have had the same problem, but no solution was offered.  Any idea as to what might be wrong?

cartman

Member

Registered: 2010-09-08

Posts: 5

Re: Samba: "Windows can't access this disc. The disc might be corrupt..."

Check if / is full

Expez

Member

Registered: 2012-03-31

Posts: 14

Re: Samba: "Windows can't access this disc. The disc might be corrupt..."

It started working again for no apparant reason the other day after I upgraded packages and removed some old and orphaned packages.  I currently have 2.2G free on / so that might've been the problem.

flintmecha

Member

Registered: 2008-07-27

Posts: 41

Re: Samba: "Windows can't access this disc. The disc might be corrupt..."

I just wanted to say I had the same problem, and this thread solved it for me, for anyone else coming here from Google. Here were my symptoms:

- Attempting to browse a mapped network drive gave me the same "the disc might be corrupt" error.
- Attempting to open the network device and browser shares from the "Network" section on Windows was giving me error code 0x80070035, "network path was not found".

I had JUST done a pacman -Syu so my only hunch was perhaps an update to Samba broke something.

After reading Expez's above comment, I checked and sure enough, the server had 0% free space according to df. I made some room by clearing out pacman pkg cache and the problem suddenly went away.