Hey all,

I'm working on a Linksys NSS6000 4 disk RAID 5 and I'm having a real problem dealing with Cisco, I must have spoken with every country in the world and no one can help me. Does anyone happen to know the block size for the NSS6000 please?

Thanks in advance,

Adrian

Do you mean working as in trying to recover data from the array?

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

Hi Labtech,

Yes I run a small data recovery company in Australia. 1 disk is pretty much dead and another has bad sectors when imaging with FTK and my DDI. I'm hoping these bad sectors are not my issue as I've tried multiple block sizes. I have been assured that the disk order the customer supplied me is correct...hopefully, as I'm sure we've all heard that before.

I'm at 96% on the DDI now so I'll see how I go once that finishes 1116 unread sectors so far

If anyone here does know the block size that would be one less thing for me to worry about.

Thanks,

Adrian

Sadly, it could be anything. Brief search does not show default block size in any documentation for this device. More research necessary.

No documentation created by customer? Customer checked with their IT person?

Looks like the data volume is XFS based. It will be a little challenging putting this together.

Best wishes

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

These parameters can be identified totally independant of the file system. Customers order may be wrong, offset needs to be identified, block size for NAS usually is 64KB but not always. Also as you have damaged disks its quite likely you will have some stale member present.

It can be determined with "some" certainty only after you have cloned the disk you are working on, but for sure there is no "standard" as every IT put some crazy "creativity" when setting up things (rarely seen things left as out of the box).

I have a feeling you are not the only one / the 1st person putting hands on the system (I hate when it happens : too often when things arrive on my bench they do not require a tech anymore, a disposal service /funeral house/coroner should be the right option - now you get why I always ask a diagnose fee ? )

I've sent a PM. It might be helpful to know what software programs you are trying to use to recovery the RAID array.

_________________
Luke
Recovery Force Data Recovery

out of those 4 if 1 is dead, no problem in Raid5, still can be done
with the bad condition of the rest (other 3) better n always n MUST clone them all
then start from there.

As some here advised, there are many issues not only 1, starting with the HDD Order then finding the block size n Offset
all depends. should know the order 1st. then the rest will be much easier.

Winhex is your friend here in all cases.

good luck

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

you may run into issues if the drive with the bad sectors actually was kicked from the raid a while back and the raid was running in a degraded state.Then the "Dead" drive failed and the raid went boom. if this is the case you may need to revive the dead drive to get the current data from the array.

I see this happen all to often.

Yep...same here.

_________________
Luke
Recovery Force Data Recovery