Hello,

 

something odd happened to me today. I'am trying to copy a file to my unraid setup and after a while i get an error saying that the device has no free space.

The disk where i am making the transfer to, has about 1.1TB of free space out of 2TB. This free space is reported correctly on the devices webpage.

I tried to copy both to a smb share and directly to the device with the same result. The last messages on the system log are:

 

Jul  9 19:40:46 Tower emhttp: Restart SMB...

Jul  9 19:40:46 Tower emhttp: shcmd (38): killall -HUP smbd

Jul  9 19:40:46 Tower emhttp: shcmd (39): ps axc | grep -q rpc.mountd

Jul  9 19:40:46 Tower emhttp: _shcmd: shcmd (39): exit status: 1

Jul  9 19:40:46 Tower emhttp: shcmd (40): /usr/local/sbin/emhttp_event svcs_restarted

Jul  9 19:40:46 Tower emhttp_event: svcs_restarted

Jul  9 19:40:46 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

Jul  9 19:40:59 Tower kernel: mdcmd (22): nocheck

Jul  9 19:40:59 Tower kernel: md: md_do_sync: got signal, exit...

Jul  9 19:40:59 Tower kernel: md: recovery thread sync completion status: -4

Jul  9 19:44:09 Tower shfs/user: shfs_write: write: (28) No space left on device

Jul  9 19:59:21 Tower last message repeated 250 times

 

If i try to copy the same file to a different disk that has the same size (2TB) but with only a few GB free the operation finishes with success. So the problem isn't the disk size but something related with the disk itself? Any idea of what can be the issue?

 

Cheers,

What unRAID version? Attach syslog. zip if needed.

you trying to disks or shares? had my screw-ups with shares and wrong settings early on with unraid... guess not reading all the wiki stuff  .

anyway, plz clarify. makes a difference!

 

cheers, L

Thanks for looking at this,

 

About the version, i followed what's written on the sticky and updated to last available version 5.0-rc16c. The problem appeared when i was at rc11 though.

 

you trying to disks or shares? had my screw-ups with shares and wrong settings early on with unraid... guess not reading all the wiki stuff  .

anyway, plz clarify. makes a difference!

 

cheers, L

I tried to state that on the first post but i recon that my english sucks Anyway, i tried both. To the share first and then directly to the disk.

 

I will post the full log later when i get home, although i don't see anything wrong in there with the exception of what i already posted, maybe i am overlooking something.

 

Cheers,

 

Here is the syslog as attachment.

 

The disk with the problem is disk4 and share 'Movies'.

 

I noticed that the syslog message

Jul 10 20:49:04 Tower shfs/user: shfs_write: write: (28) No space left on device

only appears when i try to copy the file to the share. When i try to copy it directly to the disk i get the same popup error on windows saying that there is no free space, but the message isn't logged on syslog. I don't know if this makes any sense.

 

Cheers,

syslog.zip

Show screenshots of unRAID Main, Shares, the share details, and Settings->Share Settings.

Show screenshots of unRAID Main, Shares, the share details, and Settings->Share Settings.

 

Here they are.

 

Thanks,

Hey does anyone from Lime can take a look at this and please advise me on how to proceed? I'am really needing the free space and buying a new drive is an option but is a shame to waste more than 1TB on that drive without understanding what is wrong with it...

 

Thanks,

Set the Min free Space to double the size of the largest file that you'll ever copy. This will leave a lot of free space but you can top off the drives manually later.

I am trying to copy the files directly into the disk because that's all the remaining free space i have. What i would like to know is how i should proceed to try and identify the problem cause.

 

Cheers,

Can you run the following test, change the "Allocation method:" to "most free" for the movies share

and re-test your original "copy both to a smb share and directly to the device". You can change it back afterwards.

 

Can you run the following test, change the "Allocation method:" to "most free" for the movies share

and re-test your original "copy both to a smb share and directly to the device". You can change it back afterwards.

 

 

Hello and thanks for looking at this. I had actually already tried to do this, nevertheless i tried once more just to be sure. Unfortunately the problem persists...

 

Is just me that think that this is a really weird issue?

 

Cheers,

Several things.

 

1) Your Bios is running the original firmware (2007), I recommend you follow the mft. directions very closely and update to the latest Version 0902 (2009), please verifiy the link is for your board. http://www.asus.com/Motherboards/P5EVM_DO/#support_Download_5

 

2) Syslog shows:

Jul 10 20:41:14 Tower kernel: 97MB HIGHMEM available.

If I am not mistaken you have 1GB of ram, this is odd (update the bios)

 

3) syslog shows:

Jul 10 20:41:14 Tower kernel: ACPI Warning: 0x00000400-0x0000041f SystemIO conflicts with Region \SMRG 1 (20130117/utaddress-251)

most likely kernel issue, but until you update to the latest bios, this would not be far to look into.

 

4)

Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/0DAY.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/BACKUP.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/EBOOKS.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/GAMES.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/ISEC.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/ISOS.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/LEARN AND MASTER.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/MP3.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/Movies.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/MoviesDB.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/P90X.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/SERIES.cfg: No such file or directory - assigning defaults

 

This is not good, can you please browse to your flash drive, config/shares folder and IF there are any files there, zip and attach for review.

Thank you for your input madburg! Some comments inline.

 

Several things.

 

1) Your Bios is running the original firmware (2007), I recommend you follow the mft. directions very closely and update to the latest Version 0902 (2009), please verifiy the link is for your board. http://www.asus.com/Motherboards/P5EVM_DO/#support_Download_5

Updating the bios was an adventure for me, but it's done.

 

2) Syslog shows:

Jul 10 20:41:14 Tower kernel: 97MB HIGHMEM available.

If I am not mistaken you have 1GB of ram, this is odd (update the bios)

Yes i have 1GB in there. What does this means? The remaining memory is marked as LOWMEM.

 

3) syslog shows:

Jul 10 20:41:14 Tower kernel: ACPI Warning: 0x00000400-0x0000041f SystemIO conflicts with Region \SMRG 1 (20130117/utaddress-251)

most likely kernel issue, but until you update to the latest bios, this would not be far to look into.

It seems it's gone after the bios update.

 

4)

Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/0DAY.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/BACKUP.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/EBOOKS.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/GAMES.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/ISEC.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/ISOS.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/LEARN AND MASTER.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/MP3.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/Movies.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/MoviesDB.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/P90X.cfg: No such file or directory - assigning defaults
Jul 10 20:41:16 Tower emhttp: get_config_idx: fopen /boot/config/shares/SERIES.cfg: No such file or directory - assigning defaults

 

This is not good, can you please browse to your flash drive, config/shares folder and IF there are any files there, zip and attach for review.

The directory is there but no files inside.. This is probably one stupid question, but how do i delete the shares?

 

Unfortunately, updating the bios didn't solved it. I was afraid of that because if it was a problem with the bios the issue would have manifested itself already on the other similar drive in there and it didn't.

I am attaching a new syslog file from a boot with the new bios.

 

Thanks,

syslog.txt

Updating the bios was an adventure for me, but it's done.

Yeah that didnt look to fun, from the brief look i took, you should go over the bios settings, in case any where changed and/or new ones added, when you get a chance.

 

Yes i have 1GB in there. What does this means? The remaining memory is marked as LOWMEM.

No it should be reflected there, I will look in your updated syslog after the bios update.

 

It seems it's gone after the bios update.

Thats great, Im sure they fixed one or more things with ACPI with your board in one of the revisions of the bios. I always start here.

 

The directory is there but no files inside.. This is probably one stupid question, but how do i delete the shares?

That is not good, you should have a .cfg for each share there. Do this, create a new share right now and then check that directory and see if a .cfg is created or not

 

I am attaching a new syslog file from a boot with the new bios.

Thanks, I stepped out at the moment and will review it as soon as I get back.

It's me who need to thank you and not the other way around

 

I created a new test share and a file with the same name and extension .cfg appeared on the directory. And this share answers my question on how do you delete them. None of the others have the delete option...

Yeah, thats why I was not in a rush to tell you, as I am not sure how you got to this point where u are seeing shares in the WebGui but the files dont exist.... so didnt want to question "What do you mean you cant delete them". AS the option may not exist as I have not come across this nor recall anyone posting about it. You will need to PM Tom and send him a link to this thread or wait for someone who has been here a long time and ran into this with someone before and how it was handled.

 

This is the root of your problem, but updating the bios was necessary for stability/support, etc.. if you ask me, for you. I will still check the new syslog, when I get back.

 

Yeah something happened when i created the new share. Now i am not even able to copy a file with less than 1kb in size..

 

It seems it's indeed related. Thanks a bunch madburg!

Hang tight on working with data, you need to delete does shares somehow I think, dont qoute me on that just yet.

Fixing the issue should have you squared away quickly after that. You may want to screenshot your share configurations for when you solve this and want to recreate them (something to do for now, as well as the bios setting verification).

Just when over your syslog, its a pretty old board. Somethings improved some did not with the bios update (your at the latest revision, thats all you can do with that).

 

Still states: (really weird...)

Jul 15 23:41:47 Tower kernel: 90MB HIGHMEM available.

 

I didn't express to clearly about the user shares yesterday. You will not have an option (duh, brain fart on my part) to delete a share thats not empty (contains data).

 

A user share configuration file called config/shares/<share name>.cfg is stored on the Flash for each User Share (where is the Share name). If this file does not exist, then a set of default values are used for the User Share. Whenever a User Share parameter is changed, it's configuration file is also updated, or created if it does not exist.

Your user share .cfg's don't exist and are not getting created for your existing user shares. When you created a new user share (to test) yesterday a .cfg for the new share was created, the procedure does not seem to be working for the existing user shares.

 

Can you post your share.cfg file/passwd/shadow/go files from the config directory, when u get a moment. I want to see a few things before having you try something.

 

I have been reading about the HIGHMEM/LOWMEM stuff on linux and that is a pretty weird value. I wonder if it was always like this..

 

All the files you requested are on the zip attached.

 

Thanks,

config.zip

I have been reading about the HIGHMEM/LOWMEM stuff on linux and that is a pretty weird value. I wonder if it was always like this..

Yeah not good.

 

All files are fine except for share.cfg. Here is mine, as far as I recall they are structure fairly identical (for a lack of better words)

 

# Generated settings:
shareUser="e"
shareUserInclude=""
shareUserExclude=""
shareSMBEnabled="yes"
shareNFSEnabled="no"
shareNFSFsid="100"
shareAFPEnabled="yes"
shareInitialOwner="Administrator"
shareInitialGroup="Domain Users"
shareCacheEnabled="yes"
shareCacheFloor="2000000"
shareMoverSchedule="40 3 * * *"
shareMoverLogging="yes"

 

At first I wanted to say, add a few lines and remove a few (but hold on, may have a better idea).

Question,  do you have NFS enabled (and are you using NFS)?

 

Negative for NFS.

I went into the SMB settings pressed apply and now the share.cfg looks like yours:

# Generated settings:
shareUser="e"
shareUserInclude=""
shareUserExclude=""
shareSMBEnabled="yes"
shareNFSEnabled="no"
shareNFSFsid="100"
shareAFPEnabled="no"
shareInitialOwner="Administrator"
shareInitialGroup="Domain Users"
shareCacheEnabled="yes"
shareCacheFloor="2000000"
shareMoverSchedule="40 3 * * *"
shareMoverLogging="yes"
fuse_remember="330"

OK, lets try this first, can you shutdown unRAID and remove the key and insert it into another device to access it?

if so rename share.cfg to something else, copy the share.cfg from the unRAID source, put the stick back into your unRAID server and boot it back up.

 

default share.cfg should contain only: (from the source)

 

# Share options
shareFlash=e
shareDisk=e
shareUser=-

 

Once you boot back up, paste in your post what the share.cfg contains and check your /config/shares directory as well and report back.