![]() A chkdsk /r should be able to be performed (I literally just went through this procedure 3 days ago). It could indicate a corrupted file system, or bad/missing blocks. I would hate to call the Great SAM wrong here, but from a Windows perspective, if the drive shows as RAW in Disk Management Utility, it does not necessarily mean that the drive has no file system at all. So if your drive is raw (raw here means no filesystem) there is nothing for chkdsk to check. You can't let the network fail, it is like tearing a spinning disk without hot swap out of a server in the middle of an operation.Ĭhkdsk is a filesystem check utility. This is a key reason why iSCSI is not recommended when not absolutely necessary and, as you now know, rock solid network stability is a requirement for SAN. I'm guessing it's the volumes that got corrupt during a transfer when the network went down and that's why I'm trying to run a chkdsk but it says it cannot run it on a RAW drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |