D-Link Forums
The Graveyard - Products No Longer Supported => DNS-323 => D-Link Storage => Beta code! => Topic started by: ttmcmurry on May 16, 2009, 09:36:20 AM
-
Hardware Version: B1
Firmware Version: 1.08
Software Version (Easy Search): none
Harddrive 1: Seagate ST31000340AS 5QJ0MV1L 1000 G
Harddrive 2: Seagate ST31000340AS 5QJ0MVKZ 1000 G
Problem Type: Scan disk fails to run
X Error message X Function does not work □ Enhancement □ UI Wording □ Other:___________
Problem Description: Scan disk fails to run
Function Tested: Scan disk
Test Procedure (steps to reproduce): Click on "Scan disk" and it fails
(http://img190.imageshack.us/img190/6527/323scanfail.png)
-
Hardware Version: B1
Firmware Version: 1.08
Software Version (Easy Search): none
Harddrive 1:
Harddrive 2: WDC WD1001FALS-00J7B
Same issue
-
+1 for the scandisk error, doesn't work for me either.
2x400 HDS HDD's in a RAID 1
-
Same here with Raid 0 / Ext3 - 2 x Samsung HD501LJ
-
Problem as posted by ttmcmurry -
HW version - A1
FW version - 1.08
SW version - none
HDD1 - Maxtor 6Y080M0
HDD2 - Maxtor 6Y080M0
RAID1 with ext2
-
Fails for me too with 2 Seagate 1.5TB in RAID 1.
-
I had Success
1 WDC WD400JD-22LSA0 WD-WMAM9CD19226 40 G
2 WDC WD400JD-22MSA1 WD-WMAM9LD69685 40 G
I will try some other larger drives I have here next
-
I don't know what part this plays - but - I pulled one of the two 80GB drives and formatted the other (and had some difficulties there, but that is in another thread - and scan disk now works on the 80GB drive, I will at some point reconfigure the RAID array and try again, but right now there are two possible directions this can go in - 1 - scan disk doesn't work unless the drives gave been formatted with 1.08 - or - 2- scan disk doesn't work on a RAID array.
More after I've done a little more testing.
-
I'm not RAIDed here so point 2 is moot fordem
-
- 1 - scan disk doesn't work unless the drives gave been formatted with 1.08 -
I built new Raid 0 and formatted with Ext3 - Scandisk did not work. So point 1 ....
;)
-
I am using Ext2 still I have not yet reformatted after updating the firmware to 1.08 and in a RAID1 configuration for my successful disk scan.
-
I am using Ext2 still I have not yet reformatted after updating the firmware to 1.08 and in a RAID1 configuration for my successful disk scan.
just reinitialized the box with 2x750gb Seagate ST3750640NS HDD's in a RAID 1 with ext3.
scandisk is now running on them, and appears to be working.
-
OK here's my findings so far.
I've run scandisk on ...
- an ext2 RAID1 volume (formatted with 1.06) - failure
- an ext2 standard volume (formatted with 1.08) - successful
- an ext3 standard volume (formatted with 1.08) - successful
- an ext3 RAID1 volume (formatted with 1.08) - failure
Out of curiosity what exactly is scan disk supposed to do? Presumaby find and fix errors.
What does the failure mean? That it did not find errors, that it found errors and did not fix them or that it did not run?
What does successful mean? That it did not find errors or that it found errors and fixed them?
It would be nice to have a little more verbose output messages - along the lines of - no errors found, nn errors found, nn errors fixed, aa errors found, bb crosslinked blocks, cc orphan blocks, dd fragments - etc., etc., etc..
-
Good point-- is the WI running fsck, e2fsck, or something else?
When i drop to telnet and run fsck on anything (/dev/md0, /dev/sda2, /dev/sdb2, etc), i get an error like the following:
root@BigBox:~# fsck /dev/md0
fsck 1.41.0 (10-Jul-2008)
fsck: fsck.ext2: not found
fsck: Error 2 while executing fsck.ext2 for /dev/md0
e2fsck gives me errors about checking a mounted volume.. if the WI uses it, then how does it handle the mounted volume .. umount /dev/md0 ? then mount it back ? it's not possible to umount /dev/md0 while ffp is running since the telnet server is running from /dev/md0 (it's a chicken & egg issue). so how does this occur via the WI?
i love this stuff, lol.
-
After running scandisc with success the only option then available is restart. Why does the DNS-323 need to restart after a successful scandisc?
Thanks,
Phill.
-
I am using Ext2 still I have not yet reformatted after updating the firmware to 1.08 and in a RAID1 configuration for my successful disk scan.
I just formated the drives into RAID1 using EXT3 and the scan completed successful..Same drives I'll try another model next.
-
After I run a successful scandisk the disk tools page then just shows "restart" with no other possibilities. Even after restarting the DNS-323 the option to run a further scandisc is no longer available, the only option still being "restart".
Thanks,
Phill.
-
For me it was working successfully. - But after disk scan, the DNS-323 showed me that both harddrives where formated. :o
I made a restart of the whole device. After this the data "HARD DRIVE INFO" was shown correctly in the status window.
Slot Vendor Model Serial Number Size
1 SAMSUNG HD642JJ S1AFJ9BQ906481 640 G
2 SAMSUNG HD642JJ S1AFJ9BQ906477 640 G
EXT2
RAID0
-
Scandisk was unsuccessful, and it killed smbd and nmbd in the process...
-
This feature is on the bug list it is not a completed function right now.
http://forums.dlink.com/index.php?topic=5621.0
-
So I wasn't going crazy. :)
As indicated in another post, I did perform a factory reset of my 323 for another reason. However I did check to see if it resolved the scandisk problem and it didn't correct the issue.