Is my Duo v1 dead?

If you still see the files, then you are correct - the factory default didn't work.

If you have all the files backed up, try deleting the partitions on drive 1 on a Windows PC, and power up the NAS with only [blank] drive 1 installed.

What happens if you do

# sh /bin/start_raid.sh

?

If using X-RAID post the output of

cat /proc/xraid/configuration

If using Flex-RAID post the output of

cat /proc/mdstat

Many thanks to both of you for replying.

StephenB, I will try your suggestion over the weekend if I get a chance - I'd like to secure another backup before blowing up what at the moment is my only good copy with all the files in 1 place. I do have everything secure, but it would take a bit of effort to put it all back together.

mdgm, as your suggestions only take a few seconds to run, here is what I found;

# sh /bin/start_raid.sh
# echo $?
0
#

# cat /proc/xraid/configuration
VERSION/ID::superblock=(0.1.0),ID=0e2087bf.00000000.00000000.00000000,create_time=516c67a8
RAID_INFO::disks_total=2,raid_disks=2,parity_disk=1,disks_online=1,disks_working=1,disks_failed=1,spare_disk=0,base_disk=0,size=1953108616,update_time=00000000,state=0,luns=2,extcmd=1,expandable_bitmap=0x0,lsize=1953108614,drive_present=0x3
LOGICAL_DRIVE:0:begin_sector=2,sectors=4096000,raid_level=1,status=not_redundant,initialized=0,dmap=2
LOGICAL_DRIVE:1:begin_sector=4096002,sectors=1949012614,raid_level=1,status=not_redundant,initialized=0,dmap=2
PHYSICAL_DRIVE:0:number=0,device=hdc,major=22,minor=0,raid_id=0,state=faulty,present=1,size=1953108616,r_model=ST31000528AS,r_size=1953108616,r_fw=CC38
PHYSICAL_DRIVE:1:number=1,device=hde,major=33,minor=0,raid_id=1,state=online,present=1,size=1953108616,r_model=ST31000528AS,r_size=1953108616,r_fw=CC38
RUN_PARAMETERS::raid_running=1,last_word=ok,interface_start_at=1,fake=0
RAID_REBUILD::sync=0,logical=0,parity=0,sectors=0,total=4294967295,source=2,total_drives=1,auto_sync=1
RAID_P_CHECK::chck=0,current_lun=0,total_luns=2,raid_level=0,err=0,current_sector=0,total_sectors=0,report_err=1
RAID_P_INIT::initialized_bitmap=0x2,initialize_error_bitmap=0x0,initializing_bitmap=0x0,current_sector=0,total_sector=0
#

Now if I read that correctly, it's saying I have 2 drives (both "present"), 1 of which is faulty? Physical drive 0 (can I assume disk 1) is the faulty one? If this is correct - it doesn't make sense - disk 1 is the one I can read the files from through Ubuntu.

My need to check disk 2 and copy everything to it outside of the Duo just increased!!

One other thing; why would the xraid config file suggest both disks are present when the enclosure.log suggests they are not?

Ok, so I've done a bit more digging. I can present disk 2 to my Linux box, partition the drive, create a filesystem across the whole device and then copy all of my files to it without error. I'm taking this as a perfectly working drive - unless someone can explain otherwise :)

I've re-run some of mdgm's suggestions with disk 2 still removed from the Duo. The enclosure.log has been updated as the fan spin rate has changed again (by 300 RPM due to only 1 drive?), but this log is still claiming that I have no disks:

# cat enclosure.log
model!!0!!mode=home::descr=ReadyNAS Duo::arch=nsp
fan!!0!!status=ok::descr=3614RPM
disk!!1!!status=not_present
disk!!2!!status=not_present
#

The xraid config file now has it that drive 2 is "faulty", but present :? and drive 1 is good:

# cat /proc/xraid/configuration
VERSION/ID::superblock=(0.1.0),ID=0e2087bf.00000000.00000000.00000000,create_time=516c5f19
RAID_INFO::disks_total=2,raid_disks=2,parity_disk=1,disks_online=1,disks_working=1,disks_failed=1,spare_disk=0,base_disk=0,size=1953108616,update_time=00000000,state=0,luns=2,extcmd=1,expandable_bitmap=0x0,lsize=1953108614,drive_present=0x1
LOGICAL_DRIVE:0:begin_sector=2,sectors=4096000,raid_level=1,status=not_redundant,initialized=0,dmap=1
LOGICAL_DRIVE:1:begin_sector=4096002,sectors=1949012614,raid_level=1,status=not_redundant,initialized=0,dmap=1
PHYSICAL_DRIVE:0:number=0,device=hdc,major=22,minor=0,raid_id=0,state=online,present=1,size=1953108616,r_model=ST31000528AS,r_size=1953108616,r_fw=CC38
PHYSICAL_DRIVE:1:number=1,device=hde,major=33,minor=0,raid_id=1,state=faulty,present=1,size=1953108616,r_model=UNKNOWN,r_size=1953108616,r_fw=
RUN_PARAMETERS::raid_running=1,last_word=ok,interface_start_at=1,fake=0
RAID_REBUILD::sync=0,logical=0,parity=0,sectors=0,total=4294967295,source=1,total_drives=1,auto_sync=1
RAID_P_CHECK::chck=0,current_lun=0,total_luns=2,raid_level=0,err=0,current_sector=0,total_sectors=0,report_err=1
RAID_P_INIT::initialized_bitmap=0x1,initialize_error_bitmap=0x0,initializing_bitmap=0x0,current_sector=0,total_sector=0
#

I'd really appreciate any comments on this. I feel that I need to either fix this or replace the unit - afterall, I don't have to repalce the disks!!

That's not the way to detect a failing disk. Hook the drive up to an internal SATA port in your Linux box, boot off the Ultimate Boot CD and check the health of the disk using the manufacturer's tool e.g. SeaTools for SeaGate disks.

Odd. The earlier post suggested disk 1 (0) not disk 2 (1) was faulty whilst your latest post in this threads suggests the opposite. Do you have an explanation for this?

Tech support mode is a low level diagnostics mode. In this mode the disk status isn't necessarily accurately reported in the enclosure.log file.