futeko.com FORUM
Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: B16 KJR on June 11, 2019, 12:25:51 PM
-
Hi
I have started to get a strange problem whilst trying to transfer videos from my Windows 10 PC (version 1903) via Samba to my Q10 Pro media box which is fitted with a 2TB HDD. I keep getting an error message telling me there isn't enough space on the hard drive, but I know there is plenty of room left on it. I have accessed the disk via my PC and deleted loads of videos so I know the 'connection' between PC and Q10 is working OK.
I have attached a screen shot showing there is only 208GB of HDD space being used and another screen shot showing the error message telling me there isn't enough disk space to transfer a 3.6GB file ?
I have rebooted the Q10 and performed a disc clean but it hasn't made any difference. Can anyone help ?
Kenny
-
Check this post for solution: https://www.futeko.com/newforum/index.php?topic=4265.msg28422#msg28422 (https://www.futeko.com/newforum/index.php?topic=4265.msg28422#msg28422)
What FW version are you on?
-
Hi
I am on the latest 2.1.1 version of the FW.
I have tried the disk check on Windows 10 and it reported no errors, I then tried the command prompt chkdsk and it came up with errors and recommended a chkdsk / scan which then gave the message 'access denied' something about it being an NTFS file ?
I am in the process of transferring all the content from the HDD onto my laptop and will reformat the HDD and then transfer the content back onto it but I'm pretty certain that its got something to do with the Windows 10 1903 update as my 2nd Q10 box is now doing exactly the same thing ?
-
Hi
I have reformatted the HDD and transferred all my content back onto it, but the problem persists. I have discovered that I can transfer a small 450mb file , but anything approaching 900mb and I get the error message about there not being enough space on the disk space.
I have read the post by pcristi in the link above about how the network drive should be mapped and mine is done correctly and hasn't changed, the only thing that has changed is the update to Windows 10 version 1903 and as both of my Q10 boxes are affected that is the only common link between them both.
Can anyone suggest any other course of action other that rolling back to version 1809 of Windows 10 ?
-
Exactly what procedure did you use to reformat the hard drive?
-
Hi
I connected my laptop to the back of the Q10 with a usb cable and used 'Mini Tool Partition Wizard' to reformat the drive. I did notice a small partition on the drive which I was going to reformat again today without any partitions, but last night I decided to roll back to Windows 10 version 1809 and everything is back to normal and I can once again send large files using SAMBA.
I will try reformatting the HDD again today and removing that small partition just in case with version 1903 it is only reading the capacity of the small partition rather than the rest of the HDD, if that's the case there must be some sort of change between versions, as 1809 works fine.
-
Please check if on Windows 10 version 1809 your sda2 is report as 8TB?
As I know Windows 10 version 1903 fixed that errors.
Map drive of sda2 is report real size of HDD partition, map drive of media_rw will report free space of box as need ~3.6GB and map drive of shared will report free space on internal partition ~980MB.
-
Hi
I've never seen the sda2 ever being reported as 8TB, how would I check as when I go into 'properties' it only tells me the amount of space that is being used on the HDD.
I am in the process of transferring all the media off the HDD and was going to reformat the HDD as a simple volume without the small partition, is that the correct thing to do ? Not sure why there is a small partition on the HDD anyway ?
-
-
Note :- after reformatting the drive and moving the partition, the HDD has somehow renamed itself sda1 instead of sda2 which it was before ?
That would be right as you removed the extra partition, the first partition should be sda1, the second sda2 and so on.
-
That would be right as you removed the extra partition, the first partition should be sda1, the second sda2 and so on.
I didn't realise that, but it makes sense now, thanks for explaining it. Any ideas regarding the rest of my problem ?
-
-
Hi
I can't see it being an issue with the disc, if it was, I wouldn't be able to have it working OK from my PC on version 1809 but not from my laptop on version 1903 ? However its very handy to have that information for future reference.
I just have a desktop shortcut icon for both my Q10's so that I can just copy and paste movies directly into themon my desktop, which is very handy.
pcristi seemed to know what was going on, but he hasn't replied to the last post yet, hopefully he can come back with a solution. At least I was able to roll back my PC to version 1809, I was just outside the 10 days with my laptop, so the option was no longer available for me.
-
Hi B16 KJR, I can confirm there is a problem with the later Window 10 builds, although I am not running Build 1903, one of my machines is running a very late preview (20H1 Build 18917).
The same problem exists on this machine it cannot copy larger files. I tried to copy a 1.8GB file to the q10 and I get the not enough disk space error.
Disk space reports are all over the place for the samba drive. They do report correctly for Windows machines (both remotely and local).
You can try this on your machines, you will get different results between builds 1809 & 1903.
Got to a command prompt and map a drive to the Q10, I mapped z drive. At the prompt type (you can use your IP address) eg: net use z: \\192.168.x.x\share
Now type at the prompt:- wmic logicaldisk get size,freespace,caption
With the drive still mapped, you can also try this from the PowerShell Prompt:- get-psdrive | Where Free*
Going into the share in file explorer and selecting properties on the folder does seem to give the correct used space.
-
Testing SMB copy.
My case HDD partition is sda5 and is Windows 10 19H1(18362.175) / Windows 10 20H1(18917.1)
Not map driver direct browse network \\Android_XXX\share\media_rw\sda5
map X: \\Android_XXX\share\media_rw
map Y: \\Android_XXX\share
Try copy more that 1GB files --> FAILED
(https://www.mediafire.com/convkey/f546/7v3nefuqi48p26uzg.jpg?size_id=3)
map V: \\Android_XXX\share\media_rw\sda5
(right click on V: to see HDD free space)
(http://www.mediafire.com/convkey/1a59/bnw51hci8vipxv9zg.jpg?size_id=3)
Try copy more that 1GB files --> SUCCESS
(https://www.mediafire.com/convkey/a5ba/x2x733pqbv72ku1zg.jpg?size_id=3)
(http://www.futeko.com/newforum/index.php?size_id=3)
-
....
The same problem exists on this machine it cannot copy larger files. I tried to copy a 1.8GB file to the q10 and I get the not enough disk space error.
Disk space reports are all over the place for the samba drive. They do report correctly for Windows machines (both remotely and local).
You can try this on your machines, you will get different results between builds 1809 & 1903.
Got to a command prompt and map a drive to the Q10, I mapped z drive. At the prompt type (you can use your IP address) eg: net use z: \\192.168.x.x\share
Now type at the prompt:- wmic logicaldisk get size,freespace,caption
With the drive still mapped, you can also try this from the PowerShell Prompt:- get-psdrive | Where Free*
Going into the share in file explorer and selecting properties on the folder does seem to give the correct used space.
From my point of view PowerShell get-psdrive | Where Free* is report correct for z: \\192.168.x.x\share
Name Used (GB) Free (GB) Provider Root
----- ---------- ---------- ----------- --------
Z 0,00 0,92 FileSystem \\192.168.x.x\shareshare is tmpfs as can see on smb.conf
[share]
hide dot files = yes
hide files = /.*/lost+found/
available = yes
browseable = yes
create mask = 0777
directory mask = 0777
path = /mnt
writable = yes
valid users =
guest ok = yes
force user = root From adb shell df
tmpfs 964752 0 964752 0% /mnt
-
Nice one pcristi on remapping the drive to sda(x), this also worked for me. Although really a work around for a problem that does not exist on 1809 build.
The disk reporting results are different from Build 1809 and later builds.
Yes, you are right the Powershell command on the later builds does give the correct disk info.
My results-> z: \\192.168.x.x\share y: \\192.168.x.x\share\ media_rw\sda1
Build 1809
Command Prompt
Caption FreeSpace Size
Y: 18446744073709550592 18446744073709550592
Z: 18446744073709550592 18446744073709550592
Powershell
Name Used (GB) Free (GB) Provider Root
---- --------- --------- -------- ----
Y 0.00 ...9869184.00 FileSystem \\192.168.x.x\share\media_rw\sda1
Z 0.00 ...9869184.00 FileSystem \\192.168.x.x\share
Build 18917 (20H1)
Command Prompt
Caption FreeSpace Size
Y: 907374997504 1000202039296
Z: 991301632 991301632
PowerShell
Name Used (GB) Free (GB) Provider Root
---- --------- --------- -------- ----
Y 86.45 845.06 FileSystem \\192.168.x.x\share\media_rw\sda1
Z 0.00 0.92 FileSystem \\192.168.x.x\share
-
Hi
Many thanks for all the replies, but I'm afraid that using Powershell commands and suchlike, are a bit beyond my technical ability !!
Joker, you did say that you could confirm that there is a problem with the later Windows 10 builds, do you think this is something that Microsoft will be aware of and are likely to fix ? Is there any simple way around this problem ?
-
-
Maybe a nooby question, but does this drive mapping have any impact on SAMBA transfer speeds?
-
Hi
Many thanks for the detailed simple instructions Joker, I have done as you suggested and it is all working again. It didn't reconnect to the drives automatically after a restart, even though I ticked the 'reconnect at sign in box' but that may resolve itself though updates hopefully ?
Doing it this way is very handy, as I can now see exactly how much space is left on the HDD's when looking at them via 'This PC'. I just disconnected the old mapped drive letters and paths and they seem to have vanished, I did try the cmd prompt Z:/d but it said it couldn't find them ?
I will now set up my PC the same way and then see if I can get the 1903 update again, but I don't know if it will be available as I had it then rolled back ?
pcristi, apologies, I didn't pick up on the fact that you had already offered the solution, I was getting really confused by that stage.
Thanks to everyone who offered their help.
Kenny
-
-
Maybe a nooby question, but does this drive mapping have any impact on SAMBA transfer speeds?
Nope, no noticeable difference, same crappy speeds. But at least it works!
-
Hi, the other day I went to copy some video files to the q10 pro network and it would not let me because it said that there was not enough space in the shared folder when I have more than 2tb free on the hard disk.
Does anyone know why this happens?
-
By the way, in my Windows PC has been updated to the 1903 version, will it have something to do? the samba configuration?
-
I've tried teracopy and it seems to be going well.
with the windows explorer is not going well
-
Joker, do you know if there is any way to get the 1903 update back on my PC, given that I already had it then rolled back to the 1809 version ?
Also thanks again to pcristi for all his help.
-
Sure, you can use the Windows Media Creation Tool or the update assistant. If you follow this link it should step you through it.
https://www.microsoft.com/software-download/windows10
-
Thanks a lot, Cristi ! It works indeed by mapping.
-
I'm having this same exact issue right now. Everything was perfect for the last 2 years transfering to both my HD10 and KDLinks boxes. Then Windows just installed a few updates for Windows 10 that is giving me the same error about not enough space. The updates installed were:
Feature update to Windows 10, version 1903
KB4505903
KB4506991
Ever since then I can't use Samba anymore. I tried a system restore but it didn't go through, said it might be my anti-virus blocking it. Then I tried manually uninstalling the updates but it made no change. It has to be one of the updates thats doing it as I'm trying to send to two different boxes/drives and am getting the same error about no space.
I'm going to try re-mapping that was mentioned in this thread. What a pain in the ass Microsoft is.
UPDATE: Thank you so much to Pcristi for the fix and to Joker for dumbing it down to a point I could understand what to do. You guys are the absolute best! I mapped both drives and I can transfer files to them again and even see how much disk space they have under My PC.
P.S. I Hate You Microsoft!
-
having the exact same issue here with win 10 1903, seems indeed to be a bug.
i use FastCopyPortable as a temporary solution until m$ patches it.
-
Unfortunately I also have the same problem with Windows 1903, and I'm solving the problem, using Teracopy (https://www.codesector.com/teracopy).
(https://i.postimg.cc/g0MCbq6Y/Ridimensiona-di-Screenshot-001.png)
(https://i.postimg.cc/sXqbvjcq/Ridimensiona-di-Screenshot-002.png)
-
hello, since I installed windows11 from the V:Androidxxxx\share\media_RW\ the sda1 folder has disappeared and consequently I do not sell the hard disk connected inside the box.
How can I do ? i can't mapping :( :'(