Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Dear Users,
I have a DSM-G600 with 500 GB HDD.
DSM-G600 status panel shows:
Total Disk Size: 480197164 KB
Used Space: 213786188 KB
Disk Size Remaining: 266410976 KB
But when I copying files from my laptop to DSM-g600 I get the message "Disk Full".
In this case a yellow triangle with an excalamation mark appears in the Windows taskbar notification area! It means: "Virtual Memory is low", but my laptop has 2GB of RAM, and the virtual memory
managed by Windows.
I use XP SP3 / SP2. 1.02eu firmware.
Samba problem? Can't XP access over 213 GB of disk space? or Must I make two partitions?
Thanks!!!
------------------------
Updated information (29 May, 2008) :
I increased virtual memory by hand to 4096-8192 MB last days. The mistake appears in rarer one.
I got one other message (with yellow triangle with exclamation mark of course) this message:
"{Delayed Write Failed}
Windows was unable to save all the data for the file x.
The data has been lost.
This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere."
This is an old Windows problem ( http://support.microsoft.com/kb/321733/ ) and I have SP2/SP3 on XP. I don't understand...
---
Can anybody produce this symptom? Simply copy your windows\system32 directory to your DSMg600 (with 500GB).
Thanks!
Last edited by activer (2008-05-29 12:01:53)
Offline
Have you tried to do a file system check on your DSM-G600 disk. I had a similar problem and used the following procedure to fix it.
1) unmap any drives connected to the DSM-G600 you have mapped on you PC(s)
2) telnet onto the DSM-G600 - instructions on seting up telnet are on this forum
3) find out the disk device name using the 'df' command
4) kill any samba/ftp processes running
5) run command e2fsck /dev/(device from the df command)
6) answer y if it asks you whether you want to Fix
storage login: root
Password:
BusyBox v1.2.1 (2006.08.16-19:37+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
# ps -ef
(kill processes smbd, nmbd, upnp that may be accessing the disk)
# kill id id id etc.....
# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/ram0 5947 4672 968 83% /
/dev/sda2 157044676 126477916 30566760 81% /mnt/HD_a2
# e2fsck /dev/sda2
e2fsck 1.32 (09-Nov-2002)
Pass 1: Checking inodes, blocks, and sizes
Inode 14270491, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270493, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270495, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270497, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270499, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270501, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270503, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270505, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270507, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270509, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270511, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270513, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270515, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270517, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270519, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270521, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270523, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270525, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270545, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270547, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270549, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270551, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270553, i_blocks is 64, should be 8. Fix<y>? yes
Inode 14270555, i_blocks is 64, should be 8. Fix<y>? yes
yyyyyyyyyPass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Pass 3A: Optimizing directories
Optimizing directories: 6815745 9125889 11059201 14254081 14270465 14286849 143
52385 14401537 14434305 14450689 14467073 14483457 14499841 15810561 15892481 15
908865 17727489
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(8667786--8667788) -8668001 -(8668071--8668077) -(86
69106--8669108) -(8669120--8671001) -8671040 -(28541465--28541471) -(28541473--2
8541479) -(28541481--28541487) -(28541489--28541495) -(28541497--28541503) -(285
41505--28541511) -(28541513--28541519) -(28541521--28541527) -(28541529--2854153
5) -(28541537--28541543) -(28541545--28541551) -(28541553--28541559) -(28541561-
-28541567) -(28541569--28541575) -(28541577--28541583) -(28541585--28541591) -(2
8541593--28541599) -(28541601--28541607) -(28541609--28541615) -(28541617--28541
623) -(28541625--28541631) -(28541633--28541639) -(28541641--28541647) -(2854164
9--28541655) -(28541657--28541663) -(28541665--28541671) -(28541673--28541679) -
(28541681--28541687) -(28541689--28541695) -(28541697--28541703) -(28541705--285
41711) -(28541713--28541719) -(28541721--28541727) -(28541729--28541735) -(28541
737--28541743) -(28541745--28541751) -(28541803--28541809) -(28541811--28541817)
Fix<y>? yes
Free blocks count wrong for group #264 (65532, counted=1897).
Fix<y>? yes
Free blocks count wrong for group #265 (65246, counted=0).
Fix<y>? yes
Free blocks count wrong for group #871 (31883, counted=32149).
Fix<y>? yes
Free blocks count wrong (7641674, counted=7641125).
Fix<y>? yes
Free inodes count wrong (19935395, counted=19935394).
Fix<y>? yes
/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
#
Offline