Full Version: cant see hardrive
Well im not that good with computers but a virus got at the hardrive you cant log in even in safemode etc. so I put the disk in start the linux auto option. and guess what. im using raid 0 hardrives 2 of them and it cant see the hardrives. in the hardrive menu theres only the x hardrive which is what ubcd4win is on./ any ideas?
Check in Disk Management to see if the drive/partition on the hard drive is even listed... if it is, your partition is probably corrupted and you would need to address that issue before addressing the infections.
If the drive is not even listed... its probably due to not having the proper hard drive controller in UBCD4Win and the following is the direction to take.
UBCD4Win, arguably,has the most complete set of drivers included with it to help in this type of situation. They were developed by the Driverpacks.net development team which represents the most complete set of drivers available anywhere... but still it is limited to what has already been or can be included so it can't have every single driver since new ones are developed all of the time.
So in situations like this the user needs to add the proper drivers for their system and disable the included drivers so no conflicts will mess you up and overwrite the drivers you supply. We also strongly recommend that the user report the issue in the Driverpacks.net forum so that other users will not have to worry about it later as they develop new driverpacks.
First you must locate the proper drivers for your system or its motherboard. Go to the manufacturers or motherboard's website and download the XP ( or Win2k3 drivers if that is the source files you are building from ) Floppy/F6 drivers. These are the same drivers that a user would use when installing XP ( or Win2k3 ) so should be easy to locate.
Next you need to create a folder for them. In the [UBCD4Win]\drivers folder create a folder named SCSIAdapter and in that folder another for your drivers called MyDriver... the path should be [UBCD4Win]\drivers\SCSIAdapter\MyDriver. Then extract the drivers you downloaded into that folder.
Next in the UBCD4WinBuilder go into the Plugins area and disable the "# DriverPacks.net - MassStorage" plugin so you don't get a conflict with these drivers. Rebuild the project and create a new disk and test.
If the drive is not even listed... its probably due to not having the proper hard drive controller in UBCD4Win and the following is the direction to take.
UBCD4Win, arguably,has the most complete set of drivers included with it to help in this type of situation. They were developed by the Driverpacks.net development team which represents the most complete set of drivers available anywhere... but still it is limited to what has already been or can be included so it can't have every single driver since new ones are developed all of the time.
So in situations like this the user needs to add the proper drivers for their system and disable the included drivers so no conflicts will mess you up and overwrite the drivers you supply. We also strongly recommend that the user report the issue in the Driverpacks.net forum so that other users will not have to worry about it later as they develop new driverpacks.
First you must locate the proper drivers for your system or its motherboard. Go to the manufacturers or motherboard's website and download the XP ( or Win2k3 drivers if that is the source files you are building from ) Floppy/F6 drivers. These are the same drivers that a user would use when installing XP ( or Win2k3 ) so should be easy to locate.
Next you need to create a folder for them. In the [UBCD4Win]\drivers folder create a folder named SCSIAdapter and in that folder another for your drivers called MyDriver... the path should be [UBCD4Win]\drivers\SCSIAdapter\MyDriver. Then extract the drivers you downloaded into that folder.
Next in the UBCD4WinBuilder go into the Plugins area and disable the "# DriverPacks.net - MassStorage" plugin so you don't get a conflict with these drivers. Rebuild the project and create a new disk and test.
QUOTE (rdsok @ May 15 2009, 09:48 PM) 
Check in Disk Management to see if the drive/partition on the hard drive is even listed... if it is, your partition is probably corrupted and you would need to address that issue before addressing the infections.
If the drive is not even listed... its probably due to not having the proper hard drive controller in UBCD4Win and the following is the direction to take.
UBCD4Win, arguably,has the most complete set of drivers included with it to help in this type of situation. They were developed by the Driverpacks.net development team which represents the most complete set of drivers available anywhere... but still it is limited to what has already been or can be included so it can't have every single driver since new ones are developed all of the time.
So in situations like this the user needs to add the proper drivers for their system and disable the included drivers so no conflicts will mess you up and overwrite the drivers you supply. We also strongly recommend that the user report the issue in the Driverpacks.net forum so that other users will not have to worry about it later as they develop new driverpacks.
First you must locate the proper drivers for your system or its motherboard. Go to the manufacturers or motherboard's website and download the XP ( or Win2k3 drivers if that is the source files you are building from ) Floppy/F6 drivers. These are the same drivers that a user would use when installing XP ( or Win2k3 ) so should be easy to locate.
Next you need to create a folder for them. In the [UBCD4Win]\drivers folder create a folder named SCSIAdapter and in that folder another for your drivers called MyDriver... the path should be [UBCD4Win]\drivers\SCSIAdapter\MyDriver. Then extract the drivers you downloaded into that folder.
Next in the UBCD4WinBuilder go into the Plugins area and disable the "# DriverPacks.net - MassStorage" plugin so you don't get a conflict with these drivers. Rebuild the project and create a new disk and test.
If the drive is not even listed... its probably due to not having the proper hard drive controller in UBCD4Win and the following is the direction to take.
UBCD4Win, arguably,has the most complete set of drivers included with it to help in this type of situation. They were developed by the Driverpacks.net development team which represents the most complete set of drivers available anywhere... but still it is limited to what has already been or can be included so it can't have every single driver since new ones are developed all of the time.
So in situations like this the user needs to add the proper drivers for their system and disable the included drivers so no conflicts will mess you up and overwrite the drivers you supply. We also strongly recommend that the user report the issue in the Driverpacks.net forum so that other users will not have to worry about it later as they develop new driverpacks.
First you must locate the proper drivers for your system or its motherboard. Go to the manufacturers or motherboard's website and download the XP ( or Win2k3 drivers if that is the source files you are building from ) Floppy/F6 drivers. These are the same drivers that a user would use when installing XP ( or Win2k3 ) so should be easy to locate.
Next you need to create a folder for them. In the [UBCD4Win]\drivers folder create a folder named SCSIAdapter and in that folder another for your drivers called MyDriver... the path should be [UBCD4Win]\drivers\SCSIAdapter\MyDriver. Then extract the drivers you downloaded into that folder.
Next in the UBCD4WinBuilder go into the Plugins area and disable the "# DriverPacks.net - MassStorage" plugin so you don't get a conflict with these drivers. Rebuild the project and create a new disk and test.
I already said its from a virus and its not corrupted. and i already said that im not good with computers and if i cant login how the heck do i get the info
QUOTE (darkedens @ May 17 2009, 01:12 PM)
I already said its from a virus and its not corrupted. and i already said that im not good with computers and if i cant login how the heck do i get the info
If you aren't good with computers don't you think it is worth your time to try the suggestions you were given to try first before you make further comments?
QUOTE (rdsok @ May 17 2009, 02:45 PM)
If you aren't good with computers don't you think it is worth your time to try the suggestions you were given to try first before you make further comments?
im good with computers just not using a boot disk. and i have done all of those. besides the ones that are obvius that are fine
and sorry if im being rude... im about to lose 8 years of files i need
Which hardware do you use?
Which mass storage controller do you use?
Get driver for your mass storage controller.
Do you have a floppy drive? Load mass storage drivers at F6.
Boot UBCD4Win. Run
Which mass storage controller do you use?
Get driver for your mass storage controller.
Do you have a floppy drive? Load mass storage drivers at F6.
Boot UBCD4Win. Run
CODE
devcon hwids *cc_01* *raid* *scsi*
Post the output.
If you had performed the first steps I mentioned.... the results would tell you what the next steps needed actually are.
When booted into UBCD4Win, if the disk management can see that a hard drive exists but can't mount the partition ( typically C: drive )... then fixing the partition information is the next step. But if you can't see the hard drive at all, then the issue you must address is getting the proper hard drive controller into a new UBCD4Win build so that you can take steps to address whatever the malware may have done.
You didn't say if either situation applied so no one else can make further suggestions if you don't provide the info that you saw. Stating the issue is caused by malware means nothing since the effects of malware could be anything, there is no one effect from getting infected, there are many possible effects.
When booted into UBCD4Win, if the disk management can see that a hard drive exists but can't mount the partition ( typically C: drive )... then fixing the partition information is the next step. But if you can't see the hard drive at all, then the issue you must address is getting the proper hard drive controller into a new UBCD4Win build so that you can take steps to address whatever the malware may have done.
You didn't say if either situation applied so no one else can make further suggestions if you don't provide the info that you saw. Stating the issue is caused by malware means nothing since the effects of malware could be anything, there is no one effect from getting infected, there are many possible effects.
QUOTE (rdsok @ May 17 2009, 03:59 PM)
If you had performed the first steps I mentioned.... the results would tell you what the next steps needed actually are.
When booted into UBCD4Win, if the disk management can see that a hard drive exists but can't mount the partition ( typically C: drive )... then fixing the partition information is the next step. But if you can't see the hard drive at all, then the issue you must address is getting the proper hard drive controller into a new UBCD4Win build so that you can take steps to address whatever the malware may have done.
You didn't say if either situation applied so no one else can make further suggestions if you don't provide the info that you saw. Stating the issue is caused by malware means nothing since the effects of malware could be anything, there is no one effect from getting infected, there are many possible effects.
When booted into UBCD4Win, if the disk management can see that a hard drive exists but can't mount the partition ( typically C: drive )... then fixing the partition information is the next step. But if you can't see the hard drive at all, then the issue you must address is getting the proper hard drive controller into a new UBCD4Win build so that you can take steps to address whatever the malware may have done.
You didn't say if either situation applied so no one else can make further suggestions if you don't provide the info that you saw. Stating the issue is caused by malware means nothing since the effects of malware could be anything, there is no one effect from getting infected, there are many possible effects.
all the malaware did was change the reg files so i cant log in. But thanks ill try it again..... just a little frustrated sorry guys. Im basicly going to take what i need off put them on an old computer and scan them. then wipe the hd with a fresh factory install
After you boot from the UBCD4Win disk you made you can scan the files and/or save whatever you wish to another drive if needed. Remember that if you use USB disks to save the files to, they must be connected before you boot from the UBCD4Win disk you created
QUOTE (rdsok @ May 17 2009, 05:04 PM)
After you boot from the UBCD4Win disk you made you can scan the files and/or save whatever you wish to another drive if needed. Remember that if you use USB disks to save the files to, they must be connected before you boot from the UBCD4Win disk you created
yeah thanks.... i did everything you guys told me... but now when i put the disk in hit f12 and try to boot from cd rom device it says this selected boot device not available hit f1 to retry or f2 for settings.
any ideas... retrying wont work nor will f2
The most common cause is when the user didn't burn the disk as instructed ( see http://www.ubcd4win.com/burn.htm ) and just copied the ISO file to the disk instead.
Other causes are bad disks or drives used to burn with.
Other causes are bad disks or drives used to burn with.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.