Yesterday I moved some drives around, used the "new config" utility, ran a parity check and all is well.

 

This past week I have been making some drive changes to my array.  Here is the order.

- purchased new 3TB drive so I could upgrade existing 2TB as it was 95% full.  I only have one share on this drive and keep the contents separate.  The new drive was actually pre-cleared and saved as a spare.  I took the Seagate I had previously been using as a spare and used that for the upgrade (keep rotating one through the spare drive usage so it doesn't just sit forever.

- When I installed the drive I took the opportunity to get my drives in a sensical order in the case making them easier to keep track of and planned to re-order the drives in the array.

- Ran 2 preclears on the new drive.  Once passed I did the upgrade of the existing drive.

- Last night I did a "new config" and ran a parity check.  All is fine. (I had a thread going on this the past couple days)

- Today, after running a single preclear, I added the older drive as Disk 11.

 

Today I started writing to the array since I started making all these changes.  However, I can getting "disk full errors"  There is plenty of space.  Not a single drive in the array is actually full by a long shot at this point.  my array is 52% full overall. 

 

I was able to save in one location, then another gave me the disk full error.  I rebooted the array, and then could save where I previously had trouble but now another share is giving me this error.

 

Here is the actual error from the syslog (full file attached).

Nov 19 00:51:31 TODD-Svr shfs/user: shfs_create: assign_disk: Jukebox Database Files/Zappiti DB/database-2.8.9.0.db-journal (28) No space left on device (Drive related)

 

I have attached my syslog from after this re-boot.  You will see the error occur in the last few lines.  The configuration in my signature is current. 

 

 

Addition... in looking at my syslog i see two other sets of errors

 

The first is.. 

 

Nov 18 23:52:24 TODD-Svr kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106

Nov 18 23:52:24 TODD-Svr kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved

Nov 18 23:52:24 TODD-Svr kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [c00ff780]

Nov 18 23:52:24 TODD-Svr kernel: initial memory mapped: [mem 0x00000000-0x01bfffff]

Nov 18 23:52:24 TODD-Svr kernel: Base memory trampoline at [c009a000] 9a000 size 16384

Nov 18 23:52:24 TODD-Svr kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]

Nov 18 23:52:24 TODD-Svr kernel:  [mem 0x00000000-0x000fffff] page 4k (Errors)

Nov 18 23:52:24 TODD-Svr kernel: init_memory_mapping: [mem 0x37800000-0x379fffff]

Nov 18 23:52:24 TODD-Svr kernel:  [mem 0x37800000-0x379fffff] page 2M (Errors)

Nov 18 23:52:24 TODD-Svr kernel: init_memory_mapping: [mem 0x34000000-0x377fffff]

Nov 18 23:52:24 TODD-Svr kernel:  [mem 0x34000000-0x377fffff] page 2M (Errors)

Nov 18 23:52:24 TODD-Svr kernel: init_memory_mapping: [mem 0x00100000-0x33ffffff]

Nov 18 23:52:24 TODD-Svr kernel:  [mem 0x00100000-0x001fffff] page 4k (Errors)

Nov 18 23:52:24 TODD-Svr kernel:  [mem 0x00200000-0x33ffffff] page 2M (Errors)

Nov 18 23:52:24 TODD-Svr kernel: init_memory_mapping: [mem 0x37a00000-0x37bfdfff]

Nov 18 23:52:24 TODD-Svr kernel:  [mem 0x37a00000-0x37bfdfff] page 4k (Errors)

 

I'm going to stop and run a memtest right now and see what i get... will report back, but not sure if this could be causing the disk full error.

 

The second is.....

 

Nov 18 23:52:24 TODD-Svr kernel: sas: ata9: end_device-1:0: dev error handler (Errors)

Nov 18 23:52:24 TODD-Svr kernel: sas: ata10: end_device-1:1: dev error handler (Errors)

Nov 18 23:52:24 TODD-Svr kernel: sas: ata11: end_device-1:2: dev error handler (Errors)

Nov 18 23:52:24 TODD-Svr kernel: sas: ata12: end_device-1:3: dev error handler (Errors)

Nov 18 23:52:24 TODD-Svr kernel: sas: ata13: end_device-1:4: dev error handler (Errors)

Nov 18 23:52:24 TODD-Svr kernel: sas: ata14: end_device-1:5: dev error handler (Errors)

Nov 18 23:52:24 TODD-Svr kernel: sas: ata15: end_device-1:6: dev error handler (Errors)

Nov 18 23:52:24 TODD-Svr kernel: sas: ata16: end_device-1:7: dev error handler (Errors)

 

This occurs a handful of times in the syslog and each time there are more rows with the same error...  I guess I will shut down and check all connections as well, including seating the memory.

 

syslog-2013-11-19.txt

Re-seated memory and checked all plugs.  Most of the sata cables have latches and all looked just fine. 

 

I have a memory test running, at 50% with no errors.  I'll let it run through the night and will post if any change in the morning. 

 

Any help on the drive full error is appreciated.  Thanks.

Not sure what may be causing this -- but I notice you have Simple Features installed.  I don't use that; but it's known to not-yet be compatible with v5.0.    Not sure if that's related to your issue; but the first thing I'd try is a "Safe Mode" boot ... you'll need a keyboard/monitor on the UnRAID box; but try booting to Safe Mode and see if you still have the copy issue.

 

If not, then this has something to do with your add-ons; and Simple Features would be the first one I'd disable.    [if you don't have a keyboard/monitor on the server, you may just want to try disabling that to begin with]

 

Not sure what may be causing this -- but I notice you have Simple Features installed.  I don't use that; but it's known to not-yet be compatible with v5.0.    Not sure if that's related to your issue; but the first thing I'd try is a "Safe Mode" boot ... you'll need a keyboard/monitor on the UnRAID box; but try booting to Safe Mode and see if you still have the copy issue.

 

If not, then this has something to do with your add-ons; and Simple Features would be the first one I'd disable.    [if you don't have a keyboard/monitor on the server, you may just want to try disabling that to begin with]

 

Everything has been working fine with zero issues until i yesterday. 

 

3 full mem tests pased with zero issues.

 

I still have this in the syslog:

 

Nov 19 08:15:02 TODD-Svr kernel: Base memory trampoline at [c009a000] 9a000 size 16384

Nov 19 08:15:02 TODD-Svr kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]

Nov 19 08:15:02 TODD-Svr kernel:  [mem 0x00000000-0x000fffff] page 4k (Errors)

Nov 19 08:15:02 TODD-Svr kernel: init_memory_mapping: [mem 0x37800000-0x379fffff]

Nov 19 08:15:02 TODD-Svr kernel:  [mem 0x37800000-0x379fffff] page 2M (Errors)

Nov 19 08:15:02 TODD-Svr kernel: init_memory_mapping: [mem 0x34000000-0x377fffff]

Nov 19 08:15:02 TODD-Svr kernel:  [mem 0x34000000-0x377fffff] page 2M (Errors)

Nov 19 08:15:02 TODD-Svr kernel: init_memory_mapping: [mem 0x00100000-0x33ffffff]

Nov 19 08:15:02 TODD-Svr kernel:  [mem 0x00100000-0x001fffff] page 4k (Errors)

Nov 19 08:15:02 TODD-Svr kernel:  [mem 0x00200000-0x33ffffff] page 2M (Errors)

Nov 19 08:15:02 TODD-Svr kernel: init_memory_mapping: [mem 0x37a00000-0x37bfdfff]

Nov 19 08:15:02 TODD-Svr kernel:  [mem 0x37a00000-0x37bfdfff] page 4k (Errors)

Nov 19 08:15:02 TODD-Svr kernel: BRK [0x01630000, 0x01630fff] PGTABLE

 

and..

 

Nov 19 08:15:02 TODD-Svr kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 (Drive related)

Nov 19 08:15:02 TODD-Svr kernel: sas: ata9: end_device-6:0: dev error handler (Errors)

Nov 19 08:15:02 TODD-Svr kernel: sas: ata10: end_device-6:1: dev error handler (Errors)

Nov 19 08:15:02 TODD-Svr kernel: sas: ata11: end_device-6:2: dev error handler (Errors)

Nov 19 08:15:02 TODD-Svr kernel: sas: ata12: end_device-6:3: dev error handler (Errors)

Nov 19 08:15:02 TODD-Svr kernel: sas: ata13: end_device-6:4: dev error handler (Errors)

Nov 19 08:15:02 TODD-Svr kernel: sas: ata14: end_device-6:5: dev error handler (Errors)

Nov 19 08:15:02 TODD-Svr kernel: sas: ata15: end_device-6:6: dev error handler (Errors)

Nov 19 08:15:02 TODD-Svr kernel: sas: ata16: end_device-6:7: dev error handler (Errors)

 

All cables are fine.  plenty of power...  I can access all drives.

 

I am still getting the same error.

Also of note. 

 

My main share "Media" is fine. I can write normally, or at least I haven't had issues yet.

I have 3 other user shares on the server and none of them can be written to.  They all have plenty of space but are returning this error.

 

"No space left on device" in the syslog and "There is not enough space...." in windows.

I think I've got it....

 

My user shares designate which drives are included and excluded for use, and my split level is 0. 

I had not updated since I ran the New Config so the user shares that were limited to specific disks were not working.  Media which spans multiple drives was working fine because some of the included references were still good. 

 

All seems to be working fine now.

 

Still not sure what those errors are if anyone can help with that, much appreciated.

Why did you use the initconfig? That is not necessary when upgrading a disk or adding a new disk.

 

If those only appear once on boot then it's likely they're not really errors. The dev error handler doesn't look like an error to me but rather something that handles an error if it were to occur.

 

 

Why did you use the initconfig? That is not necessary when upgrading a disk or adding a new disk.

 

If those only appear once on boot then it's likely they're not really errors. The dev error handler doesn't look like an error to me but rather something that handles an error if it were to occur.

 

Yes. None of those are errors. Update unmenu and the tag will go away.

Why did you use the initconfig? That is not necessary when upgrading a disk or adding a new disk.

 

If those only appear once on boot then it's likely they're not really errors. The dev error handler doesn't look like an error to me but rather something that handles an error if it were to occur.

 

I ran "new config" because i was re-organizing all my drives inside the case based on how they were grouped for use and keeping their place in the disk list to match their case position.  It just makes it easier to track which one is where. 

Why did you use the initconfig? That is not necessary when upgrading a disk or adding a new disk.

 

If those only appear once on boot then it's likely they're not really errors. The dev error handler doesn't look like an error to me but rather something that handles an error if it were to occur.

 

Yes. None of those are errors. Update unmenu and the tag will go away.

 

Thanks, i didn't realize there was an update.  Like the new look too.