On Nov 18, 2013, at 9:21 AM, [email protected] wrote: > Hi > > Having an odd issue with a iscsi volume, following a forced reboot on the > server that uses it. > > Using iscsiadm to login to the target successfully (it has always been > manually attached and mounted for historic reasons). Logs indicate success > and expected device of /dev/sdb created: > > Nov 18 14:27:33 mail kernel: [28459.041132] scsi32 : iSCSI Initiator over > TCP/IP > Nov 18 14:27:34 mail kernel: [28459.841119] scsi 32:0:0:0: Direct-Access > EQLOGIC 100E-00 4.3 PQ: 0 ANSI: 5 > Nov 18 14:27:34 mail kernel: [28459.841362] sd 32:0:0:0: [sdb] 1048596480 > 512-byte hardware sectors (536881 MB) > Nov 18 14:27:34 mail kernel: [28459.842480] sd 32:0:0:0: [sdb] Write Protect > is off > Nov 18 14:27:34 mail kernel: [28459.842490] sd 32:0:0:0: [sdb] Mode Sense: ad > 00 00 00 > Nov 18 14:27:34 mail kernel: [28459.842633] sd 32:0:0:0: [sdb] Write cache: > disabled, read cache: enabled, doesn't support DPO or FUA > Nov 18 14:27:34 mail kernel: [28459.842788] sd 32:0:0:0: [sdb] 1048596480 > 512-byte hardware sectors (536881 MB) > Nov 18 14:27:34 mail kernel: [28459.843620] sd 32:0:0:0: [sdb] Write Protect > is off > Nov 18 14:27:34 mail kernel: [28459.843630] sd 32:0:0:0: [sdb] Mode Sense: ad > 00 00 00 > Nov 18 14:27:34 mail kernel: [28459.843765] sd 32:0:0:0: [sdb] Write cache: > disabled, read cache: enabled, doesn't support DPO or FUA > Nov 18 14:27:34 mail kernel: [28459.843770] sdb: sdb1 > Nov 18 14:27:34 mail kernel: [28459.844284] sd 32:0:0:0: [sdb] Attached SCSI > disk > Nov 18 14:27:34 mail kernel: [28459.844319] sd 32:0:0:0: Attached scsi > generic sg8 type 0 > > Running the usual command to mount it however returns: > > mount: special device /dev/sdb1 does not exist
Is there a /dev/sdb1 node and does iscsiadm -m session -P 3 show that the session is correctly (check that the state in the command output is logged in) relogged into the target for that device? What distro is this with? You might be hitting a issue where udev deletes the node when there is a error on the disk but then does not add the /dev/sdb1 node back when the problem is fixed because it does not know that the disks is back. I have seen this with RHEL. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/groups/opt_out.
