So I'm working with the iSCSI Initiator and an EqualLogic SAN. I'm not sure when this might have happened, but it appears that the /dev/sdc device is missing, yet the /dev/sdc1 partition exists AND is mountable. Is there a method to re-create the /dev/sdc device? I cannot dd or fdisk it, obviously, but I can mount the /dev/sdc1 partition and it works just fine. Not having the /dev/sdc is messing up my multipath setup (let alone whatever else might be affected).
scsi3 : SFNet iSCSI driver Vendor: EQLOGIC Model: 100E-00 Rev: 2.3 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sdc: 8417280 512-byte hdwr sectors (4310 MB) SCSI device sdc: drive cache: write through SCSI device sdc: 8417280 512-byte hdwr sectors (4310 MB) SCSI device sdc: drive cache: write through sdc: sdc1 Attached scsi disk sdc at scsi3, channel 0, id 0, lun 0
# ls -l /dev/sdc* brw-rw---- 1 root disk 8, 33 Nov 7 14:45 /dev/sdc1
Thanks, Scott
On Nov 13, 2007 4:11 PM, Scott Moseman scmoseman@gmail.com wrote:
So I'm working with the iSCSI Initiator and an EqualLogic SAN. I'm not sure when this might have happened, but it appears that the /dev/sdc device is missing, yet the /dev/sdc1 partition exists AND is mountable. Is there a method to re-create the /dev/sdc device? I cannot dd or fdisk it, obviously, but I can mount the /dev/sdc1 partition and it works just fine. Not having the /dev/sdc is messing up my multipath setup (let alone whatever else might be affected).
scsi3 : SFNet iSCSI driver Vendor: EQLOGIC Model: 100E-00 Rev: 2.3 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sdc: 8417280 512-byte hdwr sectors (4310 MB) SCSI device sdc: drive cache: write through SCSI device sdc: 8417280 512-byte hdwr sectors (4310 MB) SCSI device sdc: drive cache: write through sdc: sdc1 Attached scsi disk sdc at scsi3, channel 0, id 0, lun 0
# ls -l /dev/sdc* brw-rw---- 1 root disk 8, 33 Nov 7 14:45 /dev/sdc1
Really weird. Anyway you can use mknod to create the missing device. In your case mknod sdc b 8 32 should do the trick.
Regards, Tim
On Nov 13, 2007 9:19 AM, Tim Verhoeven tim.verhoeven.be@gmail.com wrote:
# ls -l /dev/sdc* brw-rw---- 1 root disk 8, 33 Nov 7 14:45 /dev/sdc1
Really weird. Anyway you can use mknod to create the missing device. In your case mknod sdc b 8 32 should do the trick.
Hey Tim,
Running 'mknod sdc b 8 32' worked great. I could fdisk and the data looked good. However, when I rebooted to start from a clean slate, sdc disappeared again. Is there something that must be done to make the 'mknod' change permanent? Or perhaps something else is wiping it away and overriding what I've done?
Thanks, Scott
On Nov 13, 2007 4:47 PM, Scott Moseman scmoseman@gmail.com wrote:
Running 'mknod sdc b 8 32' worked great. I could fdisk and the data looked good. However, when I rebooted to start from a clean slate, sdc disappeared again. Is there something that must be done to make the 'mknod' change permanent? Or perhaps something else is wiping it away and overriding what I've done?
Normally udev dynamically makes the different /dev entries. So either udev is screwing up or the iSCSI driver itself is doing something wrong. What version of CentOS is this and what iSCSI initiator are you using ?
Regards, Tim
On Nov 13, 2007 9:50 AM, Tim Verhoeven tim.verhoeven.be@gmail.com wrote:
Running 'mknod sdc b 8 32' worked great. I could fdisk and the data looked good. However, when I rebooted to start from a clean slate, sdc disappeared again. Is there something that must be done to make the 'mknod' change permanent? Or perhaps something else is wiping it away and overriding what I've done?
Normally udev dynamically makes the different /dev entries. So either udev is screwing up or the iSCSI driver itself is doing something wrong. What version of CentOS is this and what iSCSI initiator are you using ?
CentOS 4.4 and iSCSI 4.0.3.0-5
Thanks, Scott
On Nov 13, 2007 10:49 AM, Scott Moseman scmoseman@gmail.com wrote:
Normally udev dynamically makes the different /dev entries. So either udev is screwing up or the iSCSI driver itself is doing something wrong What version of CentOS is this and what iSCSI initiator are you using ?
CentOS 4.4 and iSCSI 4.0.3.0-5
For the record, /etc/udev/rules.d/20-local.rules had an entry that was causing /dev/sdc to not get created. Issue resolved.
Thanks, Scott
-
Scott Moseman -
Tim Verhoeven