• February 26, 2025, 11:05:19 PM
  • 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.

Author Topic: How to read a RAID1 single drive in Windows after a unit failure  (Read 4807 times)

jose9790

  • Level 1 Member
  • *
  • Posts: 4
How to read a RAID1 single drive in Windows after a unit failure
« on: December 08, 2009, 08:46:54 AM »

Bought a new DNS323, pretty cool the device.  My concern is what to do in case the whole unit in the future fails and I need to read my RAID1 drives.  After created the array and copied information, I removed one drive and connected to usb-sata adapter into my laptop.  Installed linux reader and I couldn't see my files.  Tried from Ubuntu Linux, with no success.  I understand the box is running Linux kernel with ext2 as a file system.  Why can't I read these files? or Is there any other alternative to read the RAID1 in case of a unit failure.

Thank you in advance 
Logged

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: How to read a RAID1 single drive in Windows after a unit failure
« Reply #1 on: December 08, 2009, 12:39:16 PM »

What version of WIndows?
What firmware in the DNS-323?
What "linux reader"?

Upto firmware 1.07 I was able to read the disks from the DNS-323 on a Windows XP system using the ext2ifs installable file system driver.

Although the firmware release notes for the 1.08 beta do not mention any changes to the ext2 disk formats, I have to assume that something changed as a disk formatted ext2 with the beta firmware is no longer readable using the ext2ifs driver
Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.

perfectdark

  • Level 2 Member
  • **
  • Posts: 66
Re: How to read a RAID1 single drive in Windows after a unit failure
« Reply #2 on: December 08, 2009, 12:58:08 PM »

DELETED

I totally mis-understood your sig

« Last Edit: December 08, 2009, 01:56:01 PM by perfectdark »
Logged

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: How to read a RAID1 single drive in Windows after a unit failure
« Reply #3 on: December 08, 2009, 01:47:52 PM »

I see your signature that says RAID 1 is not disk redundancy , don't confuse the two. But if this is true then why is it called RAID ? Which stans for :Redundant Array of Independent Disks
Actually, if you go back and look at his signature, you have misquoted it.  It actually reads:
Quote
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

jose9790

  • Level 1 Member
  • *
  • Posts: 4
Re: How to read a RAID1 single drive in Windows after a unit failure
« Reply #4 on: December 09, 2009, 07:24:46 AM »

Hey guys, the version of Windows is Vista and I am using Firmware 1.07.  The Linux Reader's version is from Diskinternal.  I created one private folder for my LAN and the second folder was setup for FTP purposes and assigned to the FTP server.  After the RAID 1 is setup, copy files in it, I shutdown the DNS and remove one drive and connect it to the SATA-USB adapter then the Vista laptop.  Then, I open Linux reader in Windows and I can open the folder assigned to the FTP server but not the private one. I can see the private folder but it can not be opened. I can do that with Linux reader, in Ubuntu, I can't see the folders, just the mounted icon, it has a lock icon on top of the mounted icon and it won't open.

Logged

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: How to read a RAID1 single drive in Windows after a unit failure
« Reply #5 on: December 09, 2009, 12:06:27 PM »

Jose

I've never used the Diskinternals Linux Reader - try ext2ifs and see if  it works for you - but be aware that some folks have reported problems using it with Vista.
Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.