I just bought some new hard drives to expand my nas storage. Started copying some files over. First set of files moved over just fine. Tried a bunch more movie files (a few gigs each, some fairly large 10GB-15GB) and windows is telling me there isn't enough space.

 

This is my array right now:

 

This is what windows tells me:

 

What the hell is going on? I did some googling and read something about split level and min free space but maybe I'm not understanding correctly. No matter what settings I make, files still arent allowed to be copied over.

 

Post the diagnostics.  Have you ever had a cache drive installed?

Any one of your disks has plenty of space, so something clearly isn't working right.

 

Did you ever have a share set as "cache only" ??

(Not likely unless you had a cache drive at some point)

 

Post what the Settings - Global Share Settings page shows.

 

No, I've never had a cache drive installed nor set a share as 'cache only'

 

Also not sure what you mean by 'post diagnostics'. Do you mean the log?

 

Found the diagnostics section.

tower-diagnostics-20161126-1049.zip

How big was the complete set of files you were trying to copy when you got the message you posted above from Windows?(The one that says you need an extra 13.2GB)

 

And were you copying it to a share (e.g. "media") or to a disk share (e.g. "disk1") ?

 

I dont have any disk shares set up (In fact, Im not even sure how. When I try to add a share, it only wants to add a user share)

 

8 movies (8 folders some with subfolders) total size is just under 40 gigs.

 

Disk 4 doesn't look very well. It has failed a number of self tests in the past. I'd run another extended test on it.

 

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Extended offline    Completed: read failure      90%    20668        993587

# 2  Short offline      Completed: read failure      80%    20654        993587

# 3  Short offline      Completed: read failure      50%    20650        993587

# 4  Short offline      Completed: read failure      90%    20649        993587

# 5  Short offline      Completed without error      00%    19446        -

Disk 4 doesn't look very well. It has failed a number of self tests in the past. I'd run another extended test on it.

 

Why would it be showing green in the Main section? That seems...odd. Running an extended test. Would that actually cause this error though? I can certainly replace the drive.

I dont have any disk shares set up (In fact, Im not even sure how. When I try to add a share, it only wants to add a user share)

 

8 movies (8 folders some with subfolders) total size is just under 40 gigs.

 

You don't "set up" disk shares -- you either enable them or not.  Settings - Global Share Settings - Enable Disk Shares

 

In any event, 40GB should NOT have been an issue.  Do they work okay if you copy one movie at a time (or one folder at a time) ??

 

... Would that actually cause this error though?

 

No, it shouldn't have any bearing on the copying issue.  In fact, UnRAID hasn't had any issues with it -- it's only the SMART test that shows errors.    I would, however, be tempted to replace the drive based on the SMART data.

 

Both disk3 and disk4 are being mounted read-only. Check their filesystems.

 

Nov 25 15:11:41 Tower logger: mount: block device /dev/md3 is write-protected, mounting read-only

 

Nov 25 15:11:41 Tower logger: mount: block device /dev/md4 is write-protected, mounting read-only

 

In fact the file system looks so badly damaged unRAID can't determine what type it is, trying several and finally giving up.

 

Nov 25 15:11:41 Tower emhttp: shcmd (56): mkdir -p /mnt/disk3

Nov 25 15:11:41 Tower emhttp: shcmd (57): set -o pipefail ; mount -t auto -o noatime,nodiratime /dev/md3 /mnt/disk3 |& logger

Nov 25 15:11:41 Tower logger: mount: block device /dev/md3 is write-protected, mounting read-only

Nov 25 15:11:41 Tower kernel: REISERFS warning (device md3): sh-2021 reiserfs_fill_super: can not find reiserfs on md3

Nov 25 15:11:41 Tower kernel: EXT4-fs (md3): VFS: Can't find ext4 filesystem

Nov 25 15:11:41 Tower kernel: EXT4-fs (md3): VFS: Can't find ext4 filesystem

Nov 25 15:11:41 Tower kernel: EXT4-fs (md3): VFS: Can't find ext4 filesystem

Nov 25 15:11:41 Tower kernel: FAT-fs (md3): bogus number of reserved sectors

Nov 25 15:11:41 Tower kernel: FAT-fs (md3): Can't find a valid FAT filesystem

Nov 25 15:11:41 Tower kernel: FAT-fs (md3): bogus number of reserved sectors

Nov 25 15:11:41 Tower kernel: FAT-fs (md3): Can't find a valid FAT filesystem

Nov 25 15:11:41 Tower kernel: REISERFS warning (device md3): sh-2021 reiserfs_fill_super: can not find reiserfs on md3

Nov 25 15:11:41 Tower kernel: EXT4-fs (md3): VFS: Can't find ext4 filesystem

Nov 25 15:11:41 Tower kernel: EXT4-fs (md3): VFS: Can't find ext4 filesystem

Nov 25 15:11:41 Tower kernel: EXT4-fs (md3): VFS: Can't find ext4 filesystem

Nov 25 15:11:41 Tower kernel: FAT-fs (md3): bogus number of reserved sectors

Nov 25 15:11:41 Tower kernel: FAT-fs (md3): Can't find a valid FAT filesystem

Nov 25 15:11:41 Tower kernel: FAT-fs (md3): bogus number of reserved sectors

Nov 25 15:11:41 Tower kernel: FAT-fs (md3): Can't find a valid FAT filesystem

Nov 25 15:11:41 Tower kernel: ISOFS: Unable to identify CD-ROM format.

Nov 25 15:11:41 Tower kernel: hfsplus: unable to find HFS+ superblock

Nov 25 15:11:41 Tower kernel: UDF-fs: warning (device md3): udf_load_vrs: No VRS found

Nov 25 15:11:41 Tower kernel: UDF-fs: warning (device md3): udf_fill_super: No partition found (2)

Nov 25 15:11:41 Tower kernel: XFS (md3): Invalid superblock magic number

Nov 25 15:11:41 Tower logger: mount: you must specify the filesystem type

Nov 25 15:11:41 Tower emhttp: shcmd: shcmd (57): exit status: 32

Nov 25 15:11:41 Tower emhttp: mount error: No file system (32)

Nov 25 15:11:41 Tower emhttp: shcmd (58): rmdir /mnt/disk3

 

The situation is very similar for disk4.

 

Do they work okay if you copy one movie at a time (or one folder at a time) ??

 

- First one (3.5 GB) transferred ok, albeit a little slowly (~60MB/s)

- Second one (9GB) started out at ~60MB/s, settled at 40MB/s a few seconds in

- Third one (2.5 GB) started out around 80MB/s, settled at 30-35MB/s. Similar story for the remaining movies. So, seems I can transfer these one by one.

 

Worth noting that before when I was transferring a large number of files at once, I was saturating my network speeds. ~115MB/s read speed from my local raid0 array, ~980Mb/s network speed

In fact the file system looks so badly damaged unRAID can't determine what type it is, trying several and finally giving up.

 

The situation is very similar for disk4.

 

So, if disk4 is having smart problems, and both 3 and 4 are having filesystem/mount problems, why would Unraid be reporting all-is-well and they're operating normally? How would one even know something wrong until something like this happens? Seems awfully backwards to me...

Both disk3 and disk4 do successfully mount a couple of minutes later though (15:13:04).

 

Could it be a power supply issue? What make/model of PSU do you have? I'd check all power connections/splitters to disks.

 

Both disk3 and disk4 do successfully mount a couple of minutes later though (15:13:04).

 

Could it be a power supply issue?

 

I suppose it could be. I am using a slightly older power supply. Those drives are also connected via a fairly old backplane. I can take the backplane out of the equation

What is the exact model of your power supply?

Just to clarify, the system saw disk3 and disk4 as write-protected and attempted to mount them read-only but couldn't work out what file system they were using, so gave up. A little later they both mounted cleanly. The only thing I can think of that might cause this is intermittent power supply.

 

What is the exact model of your power supply?

 

Coolermaster CX430M

So, I just tried to transfer a large number of movies to the Movies folder and got the not-enough-space error like I mentioned. I navigated outside of the Movies folder to the root of the share, and am able to initiate the entire transfer.

 

Wat.

If I transfer my entire Movies directory from my local raid, to the root share where the Movies directory is, the transfer initiates. ~200GB at 30MB/s. Extremely slow but its transferring...

So, if disk4 is having smart problems, and both 3 and 4 are having filesystem/mount problems, why would Unraid be reporting all-is-well and they're operating normally? How would one even know something wrong until something like this happens? Seems awfully backwards to me...

 

One thing a computer really has to take for granted is a reliable power supply. If hardware components get switched on and off at random you really can't expect the operating system to track them. It's essentially a hardware fault and with hardware faults all bets are off.

 

So, I just tried to transfer a large number of movies to the Movies folder and got the not-enough-space error like I mentioned. I navigated outside of the Movies folder to the root of the share, and am able to initiate the entire transfer.

 

You need to fix the underlying problem before trying to add more data to your array.

 

I don't recognise that PSU, BTW. It looks like a Corsair model number.

 

 

You need to fix the underlying problem before trying to add more data to your array.

 

I don't recognise that PSU, BTW. It looks like a Corsair model number.

 

We haven't identified the underlying problem. Im not convinced the powersupply is to blame here.

 

It's not a corsair power supply. It is a coolermaster power supply.

Fair enough. I'll shut up then.