Try straceing fdisk to see what system call fails. My guess is that
there is something wrong with the device node such as it is using the
wrong major dev number, and opens on it fail. Verify the device number
against what sysfs/proc says.
Duane Evenson wrote:
I cannot access the raid device with fdisk: "Unable to read
/dev/mapper/hpt37x_fjfegdadi".
I have two identical hard drives. They have empty partition tables.
# dmraid -r
/dev/hde: hpt37x, "hpt37x_fjfegdadi", stripe, ok, 120064832 sectors,
data@ 0
/dev/hdg: hpt37x, "hpt37x_fjfegdadi", stripe, ok, 120064822 sectors,
data@ 10
# ls -l /dev/mapper/
total 0
crw------- 1 root root 10, 63 Oct 25 11:55 control
# dmraid -ay
ERROR: dos: reading /dev/mapper/hpt37x_fjfegdadi[No such file or directory]
# ls -l /dev/mapper/
total 0
crw------- 1 root root 10, 63 Oct 25 11:55 control
brw-rw---- 1 root disk 253, 0 Oct 26 02:07 hpt37x_fjfegdadi
# fdisk /dev/mapper/hpt37x_fjfegdadi
Unable to read /dev/mapper/hpt37x_fjfegdadi
What's my problem? Why can't I access the raid device?
Just to be thorough I tried this with identical filled partition tables
as well -- no joy.
TIA
Duane
_______________________________________________
Ataraid-list mailing list
Ataraid-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ataraid-list
