A small server setup by a linux programmer who is no longer available and support is non-existant failed after an automatic update left the machine unreachable from the LAN. Samba crashed and I now have 2 RAID arrays formatted NTFS that have thousands of files. I am going to install Windows 10 Pro on it. Will I be able to recover the data on the two RAID arrays?
My current hard drive is failing and, since I have two brand new identical hard drives lying around, I decided to do a RAID 0 set-up. I went into the BIOS and set SATA 1-4 as RAID and 5-6 as IDE. I left the Raid ROM as Legacy. I then went into the RAID set-up and turned both hdds into a RAID 0. I then inserted my usb stick with Windows 10 and started the installation process. The installer saw the raid without any issues, installed windows, and then rebooted. Unfortunately, it was at this time the error in the title appeared. No matter what I did, it would not stop producing the error. Even attempting to boot to my previous hdd (which was not included in the raid set), would produce the same error. The only way to stop it was to turn off the raid and completely remove all of the raid set partitions. This allowed me to boot into my old drive at least.
Specs: Operating System Windows 10 Pro 64-bit CPU AMD FX-812034 °C Zambezi 32nm Technology RAM 32.0GB Dual-Channel DDR3 @ 2400MHz (11-11-11-28) Motherboard ASUSTeK COMPUTER INC. CROSSHAIR V FORMULA-Z (Socket 942)28 °C Graphics G276HL (1920x1080@60Hz) 2047MB NVIDIA GeForce GTX 750 Ti (EVGA)28 °C
Storage 465GB Seagate ST9500325AS (SATA)26 °C 1397GB Western Digital WDC WD15EARS-00Z5B1 (SATA)33 °C 465GB Seagate ST9500325AS (SATA)24 °C 298GB Seagate ST3320620AS (SATA)32 °C 232GB Maxtor 6L250S0 (SATA)35 °C 7GB Memorex TRAVELDRIVE 005B USB Device (USB) Optical Drives HL-DT-ST BD-RE WH12LS30
I am converting an existing Windows 10 Pro laptop to RAID 0 - and I keep getting to the final boot where it says INACCESSIBLE_BOOT_DEVICE. What am I doing wrong? The laptop has two 1 TB Samsung 850 SSDs that are identical. Laptop is a HP Zbook 17.
Here are my steps:
1. Made a good System Image of C: drive on separate external SSD drive connected by USB. D: drive didn't have anything on it to be saved. 2. Used Win 10 Pro DVD to delete all partitions/format drives. 3. Went into BIOS and changed from AHCI to RAID, and also to turn on ability to do Control-I to get to Intel RST ROM. 4. Rebooted, did Control-I, created a RAID 0 of the two disks. 5. Rebooted, installed Windows 10 fresh. Verified it would reboot on its own. 6. Rebooted, went into Repair on Windows 10 DVD. Selected external SSD image to do image restore from. 7. Rebooted - verified on Control-I that the RAID 0 array is listed as "bootable" 8. Rebooted - get INACCESSIBLE_BOOT_DEVICE.
The place it dies - I see the little Windows 10 blue window, and the spinning circle at the bottom - then I get the blue screen with the message.
My son (26) just returned a long term loan P8B67B Deluxe to me with Linux and Win 7 on it. I upgraded 7 successfully, but after updates installed last night the PC refuses to boot saying "error, no such partition, Entering rescue mode .. grub rescue>" Repeated boot attempts saw it fall into error 53 on the mobo lcd display. Removing one ram stick brought me back to booting to "error, no such partition, Entering rescue mode .. grub rescue>"
Trying to boot just one HDD either gives the above message, or "error, no such device : 521683dd-0417-4a66-b3fb-c6c67b9cc9fo grub rescue>"
I don't need the linux. That was my engineer son. What fixes are there to bring it to Win 10 alone? I don't know the new key or the old 7 key. Should have checked and written it down
how to be able to install both Linux and Windows 10 on my laptop's hard drive?So that when I restart my laptop I will be able to choose from either Windows 10 or Linux?
I did that once with Windows 7, and I remember I had 2 possibilities: Either to be able to choose through a Linux prompt at the startup, or through a Windows prompt. I tried both options. (It was either doing it via a Microsoft boot manager or via Linux boot manager or something like that, I just can't remember)
Edit: I remember there was some sort of Linux boot manager if you install Linux AFTER Windows, and if you then delete Linux completely, you had to repair Windows boot loader (Or it was the other way?i.e installing Windows AFTER Linux and then repairing Windows boot loader?)
Last week i upgraded my laptop from win 8.1 to win 10 pro, previously i was using kali linux and win 8.1 in the same laptop, but after the upgrade my laptop can no longer boot the linux os it keeps on saying os not found every time i try loading it up.. How to fix this without loosing a single data from my drives ...
I'm on a Windows 10 Pro PC accessing a linux server with samba etc installed and working well (visible via Homegroup to both Android and Windows 7 pro). From the Win 10 box, if I type the name of the server in Windows File Explorer, then the shares from the server show up without issue. However, if I go into the Network folder, it does not see the linux servers - even though they are correctly configured for the correct homegroup. My windows 7 machines can see the servers in "network" as can my android devices.
Here's a screenshot. Note, the red arrows show what displays in Network folder (red arrows). If I click on the Server Name (HunterNAS in this case), the server shares are displayed and it shows up in the Network folder (blue arrows). Even after making the successful connection, display of another file explorer window > Network folder displays no linux server shares...
I have a Lenovo Thinkcentre preloaded with Windows 10 Pro. Sometimes when I go to File Explorer and click on Network it shows something called "Ralink Linux Client" connected to my home network. When I select its properties the only information I get is it's MAC address. But the funny thing is when I check my router's list of connected devices the Ralink Linux Client doesn't show up on my router's list even though it shows up on Network on my computer. I am using a Buffalo WHR-300HP router. I also have a Thinkpad notebook computer running Windows 7 Pro on my home network and this phantom device never shows up on Network on the Thinkpad. This Ralink Linux Client comes and goes on my Thinkcentre showing up sometimes but not all the time.
I tried researching this on the Web and apparently others have had this problem too both with Windows 7 and Windows 8. But I am reading conflicting information about what might be going on. One forum poster suggested that this means that the router connected to the network is picking up another router within range. Someone else suggested that this is actually something to do with the local router's internal components.
edit - My Thinkcentre is connected to my router via Ethernet. My Thinkpad is connected wirelessly.
Okay. I have been doing a lot of cloning and migrating an OS before but I haven't done cloning or migrating an OS from dual drives in RAID 0 mode.
It's not my PC. Is it a different approach or is it just like working on a single drive? Can Macrium handle this?
Btw, I know clean install is the best way to go, but I was told by the PC owner that she can't afford to install all her programs back due to time issues, etc.
I have an ssd and I want to get another to configure it in raid zero for faster pc but I have already installed windows 10 on one, is there a way I can configure it in raid zero without having to reinstall windows?
I bought two new SSDs to be used in a RAID 0 configuration with a Dell 9020 under Windows 10.
Before the drives I arrived I configured two old HDDs in RAID 0 and installed Windows 10 as a clean install. This worked perfectly.
Once the new SSDs arrived I configured these in RAID 0 and started a clean install. Windows correctly identified the disk with the correct capacity and the install completed without issue.
When the computer restarts I got a "A disk read error occurred" error.
If I boot from the installation media to a command prompt I can see that the Windows files have been correctly installed to the C drive of the RAID 0 array.
I also tried loading the RAID drive during Windows install but this made no difference, and if it was the driver causing the issue it would not have worked with my old HDDs.
If I open diskpart I see that the drive is not marked as boot, which it is when I check these details on the old HDDs in RAID0.
I currently have Windows 10 installed on a Raid 0 of Two Samsung 840 Evo's. Because of a change in the way I am using the PC I need to disable the raid and leave them as separate drives.
The reason I am concerned is that windows 10 is bound to your Hardware, not you. So for me to reinstall windows after disabling raid would I need a new copy or would just installing windows 10 again work?
Alternately if I was to re-install windows 8.1 on my machine after disabling raid. Would I then be able to do the upgrade again and get windows 10 that way?
So I know very little about raid configurations and how to set them up. I have just finished building my pc and everything is working great, however what about the raid configuration my 500gb ssd and 1 tb hdd have been set up in.
I am therefore wondering a) how to find how my storage has been set up, b) which raid configuration to go for and c) how to set it up.
I was thinking of having the ssd and hdd already installed acting as two different drives. i have put windows 10 and all the programmes on to the ssd and would like the hdd to be seen as if it were a usb stick (I think that is what it is at the moment as under this pc the ssd and hdd show as different drives). Then have those two drives mirrored to a single 2 tb hdd.
I have heard about raid 5 but from what i have read this spreads the data across multiple drives and the drives used have to be the same size and so wont work how I would like them to.
I have 2 ssd drives and one mechanical for back up.
Currently I have windows 10 installed on one SSD and nothing on the second. I have cloned the SSD with OS onto the mechanical and I am trying to boot to it and format both SSD drives so I can pool them into a single storage drive with the new windows 10 utility.
I have changed my boot order in the bios to boot from the mechanical drive but windows will not let me delete/format the SSD that I originally installed the OS onto.
I have Windows 10 Pro installed on an SSD in AHCI mode.
I would like to add a RAID 1 array to this system for storage but I understand some registry tweaks must be made before I can change my BIOS from AHCI to RAID mode or I'll end up hosing Windows.
I've read that the edits for older Windows at [URL] do not apply to Windows 10. know the registry edits that work for Windows 10?
I've rescued an old small server(working with Red Hat enterprise -- but I can't have the OS as it's licensed by the office) from our office --was being chucked out but looks quite good to me.
4 SATA bays populated with 4X 3TB HDD's (the HDD's were mine BTW !!!). I'm thinking of using this as a NAS server - 16 GB RAM and decent Intel CPU (i3 equivalent -- good enough for media server).
The only problem is that it's MBR BIOS and I have two RAID 0 arrays consisting of 2 X 2 3TB HDD's.
Installing Windows though -- No HDD's seen !!! yet there's 12 TB of them in the system.
The RAID is onboard --not a separate RAID controller.
Should I remove the HDD's and send the server on it's original journey to a one way trip to the City's TIP.
(On board VGA good enough also for running a GUI - if I can ever install an OS on it -- preferably W10).
I have a PC with Asus Z97-Pro mb. OS (W10) is on SSD. Two SATA HDD's (each 1 TB) contain dissimilar data. Can I add a third SATA drive (1TB) and create a RAID-1 configuration with only one of the two existing drives? The mb manual says that when SATA ports are set to RAID mode, all SATA ports run at RAID mode together. Does this mean that I cannot do what I am asking?
When I built my PC I only got a 250gb ssd, figuring that it would be enough for the time being. I have been having issues with what to keep and what to get rid of on there.Is there a way to convert my (C drive to raid 0 keeping everything installed or will I have to format and reinstall everything. Also, could I do the same with my 1Tb secondary drive so I won't have to re-download everything as I have a slow internet connection.
So at first, I was trying to resolve an issue with my BD-ROM drive described here: XPS 8700 - BD-ROM (HL-DT-ST DVDRW/BDROM CH20N) Not Recognized Windows 10 - Disk Drives (HDD, CD/DVD, Blu-ray) Forum - Disk Drives - Dell Community
However, when attempting to try different things, I am now in a position where I can no longer boot to Windows 10. More specifically, when I turn on my computer, I get an error saying no bootable drives found and it just lists my SATA 1, 2, 3, etc. drives with an option to restart or go to BIOS setup. In other words, I don't even see Windows anymore existing.
My basic computer specs: Dell XPS 8700 SE Intel Core i7-4700 Windows 10 with 1511 update 2TB hdd with 32GB mSATA SSD cache drive 16GB RAM BD-ROM
I need to get Windows working again, and hopefully, get back my data. Here's what I did to cause the problems:
1) I went to Dell UEFI BIOS setup, and changed the SATA mode from "RAID" to "AHCI". Saved and exited BIOS. 2) After rebooting, Windows failed to load, had a consistent blue screen with the sad smiley face with error "IO1_INITIALIZATION_FAILED", automatic repair also failed. 3) I tried reverting back to "RAID" in SATA mode in BIOS, but it failed to change anything. Windows still wouldn't boot 4) I then entered into the special BIOS menu showing devices which listed my mSATA cache drive and hard drive and RAID settings. Since it showed that the cache drive was "Disabled", I thought I could fix my issues by re-creating the RAID array. 5) I tried to delete the current RAID setup shown in that BIOS menu, then chose the option to recreate the RAID0 array by selecting the option to create a "Striped Disk Array". 6) Once I did the above, Windows itself disappeared, and trying to undo the RAID0 option did not fix anything
So now I am no longer seeing Windows, not sure if my data on the hard drive still exists, and my cache drive (obviously) is not working.
doing a clean reinstall and losing all my previous data in Windows?
I am finding the correct driver for my SATA RAID controller which is operating two mirrored 2TB hard drives. The computer still recognizes the controller being installed at the BIOS level. But currently Windows doesn't see the controller card or hard drives.
Information on the card is; Sil 3124 PCI/PCI-X to 4 port SATA300
System information is: AMD 64x2 Dual Core 5800+ 3.00GHZ with 6GB RAM operating Windows 10 Pro.
I have a PC with Asus P9X79 Deluxe motherboard. It has Intel chipset and Intel BIOS RAID (RSTe) and 6 SATA ports connected to it. The chipset IDE controller lists in Linux as:
Intel Corporation C600/X79 series chipset SATA RAID Controller (rev 06), and the PCI ID is: 0104: 8086:2826 (rev 06).
My RAID configuration is 2xOCZ-VERTEX4 256GB SSD's in RAID0, as boot drive (C: drive), and 2 (quite old) WDC WD2500KS 250GB disks in RAID0 for extra storage (games, movies etc) (J: drive).
So yesterday I decided to upgrade my Windows 7 Ultimate to Windows 10 Pro. All seemingly went well during the upgrade process, and the system booted fine, and most stuff seemed to work as it should. But after a while when I accessed files on the J: drive I started experiencing random (temporary) freezes.
Then after a while it got more serious and the whole system froze, I had to hit the reset button.
So I rebooted and looked in the event log, I get see tons of errors there saying that the disk has a bad sector.
Then I try using the J-drive again, by viewing some videos there, and it works fine, but after a while there are some freezes and then I see in the event log, that the drive was reset. After this it works again for a while but then another of those resets comes, and freezes everything for a short while (like 30 seconds).
But when I try to copy some large files off the J-drive, another reset comes, and then the event log starts showing a lot of the error messages from before, with "the disk has an bad sector". (I will post screenshots of these errors after I reboot back into Windows).
After this I can't access the J-drive at all, and Windows gives me error messages when I try to.
So, I figure that I might have just got unlucky and the old WDC drive actually developed read errors, although it's strange that it happens exactly when I install Windows 10 (these drives are something like 7 years old).
Well I can't copy the contents off the disk from Windows since it keeps failing as described above, so I boot into Ubuntu Linux from a USB stick, so I can use ntfsclone to image the J-drive to another disk. I start it running expecting that I'll start seeing read errors, but to my surprise there are NONE. It also copies all files off the J-drive without any problems from inside Linux!
So it was after all not the old drive that had failed, but instead Windows 10/Intel had failed me in a big way.
I trawled the web for updated Intel chipset drivers and installed those from the Asus site, but it made no difference at all. I couldn't find any other Intel drivers and when I searched for the RST drivers on Intel's own site, I could only find ones for Windows XP upto Windows 8.1, but none for Windows 10.
For now I'm left with a PC that I can't use, because I can't go back to Windows 7 and Windows 10 is not working with my RAID arrays. I got some spare 2TB disks, and I'm right now copying all the data from the old J-drive (the RAID1 about 500GB) over to this, hopefully I can then work in Win 10, but I am VERY concerned because the same RAID and drivers are used for my master boot drive with the two OCZ SSD's.
Ok recently my pc has been crashing like crazy and I got tired of it so I decided to reset my pc (I have windows 10) but after I did so it would try to restart and it kept saying it ran into a problem (INACCESSIBLE BOOT DEVICE) and it would reset again and it would keep doing that in an endless loop.
So I figured all the crashing before was because of motherboard. Gigabyte ATX Socket AM3+ AMD 970 Chipset. So I recently bought a new motherboard.A MSI 970 Gaming mother board. But its still keeps showing the screen that keeps saying it ran into a problem (INACCESSIBLE BOOT DEVICE) in a endless loop. Does this mean I need a brand new clean hard drive that doesn’t have windows installed on it so it can act like a brand new computer or what?
so I went from windows 7 to windows 10 reason behind it was because being new.. I thought I would reset everything as it was going slow and now it is just showing the
inaccessible boot device
I am trying to change the settings on the esc start up but it's not showing things I can change?