Incorrect disk in logical unit, using v4.20 PRO

Post here if you encounter any problems or bugs with the software.
chma
Posts: 4
Joined: 2013.01.26. 12:34

Incorrect disk in logical unit, using v4.20 PRO

Post by chma »

I have LSI 3ware 9650SE SATA RAID Controller with two RAID1 volumes, disks 0 and 3 are in one volume (C) and disks 1 and 2 in another (D). But HD Sentinel reports that all disks are in the same volume, which is wrong. Here is end of http://localhost:61220/report

Partitionsinformation
Logisk Enhet Totalt utrymme Fritt utrymme Fritt utrymme % Använt utrymme
C: cR1-120G 111,7 GB 69,3 GB 62 %
D: zR1-500G (Disk: #0-1-2-3) 465,6 GB 438,6 GB 94 %

Windows Volume/RAID Information
Volymnr Enh Etikett Fils. Typ Storlek Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volymnr 0 E DVD-ROM 0 B Inget med
Volymnr 1 D zR1-500G NTFS Partition 465 G Felfri System
Volymnr 2 C cR1-120G NTFS Partition 111 G Felfri Systemst

And the Status page shows (all on D:):
Disk: #0 xxx D:
Disk: #1 yyy D:
Disk: #2 yyy D:
Disk: #3 xxx D:
User avatar
hdsentinel
Site Admin
Posts: 3010
Joined: 2008.07.27. 17:00
Location: Hungary
Contact:

Re: Incorrect disk in logical unit, using v4.20 PRO

Post by hdsentinel »

Yes, I completely understand the issue with the logical drives, this is known.

This is not really a bug in Hard Disk Sentinel but it is a limitation of the RAID controller - in the current RAID configuration it is not possible to determine which physical drive(s) are associated with the logical drives. The RAID controller offers no function to determine the RAID configuration and the relation between the physical drive(s) and drives available for the operating system.

This is common for some RAID controllers, for example 3ware and Highpoint. There are no such problems with newer / different models (3ware 9750, Adaptec, LSI, etc..) as with them, Hard Disk Sentinel can detect how the drive(s) are configured to arrays and display the proper relation between the physical drives and the drives assigned by the OS.

We try the best to improve the situation but the highest priority is disk monitoring (temperature, health and complete S.M.A.R.T. statistics).

Currently on 3ware 9650 controllers, 100% correct logical disk information would be displayed if you'd have only one RAID array on the RAID
controller (regardless of the number of disks in the array).

Currently I'd recommend to use the "Comment" field (see the "Click here to add comment") section - which is designed exactly for the purpose to add any comment to help identifying the drive(s) by any tags, for example their logical drives, physical location (eg. bay 1, etc..)

Excuse me for this issue.

Anyway, if you can use Report -> Send test report to developer option, that may help further researching and development for your controller.
chma
Posts: 4
Joined: 2013.01.26. 12:34

Re: Incorrect disk in logical unit, using v4.20 PRO

Post by chma »

OK, thank you. It's not a big issue.
spike6479
Posts: 1
Joined: 2013.03.19. 14:12

Re: Incorrect disk in logical unit, using v4.20 PRO

Post by spike6479 »

I am experiencing a similar issue. Although the controller says it is a RAID controller, I'm using to access drives in a San Digital box as a JBOD. Two drives are listed as the same partition, one is in the Sans Digital box, the other is esata directly to the drive. The esata drive is the one that is wrong. The SMART data is correct for each frive, it's just the partition name that is in error.

-- Physical Disk Information - Disk: #8: ST31000340AS --

Hard Disk Summary
-------------------
Hard Disk Number . . . . . . . . . . . . . . . . : 8
Interface . . . . . . . . . . . . . . . . . . . : HighPoint RAID #8/1 [5]
Disk Controller . . . . . . . . . . . . . . . . : RocketRAID 622 SATA Controller (RAID)
Disk Location . . . . . . . . . . . . . . . . . : Bus Number 0, Target ID 0, LUN 0
Hard Disk Model ID . . . . . . . . . . . . . . . : ST31000340AS
Firmware Revision . . . . . . . . . . . . . . . : SD1A
Hard Disk Serial Number . . . . . . . . . . . . : 5QJ0XGMJ
Total Size . . . . . . . . . . . . . . . . . . . : 953869 MB
Power State . . . . . . . . . . . . . . . . . . : Active
Logical Drive(s) . . . . . . . . . . . . . . . . : R: [Backup-5(SC)]
Current Temperature . . . . . . . . . . . . . . : 40 °C
Power On Time . . . . . . . . . . . . . . . . . : 874 days, 23 hours
Estimated Remaining Lifetime . . . . . . . . . . : 9 days
Health . . . . . . . . . . . . . . . . . . . . . : #------------------- 9 % (Critical)
Performance . . . . . . . . . . . . . . . . . . : #################### 100 % (Excellent)

-- Physical Disk Information - Disk: #9: WDC WD20EARS-00MVWB0 --

Hard Disk Summary
-------------------
Hard Disk Number . . . . . . . . . . . . . . . . : 9
Interface . . . . . . . . . . . . . . . . . . . : HighPoint RAID #8/2 [5]
Disk Controller . . . . . . . . . . . . . . . . : RocketRAID 622 SATA Controller (RAID)
Disk Location . . . . . . . . . . . . . . . . . : Bus Number 0, Target ID 0, LUN 0
Hard Disk Model ID . . . . . . . . . . . . . . . : WDC WD20EARS-00MVWB0
Firmware Revision . . . . . . . . . . . . . . . : 51.0AB51
Hard Disk Serial Number . . . . . . . . . . . . : WD-WCAZAC982583
Total Size . . . . . . . . . . . . . . . . . . . : 1907729 MB
Power State . . . . . . . . . . . . . . . . . . : Active
Logical Drive(s) . . . . . . . . . . . . . . . . : R: [Backup-5(SC)]
Current Temperature . . . . . . . . . . . . . . : 30 °C
Power On Time . . . . . . . . . . . . . . . . . : 269 days, 21 hours
Estimated Remaining Lifetime . . . . . . . . . . : more than 1000 days
Health . . . . . . . . . . . . . . . . . . . . . : #################### 100 % (Excellent)
Performance . . . . . . . . . . . . . . . . . . : #################### 100 % (Excellent)
User avatar
hdsentinel
Site Admin
Posts: 3010
Joined: 2008.07.27. 17:00
Location: Hungary
Contact:

Re: Incorrect disk in logical unit, using v4.20 PRO

Post by hdsentinel »

Yes, it is not surprising.
As described previously, this is related to the hard disk controller - it is not possible to determine which physical hard disk is related to the logical drive (partition) in this configuration.
I can only repeat what I wrote on 26 Jan 2013 (two posts above):

Currently I'd recommend to use the "Comment" field (see the "Click here to add comment") section - which is designed exactly for the purpose to add any comment to help identifying the drive(s) by any tags, for example their logical drives, physical location (eg. bay 1, etc..)

Anyway, if you can use Report -> Send test report to developer option, that may help further researching and development for your controller.
Post Reply