| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 112605 | 2010-09-13 21:48:00 | Server 2003 - No disk error on admin console | Chilling_Silence (9) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1136967 | 2010-10-11 01:46:00 | I'll double-check our SNMP setup, but they were basically all setup identically. No shadow copies either, though I like your train of thinking! :D Just confirmed that yes, it is running on ESX. |
Chilling_Silence (9) | ||
| 1136968 | 2010-10-11 01:55:00 | I'll double-check our SNMP setup, but they were basically all setup identically. No shadow copies either, though I like your train of thinking! :D Just confirmed that yes, it is running on ESX. Is A: shared? |
SolMiester (139) | ||
| 1136969 | 2010-10-11 01:59:00 | I'll double-check our SNMP setup, but they were basically all setup identically. No shadow copies either, though I like your train of thinking! :D Just confirmed that yes, it is running on ESX. Just thought, are you using virtual centre to control the hosts or just the client to each host. I have found that sometimes I have to use the client as VM amendments dont take when using the VC...ie: adding storage or storage controllers. Also...when the floppy was attached, it could well of been to a client floppy rather than the host floppy which could account for the error! |
SolMiester (139) | ||
| 1136970 | 2010-10-11 02:15:00 | Changes are being made from within the VMWare vSphere Client. A: Is not shared. When the floppy was attached, it was to a .img file that I SCP'd across to the VMWare host. Does that help narrow it down at all? |
Chilling_Silence (9) | ||
| 1136971 | 2010-10-11 02:17:00 | Also, indexing service is only running on c:\System Volume Information and c:\inetpub :) |
Chilling_Silence (9) | ||
| 1136972 | 2010-10-11 02:24:00 | Changes are being made from within the VMWare vSphere Client. A: Is not shared. When the floppy was attached, it was to a .img file that I SCP'd across to the VMWare host. Does that help narrow it down at all? More details on this! the floppy was a .img that you SCP to where on the host? , a datastore? What was the image?, an install? Are you not able to re-connect? |
SolMiester (139) | ||
| 1136973 | 2010-10-11 02:40:00 | I used DD on a linux machine to make an empty 1.44MB file. I then mounted it as a loopback device and formatted it with FAT12. That was then SCP'd into a directory on the host where all the other CD Images and Floppy images are stored by default, I can't remember off the top of my head. We could re-connect it, it was temporarily fixed while that was connected, but obviously when we then went to reboot the virtual server it tried to boot off the floppy, so we unmounted the virtual floppy and told VMWare to "deconnect" the drive. Let me know if I can clarify that further :) I'll find where on the host we SCP'd the image to. |
Chilling_Silence (9) | ||
| 1136974 | 2010-10-11 02:51:00 | I used DD on a linux machine to make an empty 1.44MB file. I then mounted it as a loopback device and formatted it with FAT12. That was then SCP'd into a directory on the host where all the other CD Images and Floppy images are stored by default, I can't remember off the top of my head. We could re-connect it, it was temporarily fixed while that was connected, but obviously when we then went to reboot the virtual server it tried to boot off the floppy, so we unmounted the virtual floppy and told VMWare to "deconnect" the drive. Let me know if I can clarify that further :) I'll find where on the host we SCP'd the image to. Well, of course the fix is to remove the floppy from the bootable devices and re-attach the image etc, but that isnt solving the issue. I am curious as to what is trying to access the floppy at the scheduled times....we need a program to monitor disk assess!? We have covered A/V, indexing, shadow copies, defrag, sharing, program install, runonce?, run at startup?....snapshot? (do you use veeam?) or shadow protect? |
SolMiester (139) | ||
| 1136975 | 2010-10-11 03:00:00 | Well, of course the fix is to remove the floppy from the bootable devices and re-attach the image etc, but that isnt solving the issue. Yes, we know this, but like you I'm not keen on applying a bandaid fix, I wanna know the real cause :D curiousity... I am curious as to what is trying to access the floppy at the scheduled times....we need a program to monitor disk assess!? We have covered A/V, indexing, shadow copies, defrag, sharing, program install, runonce?, run at startup?....snapshot? (do you use veeam?) or shadow protect? No, no Veeam, no shadow protect See attached :) Thanks again for your persistent help, it's very much appreciated! |
Chilling_Silence (9) | ||
| 1136976 | 2010-10-11 03:03:00 | Do you have any suggestions on an application that will monitor processes reading / writing to the disk ? | Chilling_Silence (9) | ||
| 1 2 3 4 5 | |||||