Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
http://forums.dlink.com/index.php?topic=4489.0
The Deskstar 7K1000.B - Model HDT721010SLA360 hitachi drives are currently not supported we are looking into this issue.
Very upsetting. I just bought the drives and NAS in February. I'm trying to look into it further, but it seems the problem is the drives won't be recognized if you boot up the NAS enclosure after it's been shutdown. If you simply reboot, then the drives will be recognized again.
This isn't too big of an issue for me, but I'm trying to track down if this is related to another problem i just uncovered:
One of my drives has degraded serverely. My lesser used backup drive still saturates the fast ethernet connection at 10MB/sec. But the drive I used to run a few bittorrents (only a few), has already degraded to 3MB/sec.
I now have my NAS turned off so I don't ruin my drives any further. I've also contacted Hitachi for some assistance. Are these the guys I should be talking to? Would D-LINK care? I don't think my vendor will care anymore.
Has anyone else had these issues?
Offline
I don't think you've ruined the drive - I think it's just fragmented. Unfortunately there doesn't seem to be any tools available to defrag and ext2 file system, so you have to find an alternative way to do it.
Here's something you could try - copy all the files of the "degraded" drive, reformat it, and copy them back - now run whatever test you ran and see if it "saturates the fast ethernet connection" again.
Let me know how it goes
Offline
Phew,
I backed up all of my stuff today, and reformatted the drive. You were right - it was just fragmented.
What does that mean for the future? The drives/NAS are only a month old.
Would it make sense to have downloads on a seperate partition? Can I do that easily?
I'll continue to do research on my own.
Offline
What does it mean for the future? I wish I had an answer for that.
I half expected someone to jump on my case for suggesting that an ext2 drive could be fragmented - the generally held view is that the linux ext2 & ext3 files systems do not fragment in the same way that the Windows FAT & NTFS file systems do, and therefore do not need to be defragmented.
As a result - this is now my opinion - the necessary tools to do it have been neglected and the only way to do it, is the rather cumbersome, backup/reformat/restore process that you went through.
I'm not the best person to tell you what the options are - not being a BT user - I have limited experience with it, but, from the postings and the experiences of others like yourself, I've come to recognize that the nature of the process is to download files in fragments rather than one contiguous chunk and this apparently leads to them being stored in a fragmented nature on the disks.
It is, I suppose, possible that other BT clients may not work in this way, or, may or may not have the same problem to a greater or lesser extent - there's no reason why a BT client could not be written so that it creates a temp file where it assembles the torrent from the fragments and then copies that file elsewhere and either reuses it's fragmented "scratch area" or deletes it - so a change to a different BT client might be one option.
As you suggest having a separate small partition (the "scratch area" I describe above) could be another, but on a DNS-323 that potentially leads to other problems as the device does not really allow for custom partitioning.
I leave it to the linux gurus and the DNS-323 masters to guide you from here.
Offline
It would be interesting (if this happens in the future) to see the output of
# e2fsck -nv /dev/sda2 (or sdb2)
for the degraded drive and compare that output to a "good" drive
to see the extent of the BT fragmentation.
Offline
I am not using BT, and have a different type of 1TB discs, BUT I apparently have degraded drives AND I am interested in the level of defragmentation with regards to FW 1.06 which I am still having problems with. I installed ffp 0.5, then ran telnet from a dos window. This is the exchange 'snipped out'
/ # e2fsck -nv /dev/sda2
e2fsck 1.41.0 (10-Jul-2008)
e2fsck: Device or resource busy while trying to open /dev/sda2
Filesystem mounted or opened exclusively by another program?
/ # e2fsck -nv /dev/sdb2
e2fsck 1.41.0 (10-Jul-2008)
e2fsck: No such device or address while trying to open /dev/sdb2
Possibly non-existent or swap device?
/ #
OK, that clearly did not work. And yes there is only one disc in this DNS-323.
I searched and read something about needing to dismount in one article and not needing to dismount in another. So what do I do next?
Biscotte
Offline
Biscotte wrote:
I searched and read something about needing to dismount in one article and not needing to dismount in another. So what do I do next?
If you want e2fsck to repair your filesystem then you need to unmount it (the filesystem)
However the -n option tells e2fsck not to make any changes to the fileystem, and the -v
option tells e2fsck to be verbose in the output.
I'm not sure why you are seeing those errors? This is the output of the command on my DNS-323,
with a single 'test' 80GB drive - showing .2% fragmentation.
/ # e2fsck -n /dev/sda2
e2fsck 1.41.0 (10-Jul-2008)
Warning! /dev/sda2 is mounted.
/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? no
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (18679449, counted=18678407).
Fix? no
Free inodes count wrong (9646098, counted=9646090).
Fix? no
/dev/sda2: ********** WARNING: Filesystem still has errors **********
/dev/sda2: 4078/9650176 files (0.2% non-contiguous), 596542/19275991 blocks
Offline