Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Messerschmitt

Member
  • Content Count

    356
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Messerschmitt

Contact Methods

  • Website URL
    http://

Profile Information

  • OS
    none specified
  • Country
  1. I used DMDE and I blieve I opened the .dd (I used disk image). I guess the 975mb .dd image doesn't look too good eh? It ran for about half an hour? Before I cancelled it.
  2. Hello all. So I have got my basic computer going. Fresh OS install on my SSD and put in 2 older 3TB reds in Raid, as you probably know reading my other few threads. Somehow I think my SSD failed to boot because either somehow some files were written on my failed HDD when I first installed the OS, or because I used the SSD Tweak forum and things such as Enable Write Caching on SSD and checking Turn off Windows write-cache buffer flushing on the device have corrupted the SSD when my HDD failed and it improperly shut down windows. I don't know. There wasn't really a power loss. Anyway, back to my main quest, trying to get my pictures back. I am using DataRescue DD. Seems like the only option is to create a image? I saved it as the default "image[%Range%].dd and did the whole drive. Now, it seems this will take a LONG time. The timer at the bottom stays at 00:00:00 remaining and the progress bar hasn't moved. But before I let it run over night, I am hoping you can tell me what "Read error at 22bxxxxx: Data error (cyclic redundancy check) means. The address keeps changing as I am guessing those are bad sectors, but I am getting a LOT of them. Like 10-30 every minute. Does this mean I am SOL and it won't work? These errors started popping up from the very beginning and they haven't stopped since I started writing this (just over 10 minutes). Lastly, is it possible that the HDD physically failed? Like mentioned it crashed as I was coping the thousands pictures, it didn't really suffered a physical blow (like drive failing off). Can it have brought down everything? While DataRescue DD is going, I can't hear the HDD keep crunching at the same tempo every few seconds. And it took a while until DataRescue DD loaded up the drives. Also, if the .dd file makes it in the end, what are my options to explore the .dd file and hope I can retrieve my pictures?
  3. Regarding the software (windows) vs hardware RAID, I've read a few articles saying I should really do software if I plan sticking to the same OS (in this case Win 7). If the motherboard fails, I lose my array and my data since only that motherboard has access to the array. With windows, I can read my array in any computer or if I change any component in my computer. So from this perspective I've decided to go with windows RAID. I've done RAID 1 and I have no concern on speed. It's purely to store movies, photos, etc. No application will run from these HDD's as I install those on my SSD where my OS is. So now I was wondering if I did the right thing by using Disk Management in windows to create the array, vs using the Intel Rapid Storage Technology. Seems like the 2 don't communicate between them because now the IRST sees the 2 HDD's individually like there is no array. And when I used IRST before breaking the array and using Disk management, Disk Management saw the 2 HDD's individually as well with no signs that it knew it was part of array.
  4. Any difference and pro and cons which I am using? Updating my Intel Rapid Storage allowed me to see the whole 3TB HDD instead of just 746Gb. Using the Intel Rapid Storage, the drive shows as 1 in Disk Manager as Primary. Using the Disk Manager, the 2 disks show together in red as mirrored volume, but individual if I open Intel Rapid Storage. Or it makes no difference? What about portability? (if I have to take out the 2 HDD and use them on a different Win 7 computer) Thanks
  5. Thank you, yes I'll 100% windows, and I will be running windows 7. My first priority is just the picture files if it's possible to get them individually. Creating an image from my downed HDD is a bonus. This is the second time when copying a few thousand pictures killed HDD's. Only a few months ago, when I tried moving a large amount of files (thousands of pictures), my NAS started spitting out bad sectors on 1 WD red, then on a 2nd, and I had to get them replaced to not lose integrity (RAID 5). Now this WD black fails after trying to copy a few thousand pics. Seems like moving around pictures is a HDD killer. The drives are old and several 10k's hrs (the NAS I think had 25k, this black is probably around there or higher). Will try DataRescueDD. Otherwise I'll try DMDE free if DR DD won't work.
  6. Thanks, will try those programs. Hopefully they are free?
  7. I have an ASUS motherboard Z87-A. I'll have a SSD for drive C and want to setup a RAID made of 2 x 3TB for my drive D storage. Currently I'm planning to just leave my SSD in and install Win 7 first, then add the 2 HDD's and setup the RAID. Is this doable? I remember in the past when if I installed Windows with legacy HDD option in BIOS, I couldn't change it to AHCI (for SATA). Is this similar? Any tutorial that I can follow in order to correctly add a RAID for drive D? And most importantly, can I install Windows on my SSD and add the array later? Can I leave Sata mode into AHCI, then change it to RAID when I add the 2 3TB hdd's? Hoping I can get windows installed today
  8. I will probably end up formating and reinstalling a fresh copy of Win 7 after I browse through the SSD and see if I don't have any files there. What is weird, is that before I was able to start windows with ONLY the SSD and the old HDD disconnected. It gave a few errors probably because the TMP and TEMP folders are missing but it was 99% functional. So something must've gotten corrupted in that huge picture file transfer attempt. I also tried the windows repair from the windows installation disk, but that doesn't seem to be doing anything. With only the SSD it straight up boots into BIOS. With the old HDD attached, it wouldn't even load into safe mode, but as mentioned after a loooong time it finally boots into normal window My biggest concern are the pictures I was trying to transfer. I was retarded enough to delete them from my phone after I transferred them to the old HDD, and then all this fiasco happened when trying to copy them to my NAS. What would be the best way to try to recover them and be able to access the old HDD which now would show up in windows as RAW.
  9. I'm having some big problems with my computer, specifically I believe with my drives. I have a SSD where I have windows installed and an older HDD where I keep my file. Now, I think it's worth mentioning that I did change the environment variables to drive D, as per an older article to save the SSD the reads and writes. https://www.overclock.net/forum/355-ssd/1133897-windows-7-ssd-tweaking-guide.html Anyway, I was copying a huge amount of pictures (a few mb's each) to my old HDD on drive D (about 7000). It was copying until everything crapped out and windows crashed. This is when everything went bad. IF I disconnect drive D (because I think it might have failed since it was old), drive C will NOT boot. My computer will keep booting into BIOS. If I keep drive D, windows WILL boot, but extremely slow, and I can hear my old HDD keep crunching for a 1-2 seconds, then stopping for like 6-7, then again 1-2 seconds, rinse and repeat. Windows will be VERY slow to load (while normally it's super fast since it's on SSD), after windows loads, it always wants to do a CHKDSK on drive D, which will never complete as it hangs, and if I cancel, windows will load in 5-10 minutes. Initially will be a blank screen with only my mouse, but if I click, at some point my desktop will show up. Even so, it's unusable, as nothing will load, and even if I go to "Computer" and click property (wanted to change the environment variables), it will give me a system error. Anyobody have any idea what's happening? I have installed another copy of Win 7 on another HDD. With my SSD connected, I can access it (can see the files). With my older HDD connected, I cannot access it, and the file system appears as RAW in disk management, but still shows up, with the size. The only important files were those pictures I was trying to copy, as I was a retard and did a cut from my phone to the HDD (after which I was going to copy them to my NAS), so now I don't have any of those pictures expect on this old HDD. Thanks.
  10. Awesome, teamviewer is exactly what I was looking for. Extremely easy to use. All I have to tell my parents is to open that program and I can take over for them. Thanks mate! MSFN never disappoints with the knowledge it offers.
  11. Hello everyone and happy new year I have found myself short on time as I should've done this research days ago. I need recommendation for a good software for remote desktop to access the computer remotely. I will be gone for several months and my parents have extremely limited computer knowledge. I'd like to be able to connect in via remote desktop and help them in case they need to print something, sign up for a service, etc. Computer runs Windows 7 x64. Any good recommendations for remote desktop programs, hopefully that are simple to connect and secure? I have my own router at home, a E1000 linksys using DD-WRT so I can do the port forwarding if necessary.
  12. I have my laptop that I had 1 SSD (windows 7) and 1 HDD. I saved my HDD content, then I proceeded to upgrade to Windows 10 to reserve the key. I used the HDD to delete it, and install windows 10 on that while leaving my windows 7 SSD untouched. Once I booted in Windows 10, activated the copy, I went ahead and formated the HDD. But somehow something about Windows 10 boot found it's way on the SSD, since now everytime I start my computer I get the following: Any way to fix this so I can get Windows 7 to startup automatically like before? I'm afraid Windows 10 installed the boot files on my SSD and that messes up the boot process now. If I press F9 it will start Windows 7 without problems, but I don't want to have to keep pressing F9 all the time.
  13. Any way to confirm the key is registered to windows 10? I ended just using a spare hdd and formatting that and installing windows on that. Since I had that there was no reason to screw around with virtual machines Edit: darn apparently I can't register 2 keys on the same computer. Somehow it knew I registered it on that mobo, so the new copy was already activated
  14. So are OEM licences and retail licences the same, as in you can reinstall them on new hardware? Or you mean only retail licences, and OEM it's usually only for the 1 hardware? Unfortunately my motherboard is quite old, 2013, a ASUS Z87-A. I guess I will have to do as you said and try the virtual machine. Now I do have Oracle VM VirtualBox installed, but I have a feeling the VirtualBox is the kind that you can actually boot the entire computer from it? (rather than the VirtualBox that opens an instance in windows and uses emulated hardware)
×
×
  • Create New...