300GB SAS shows 140

[einstein9]

Dear Experts (specially Doomer)

i got 4 SAS drives (seagate) in RAID, but noticed this issue which is strange really

SAS Controller reports correct size, but Windows reads it as 140GB

the problem is this applies to ALL 4 drives, not only one, which i suspect here

any clues...

thnx

[Vulcan]

SAS Controller reports correct size

So this is not problem with the drives themselves.

but Windows reads it as 140GB

Therefore IMHO much more detail needed about:

- the RAID configuration;
- exactly where you are looking when you say that "Windows reads it as 140GB";
- details of customer's original SAS controller and any RAID features;
- what exact problem the customer reported;
- what steps led up to this situation.

the problem is this applies to ALL 4 drives, not only one, which i suspect here

I don't understand what specifically you are referring to when you say "which i suspect here" - what are you suspecting and why?

Good luck!

[einstein9]

Thnx Vulcan for the reply


I meant in windows like DM, or Winhex, or any tool reads as 140gb
and when trying to READ those 140GB, PC hangs with NO BAD SECTORS reported in events viewer

and suspicion here is that the problem of Size applies to all drives not only 1

[mr_spokk]

Better do a full disc clone of all 4 before going further.

[Vulcan]

@einstein9,

Thanks for that info. As mr_spokk says, cloning would be a good idea - but of course all 300GB needs to be recognised & cloned by whatever cloning tool you use.

Personally I would also need the answers to my other questions which you didn't answer, before I offered any suggestions (as I would need those answers in order to avoid giving bad advice, which is why I asked the questions ). The troubleshooting plan in my head at the moment may be changed, depending on those other answers...

Anyway, good luck with this interesting problem.

[mr_spokk]

As the controller reports right size, and Os +SW don't...I would Image the drives in an "non" Os depended SW...Like mediatoools or similar.

[Vulcan]

Agreed (if the HBA has its BIOS extension enabled)

I think there may also be another easy option, but I'm waiting on answers to the earlier troubleshooting questions, so hopefully I avoid making bad suggestions...

[guru]

What model of SAS are these?

[einstein9]

@ guru, Model: ST9300605SS

@ Vulcan, Raid5, client reported 3 hdd`s in server LED Blinks (reports errors)

@ Spildit & mr_spokk any access to hdd will hang the PC, booting is FINE into windows

as an update to this case, I managed to clone 1 (took full day - more or less) COMPLETE IMAGE...

thank you

[guru]

If you got min>maxlba no problem

[mr_spokk]

I managed to clone 1 (took full day - more or less) COMPLETE IMAGE...

thank you

How and what did you use to clone the drives?

[pcimage]

I managed to clone 1 (took full day - more or less) COMPLETE IMAGE...

thank you

How and what did you use to clone the drives?

It shouldn't take that long to clone just one drive.

Probably not if it was a healthy drive, but chances are that it wasn't healthy, given that it is in for recovery.

[mr_spokk]

Probably not if it was a healthy drive, but chances are that it wasn't healthy, given that it is in for recovery.

[einstein9]

Problem Solved.....
Case closed...

happy ending..

[drc]

happy ending..

Do you charge extra for that?

[pcimage]

happy ending..

Do you charge extra for that?

Haha

All the "extras" !!

[einstein9]

hehehe

Well i like it when you face a problem for the 1st. time and you are able to find the solution for it in a short time
paying our school fee`s