• February 23, 2025, 03:36:31 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: [1] 2

Author Topic: Scan Disk Fails  (Read 24608 times)

ttmcmurry

  • Level 4 Member
  • ****
  • Posts: 438
Scan Disk Fails
« 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

« Last Edit: May 16, 2009, 09:38:13 AM by ttmcmurry »
Logged

Arvald

  • Level 3 Member
  • ***
  • Posts: 108
Re: Scan Disk Fails
« Reply #1 on: May 16, 2009, 10:09:24 AM »
Hardware Version: B1
Firmware Version: 1.08
Software Version (Easy Search): none

Harddrive 1: 
Harddrive 2:  WDC WD1001FALS-00J7B

Same issue
Logged

drick

  • Level 3 Member
  • ***
  • Posts: 270
Re: Scan Disk Fails
« Reply #2 on: May 16, 2009, 10:49:28 AM »
+1 for the scandisk error, doesn't work for me either.

2x400 HDS HDD's in a RAID 1
« Last Edit: May 18, 2009, 02:37:45 PM by drick »
Logged
DNS-323v1.8 + ffp 0.5
2x750GB Seagate HDD's / RAID1+EXT3
DNS-343A - retired due to faulty fan
DNS-343B - retired due to faulty fan
DNS-343C v1.05b + ffp 0.5
4x2TB Seagate HDD's / RAID5+EXT3
Netgear RNDP6000
6x2TB WD HDD's / RAID6
Netgear WNDR4500

lizzi555

  • Level 5 Member
  • *****
  • Posts: 605
Re: Scan Disk Fails
« Reply #3 on: May 16, 2009, 10:53:34 AM »
Same here with Raid 0 / Ext3 - 2 x Samsung HD501LJ
Logged

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: Scan Disk Fails
« Reply #4 on: May 16, 2009, 01:41:21 PM »
Problem as posted by ttmcmurry -

HW version - A1
FW version - 1.08
SW version - none

HDD1 - Maxtor 6Y080M0
HDD2 - Maxtor 6Y080M0

RAID1 with ext2
Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.

sgip2000

  • Level 2 Member
  • **
  • Posts: 77
Re: Scan Disk Fails
« Reply #5 on: May 16, 2009, 10:04:28 PM »
Fails for me too with 2 Seagate 1.5TB in RAID 1.
Logged

ECF

  • Administrator
  • Level 11 Member
  • *
  • Posts: 2692
Re: Scan Disk Fails
« Reply #6 on: May 18, 2009, 12:02:59 PM »
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
Logged
Never forget that only dead fish swim with the stream

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: Scan Disk Fails
« Reply #7 on: May 18, 2009, 12:59:49 PM »
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.
Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.

Arvald

  • Level 3 Member
  • ***
  • Posts: 108
Re: Scan Disk Fails
« Reply #8 on: May 18, 2009, 01:11:58 PM »
I'm not RAIDed here so point 2 is moot fordem
Logged

lizzi555

  • Level 5 Member
  • *****
  • Posts: 605
Re: Scan Disk Fails
« Reply #9 on: May 18, 2009, 01:15:53 PM »
Quote from: 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 ....
 ;)
Logged

ECF

  • Administrator
  • Level 11 Member
  • *
  • Posts: 2692
Re: Scan Disk Fails
« Reply #10 on: May 18, 2009, 02:01:28 PM »
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.
Logged
Never forget that only dead fish swim with the stream

drick

  • Level 3 Member
  • ***
  • Posts: 270
Re: Scan Disk Fails
« Reply #11 on: May 18, 2009, 02:41:15 PM »
Quote from: ECF on May 18, 2009, 02:01:28 PM
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.
Logged
DNS-323v1.8 + ffp 0.5
2x750GB Seagate HDD's / RAID1+EXT3
DNS-343A - retired due to faulty fan
DNS-343B - retired due to faulty fan
DNS-343C v1.05b + ffp 0.5
4x2TB Seagate HDD's / RAID5+EXT3
Netgear RNDP6000
6x2TB WD HDD's / RAID6
Netgear WNDR4500

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: Scan Disk Fails
« Reply #12 on: May 19, 2009, 11:38:18 AM »
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..
« Last Edit: May 19, 2009, 11:44:08 AM by fordem »
Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.

ttmcmurry

  • Level 4 Member
  • ****
  • Posts: 438
Re: Scan Disk Fails
« Reply #13 on: May 19, 2009, 08:01:43 PM »
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:

Code: [Select]
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.
« Last Edit: May 19, 2009, 08:34:07 PM by ttmcmurry »
Logged

PhillB

  • Level 1 Member
  • *
  • Posts: 24
Re: Scan Disk Fails
« Reply #14 on: May 21, 2009, 11:26:31 AM »
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.
Logged
Pages: [1] 2
« previous next »