Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > aus.computers > #56471 > unrolled thread
| Started by | felix <me@nothere.invalid> |
|---|---|
| First post | 2016-12-21 18:20 +1100 |
| Last post | 2016-12-30 15:40 +1100 |
| Articles | 20 on this page of 89 — 13 participants |
Back to article view | Back to aus.computers
Windose 10 felix <me@nothere.invalid> - 2016-12-21 18:20 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-21 18:36 +1100
Re: Windose 10 jonz <johnhhhinton7@gmail.com> - 2016-12-21 03:13 -0800
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-22 05:59 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 06:49 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 07:50 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 08:16 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 08:32 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 09:46 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 10:04 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 11:48 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-22 07:33 +1000
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 08:41 +1100
Re: Windose 10 Frank Slootweg <this@ddress.is.invalid> - 2016-12-22 16:08 +0000
Re: Windose 10 Jeßus <j@j.net> - 2016-12-23 06:09 +1100
Re: Windose 10 Lucifer Morningstar <Barry@saymyname.com> - 2016-12-24 07:54 +1100
Re: Windose 10 "John" <dj34d@gmail.com> - 2016-12-22 11:34 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-21 22:30 +1100
Re: Windose 10 not@telling.you.invalid (Computer Nerd Kev) - 2016-12-21 21:46 +0000
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 09:48 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-22 10:06 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-22 11:49 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-22 15:13 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-22 14:42 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-22 15:12 +1100
Re: Windose 10 Jeßus <j@j.net> - 2016-12-21 22:06 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-22 15:08 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-22 14:44 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-22 21:05 +1100
Re: Windose 10 Frank Slootweg <this@ddress.is.invalid> - 2016-12-22 16:21 +0000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-23 17:47 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-23 10:52 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-23 17:49 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-23 17:57 +1100
Re: Windose 10 Lucifer Morningstar <Barry@saymyname.com> - 2016-12-23 19:11 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:29 +1100
Re: Windose 10 not@telling.you.invalid (Computer Nerd Kev) - 2016-12-23 11:28 +0000
Re: Windose 10 Jeßus <j@j.net> - 2016-12-24 05:46 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-24 07:19 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:47 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:46 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:50 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-25 07:34 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-24 20:59 +1100
Re: Windose 10 Grumpy Tech <grumpytech07@gmail.com> - 2016-12-24 21:09 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-25 00:06 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-25 16:57 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-25 17:49 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 00:26 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 08:21 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-26 09:36 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 11:16 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 11:27 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 11:43 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 11:50 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-26 12:36 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-26 12:57 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-26 12:02 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-26 12:51 +1100
Re: Windose 10 "SG1" <lost@the.races.com> - 2016-12-26 11:52 +1000
Re: Windose 10 Lucifer Morningstar <Barry@saymyname.com> - 2016-12-27 18:26 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-25 09:30 +1100
Re: Windose 10 keithr0 <user@account.invalid> - 2016-12-22 21:30 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-23 00:07 +1100
Re: Windose 10 Petzl <petzlx@gmail.com> - 2016-12-23 09:13 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-28 20:35 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-29 04:52 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 21:15 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 22:27 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 22:34 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 22:53 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-29 23:41 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 05:54 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 11:01 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 11:04 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 13:27 +1100
Re: Windose 10 keithr0 <user@account.invalid> - 2016-12-30 16:08 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 17:32 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-30 19:26 +1100
Re: Windose 10 keithr0 <user@account.invalid> - 2016-12-30 23:54 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 17:35 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 21:09 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 21:07 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 05:53 +1100
Re: Windose 10 "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-12-30 05:52 +1100
Re: Windose 10 Jeßus <j@j.org> - 2016-12-30 11:43 +1100
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 13:25 +1100
Re: Windose 10 Grumpy Tech <grumpytech07@gmail.com> - 2016-12-30 14:15 +1000
Re: Windose 10 felix <me@nothere.invalid> - 2016-12-30 15:40 +1100
Page 3 of 5 — ← Prev page 1 2 [3] 4 5 Next page →
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-24 20:46 +1100 |
| Message-ID | <ec6ug3Fmgu3U1@mid.individual.net> |
| In reply to | #56568 |
On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: > felix <me@nothere.invalid> wrote: >> I've now determined that the problem is that the none of the SATA ports >> are working. the hard drive is not being seen and not showing up in the >> bios. so I assume that can only mean the SATA ports are cactus, as the >> drive has power. > Ok it has power, but have you tried it in another PC to see whether the > control electronics have thrown in the towl? yes, I put it in a usb box on the main PC and I can read the drive no prob > > Any chance that the BIOS settings have got scrambled due to some > glitch or a failing backup battery and the SATA controller's simply > disabled? > no, I had checked the bios -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-24 20:50 +1100 |
| Message-ID | <ec6unvFmgu3U3@mid.individual.net> |
| In reply to | #56568 |
On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: > felix <me@nothere.invalid> wrote: >> I've now determined that the problem is that the none of the SATA ports >> are working. the hard drive is not being seen and not showing up in the >> bios. so I assume that can only mean the SATA ports are cactus, as the >> drive has power. > Ok it has power, but have you tried it in another PC to see whether the > control electronics have thrown in the towl? > > Any chance that the BIOS settings have got scrambled due to some > glitch or a failing backup battery and the SATA controller's simply > disabled? > is it usual for ALL SATA ports to fail? there are eight -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Date | 2016-12-25 07:34 +1100 |
| Message-ID | <ec84rnFv75U2@mid.individual.net> |
| In reply to | #56623 |
"felix" <me@nothere.invalid> wrote in message news:ec6unvFmgu3U3@mid.individual.net... > On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >> felix <me@nothere.invalid> wrote: >>> I've now determined that the problem is that the none of the SATA ports >>> are working. the hard drive is not being seen and not showing up in the >>> bios. so I assume that can only mean the SATA ports are cactus, as the >>> drive has power. >> Ok it has power, but have you tried it in another PC to see whether the >> control electronics have thrown in the towl? >> >> Any chance that the BIOS settings have got scrambled due to some >> glitch or a failing backup battery and the SATA controller's simply >> disabled? > is it usual for ALL SATA ports to fail? That can happen when the chip that provides them dies. Uncommon tho. > there are eight Usually 8 is done with two separate chips. Yours has 6 done by one chip and 2 done by the other. http://www.asrock.com/mb/AMD/980DE3U3S3/?cat=Specifications Very unlikely they have all died at that same time.
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-24 20:59 +1100 |
| Message-ID | <ec6v8lFmmg7U1@mid.individual.net> |
| In reply to | #56568 |
On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: > felix <me@nothere.invalid> wrote: >> I've now determined that the problem is that the none of the SATA ports >> are working. the hard drive is not being seen and not showing up in the >> bios. so I assume that can only mean the SATA ports are cactus, as the >> drive has power. > Ok it has power, but have you tried it in another PC to see whether the > control electronics have thrown in the towl? > > Any chance that the BIOS settings have got scrambled due to some > glitch or a failing backup battery and the SATA controller's simply > disabled? > it's showing up in the 'boot' section of the bios, and at startup on the blank black screen, but it's not showing as detected on the sata port in bios -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | Grumpy Tech <grumpytech07@gmail.com> |
|---|---|
| Date | 2016-12-24 21:09 +1000 |
| Message-ID | <o3ll11$1637$1@gioia.aioe.org> |
| In reply to | #56624 |
On 24/12/2016 7:59 PM, felix wrote: > On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >> felix <me@nothere.invalid> wrote: >>> I've now determined that the problem is that the none of the SATA ports >>> are working. the hard drive is not being seen and not showing up in the >>> bios. so I assume that can only mean the SATA ports are cactus, as the >>> drive has power. >> Ok it has power, but have you tried it in another PC to see whether the >> control electronics have thrown in the towl? >> >> Any chance that the BIOS settings have got scrambled due to some >> glitch or a failing backup battery and the SATA controller's simply >> disabled? >> > > it's showing up in the 'boot' section of the bios, and at startup on the > blank black screen, but it's not showing as detected on the sata port in > bios > That's probably because your Bios is in AHCI mode which won't show drives there. Change the Bios to legacy mode and see if you can get it to boot (Needs to be under 2tb). It's not a faulty MB. It sounds like the standard windows boot sector issue, which could indicate a drive that has a failed boot sector or the bcd file has been corrupted. Put it in your other machine on another sata port and run from an admin dos prompt chkdsk x: /r where x: is the drive letter given to the drive by your machine. It may resolve the issue. You could also try this Open Command Prompt from Advanced Startup Options or System Recovery Options menu. Note: The Command Prompt available from these diagnostic menus is very similar to the one you may be familiar with within Windows. ... At the prompt, type the bootrec command as shown below and then press Enter: bootrec /rebuildbcd.
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-25 00:06 +1100 |
| Message-ID | <ec7a79Fp8raU1@mid.individual.net> |
| In reply to | #56630 |
On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: > On 24/12/2016 7:59 PM, felix wrote: >> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>> felix <me@nothere.invalid> wrote: >>>> I've now determined that the problem is that the none of the SATA >>>> ports >>>> are working. the hard drive is not being seen and not showing up in >>>> the >>>> bios. so I assume that can only mean the SATA ports are cactus, as the >>>> drive has power. >>> Ok it has power, but have you tried it in another PC to see whether the >>> control electronics have thrown in the towl? >>> >>> Any chance that the BIOS settings have got scrambled due to some >>> glitch or a failing backup battery and the SATA controller's simply >>> disabled? >>> >> >> it's showing up in the 'boot' section of the bios, and at startup on the >> blank black screen, but it's not showing as detected on the sata port in >> bios >> > That's probably because your Bios is in AHCI mode it is > which won't show drives there. Change the Bios to legacy mode and see > if you can get it to boot still won't boot and still doesn't show on the sata port > (Needs to be under 2tb). 1Tb > It's not a faulty MB. It sounds like the standard windows boot sector > issue, which could indicate a drive that has a failed boot sector or > the bcd file has been corrupted. Put it in your other machine on > another sata port and run from an admin dos prompt chkdsk x: /r where > x: is the drive letter given to the drive by your machine. It may > resolve the issue. > > You could also try this > > Open Command Prompt from Advanced Startup Options or System Recovery > Options menu. Note: The Command Prompt available from these diagnostic > menus is very similar to the one you may be familiar with within > Windows. ... > At the prompt, type the bootrec command as shown below and then press > Enter: bootrec /rebuildbcd. > > Ok, thanks I'll try those after Xmas. see, you are good for something after all.. :) -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-25 16:57 +1100 |
| Message-ID | <ec95dpF7tbiU1@mid.individual.net> |
| In reply to | #56637 |
On Sunday, 25 Dec 2016 12:06 AM, felix wrote: > On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >> On 24/12/2016 7:59 PM, felix wrote: >>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>> felix <me@nothere.invalid> wrote: >>>>> I've now determined that the problem is that the none of the SATA >>>>> ports >>>>> are working. the hard drive is not being seen and not showing up >>>>> in the >>>>> bios. so I assume that can only mean the SATA ports are cactus, as >>>>> the >>>>> drive has power. >>>> Ok it has power, but have you tried it in another PC to see whether >>>> the >>>> control electronics have thrown in the towl? >>>> >>>> Any chance that the BIOS settings have got scrambled due to some >>>> glitch or a failing backup battery and the SATA controller's simply >>>> disabled? >>>> >>> >>> it's showing up in the 'boot' section of the bios, and at startup on >>> the >>> blank black screen, but it's not showing as detected on the sata >>> port in >>> bios >>> >> That's probably because your Bios is in AHCI mode > > it is > >> which won't show drives there. Change the Bios to legacy mode and see >> if you can get it to boot > > still won't boot and still doesn't show on the sata port > >> (Needs to be under 2tb). > > 1Tb > >> It's not a faulty MB. It sounds like the standard windows boot sector >> issue, which could indicate a drive that has a failed boot sector or >> the bcd file has been corrupted. Put it in your other machine on >> another sata port and run from an admin dos prompt chkdsk x: /r where >> x: is the drive letter given to the drive by your machine. It may >> resolve the issue. >> >> You could also try this >> >> Open Command Prompt from Advanced Startup Options or System Recovery >> Options menu. Note: The Command Prompt available from these >> diagnostic menus is very similar to the one you may be familiar with >> within Windows. ... >> At the prompt, type the bootrec command as shown below and then press >> Enter: bootrec /rebuildbcd. >> >> > > Ok, thanks I'll try those after Xmas. see, you are good for something > after all.. :) > > couldn't wait. I tried it last night. no different. btw.. the win10 message I get is 'inaccessible boot device' which still seems to indicate a hardware problem -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Date | 2016-12-25 17:49 +1100 |
| Message-ID | <ec98f2F8hjuU1@mid.individual.net> |
| In reply to | #56660 |
"felix" <me@nothere.invalid> wrote in message news:ec95dpF7tbiU1@mid.individual.net... > On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>> On 24/12/2016 7:59 PM, felix wrote: >>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>> felix <me@nothere.invalid> wrote: >>>>>> I've now determined that the problem is that the none of the SATA >>>>>> ports >>>>>> are working. the hard drive is not being seen and not showing up in >>>>>> the >>>>>> bios. so I assume that can only mean the SATA ports are cactus, as >>>>>> the >>>>>> drive has power. >>>>> Ok it has power, but have you tried it in another PC to see whether >>>>> the >>>>> control electronics have thrown in the towl? >>>>> >>>>> Any chance that the BIOS settings have got scrambled due to some >>>>> glitch or a failing backup battery and the SATA controller's simply >>>>> disabled? >>>>> >>>> >>>> it's showing up in the 'boot' section of the bios, and at startup on >>>> the >>>> blank black screen, but it's not showing as detected on the sata port >>>> in >>>> bios >>>> >>> That's probably because your Bios is in AHCI mode >> >> it is >> >>> which won't show drives there. Change the Bios to legacy mode and see if >>> you can get it to boot >> >> still won't boot and still doesn't show on the sata port >> >>> (Needs to be under 2tb). >> >> 1Tb >> >>> It's not a faulty MB. It sounds like the standard windows boot sector >>> issue, which could indicate a drive that has a failed boot sector or the >>> bcd file has been corrupted. Put it in your other machine on another >>> sata port and run from an admin dos prompt chkdsk x: /r where x: is the >>> drive letter given to the drive by your machine. It may resolve the >>> issue. >>> >>> You could also try this >>> >>> Open Command Prompt from Advanced Startup Options or System Recovery >>> Options menu. Note: The Command Prompt available from these diagnostic >>> menus is very similar to the one you may be familiar with within >>> Windows. ... >>> At the prompt, type the bootrec command as shown below and then press >>> Enter: bootrec /rebuildbcd. >>> >>> >> >> Ok, thanks I'll try those after Xmas. see, you are good for something >> after all.. :) >> >> > > couldn't wait. I tried it last night. no different. btw.. the win10 > message I get is 'inaccessible boot device' which still seems to indicate > a hardware problem That's just saying it can't see a boot drive. I'd reset the cmos and see if the SATA ports work again. Very unlikely to be a hardware failure with all 8 sata ports going missing given that 6 of them are on 1 chip and the other two are on a different one. Nothing much shows up with google and that motherboard, ask the manufacturer about it.
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-26 00:26 +1100 |
| Message-ID | <ec9vo5FdnvkU1@mid.individual.net> |
| In reply to | #56661 |
On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: > > > "felix" <me@nothere.invalid> wrote in message > news:ec95dpF7tbiU1@mid.individual.net... >> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>> On 24/12/2016 7:59 PM, felix wrote: >>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>> felix <me@nothere.invalid> wrote: >>>>>>> I've now determined that the problem is that the none of the >>>>>>> SATA ports >>>>>>> are working. the hard drive is not being seen and not showing up >>>>>>> in the >>>>>>> bios. so I assume that can only mean the SATA ports are cactus, >>>>>>> as the >>>>>>> drive has power. >>>>>> Ok it has power, but have you tried it in another PC to see >>>>>> whether the >>>>>> control electronics have thrown in the towl? >>>>>> >>>>>> Any chance that the BIOS settings have got scrambled due to some >>>>>> glitch or a failing backup battery and the SATA controller's simply >>>>>> disabled? >>>>>> >>>>> >>>>> it's showing up in the 'boot' section of the bios, and at startup >>>>> on the >>>>> blank black screen, but it's not showing as detected on the sata >>>>> port in >>>>> bios >>>>> >>>> That's probably because your Bios is in AHCI mode >>> >>> it is >>> >>>> which won't show drives there. Change the Bios to legacy mode and >>>> see if you can get it to boot >>> >>> still won't boot and still doesn't show on the sata port >>> >>>> (Needs to be under 2tb). >>> >>> 1Tb >>> >>>> It's not a faulty MB. It sounds like the standard windows boot >>>> sector issue, which could indicate a drive that has a failed boot >>>> sector or the bcd file has been corrupted. Put it in your other >>>> machine on another sata port and run from an admin dos prompt >>>> chkdsk x: /r where x: is the drive letter given to the drive by >>>> your machine. It may resolve the issue. >>>> >>>> You could also try this >>>> >>>> Open Command Prompt from Advanced Startup Options or System >>>> Recovery Options menu. Note: The Command Prompt available from >>>> these diagnostic menus is very similar to the one you may be >>>> familiar with within Windows. ... >>>> At the prompt, type the bootrec command as shown below and then >>>> press Enter: bootrec /rebuildbcd. >>>> >>>> >>> >>> Ok, thanks I'll try those after Xmas. see, you are good for >>> something after all.. :) >>> >>> >> >> couldn't wait. I tried it last night. no different. btw.. the win10 >> message I get is 'inaccessible boot device' which still seems to >> indicate a hardware problem > > That's just saying it can't see a boot drive. > > I'd reset the cmos and see if the SATA ports work again. ok I'll give that a try tomorrow, thanks > > Very unlikely to be a hardware failure with all 8 sata ports > going missing given that 6 of them are on 1 chip and the > other two are on a different one. makes sense > > Nothing much shows up with google and that > motherboard, ask the manufacturer about it. -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-26 08:21 +1100 |
| Message-ID | <ecarj3Fk6d5U1@mid.individual.net> |
| In reply to | #56674 |
On Monday, 26 Dec 2016 12:26 AM, felix wrote: > On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >> >> >> "felix" <me@nothere.invalid> wrote in message >> news:ec95dpF7tbiU1@mid.individual.net... >>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>> I've now determined that the problem is that the none of the >>>>>>>> SATA ports >>>>>>>> are working. the hard drive is not being seen and not showing >>>>>>>> up in the >>>>>>>> bios. so I assume that can only mean the SATA ports are cactus, >>>>>>>> as the >>>>>>>> drive has power. >>>>>>> Ok it has power, but have you tried it in another PC to see >>>>>>> whether the >>>>>>> control electronics have thrown in the towl? >>>>>>> >>>>>>> Any chance that the BIOS settings have got scrambled due to some >>>>>>> glitch or a failing backup battery and the SATA controller's simply >>>>>>> disabled? >>>>>>> >>>>>> >>>>>> it's showing up in the 'boot' section of the bios, and at startup >>>>>> on the >>>>>> blank black screen, but it's not showing as detected on the sata >>>>>> port in >>>>>> bios >>>>>> >>>>> That's probably because your Bios is in AHCI mode >>>> >>>> it is >>>> >>>>> which won't show drives there. Change the Bios to legacy mode and >>>>> see if you can get it to boot >>>> >>>> still won't boot and still doesn't show on the sata port >>>> >>>>> (Needs to be under 2tb). >>>> >>>> 1Tb >>>> >>>>> It's not a faulty MB. It sounds like the standard windows boot >>>>> sector issue, which could indicate a drive that has a failed boot >>>>> sector or the bcd file has been corrupted. Put it in your other >>>>> machine on another sata port and run from an admin dos prompt >>>>> chkdsk x: /r where x: is the drive letter given to the drive by >>>>> your machine. It may resolve the issue. >>>>> >>>>> You could also try this >>>>> >>>>> Open Command Prompt from Advanced Startup Options or System >>>>> Recovery Options menu. Note: The Command Prompt available from >>>>> these diagnostic menus is very similar to the one you may be >>>>> familiar with within Windows. ... >>>>> At the prompt, type the bootrec command as shown below and then >>>>> press Enter: bootrec /rebuildbcd. >>>>> >>>>> >>>> >>>> Ok, thanks I'll try those after Xmas. see, you are good for >>>> something after all.. :) >>>> >>>> >>> >>> couldn't wait. I tried it last night. no different. btw.. the win10 >>> message I get is 'inaccessible boot device' which still seems to >>> indicate a hardware problem >> >> That's just saying it can't see a boot drive. >> >> I'd reset the cmos and see if the SATA ports work again. > > ok I'll give that a try tomorrow, thanks >> >> Very unlikely to be a hardware failure with all 8 sata ports >> going missing given that 6 of them are on 1 chip and the >> other two are on a different one. > > makes sense > >> >> Nothing much shows up with google and that >> motherboard, ask the manufacturer about it. > > I've established the SATA ports are working. I installed Linux on a DVD and booted with a SATA drive connected and I could read the drive and load files. seems it's nothing more than a corrupt win10 64 bit installation -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Date | 2016-12-26 09:36 +1100 |
| Message-ID | <ecavvvFl6iaU2@mid.individual.net> |
| In reply to | #56689 |
"felix" <me@nothere.invalid> wrote in message news:ecarj3Fk6d5U1@mid.individual.net... > On Monday, 26 Dec 2016 12:26 AM, felix wrote: >> On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >>> >>> >>> "felix" <me@nothere.invalid> wrote in message >>> news:ec95dpF7tbiU1@mid.individual.net... >>>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>>> I've now determined that the problem is that the none of the SATA >>>>>>>>> ports >>>>>>>>> are working. the hard drive is not being seen and not showing up >>>>>>>>> in the >>>>>>>>> bios. so I assume that can only mean the SATA ports are cactus, as >>>>>>>>> the >>>>>>>>> drive has power. >>>>>>>> Ok it has power, but have you tried it in another PC to see whether >>>>>>>> the >>>>>>>> control electronics have thrown in the towl? >>>>>>>> >>>>>>>> Any chance that the BIOS settings have got scrambled due to some >>>>>>>> glitch or a failing backup battery and the SATA controller's simply >>>>>>>> disabled? >>>>>>>> >>>>>>> >>>>>>> it's showing up in the 'boot' section of the bios, and at startup on >>>>>>> the >>>>>>> blank black screen, but it's not showing as detected on the sata >>>>>>> port in >>>>>>> bios >>>>>>> >>>>>> That's probably because your Bios is in AHCI mode >>>>> >>>>> it is >>>>> >>>>>> which won't show drives there. Change the Bios to legacy mode and see >>>>>> if you can get it to boot >>>>> >>>>> still won't boot and still doesn't show on the sata port >>>>> >>>>>> (Needs to be under 2tb). >>>>> >>>>> 1Tb >>>>> >>>>>> It's not a faulty MB. It sounds like the standard windows boot sector >>>>>> issue, which could indicate a drive that has a failed boot sector or >>>>>> the bcd file has been corrupted. Put it in your other machine on >>>>>> another sata port and run from an admin dos prompt chkdsk x: /r where >>>>>> x: is the drive letter given to the drive by your machine. It may >>>>>> resolve the issue. >>>>>> >>>>>> You could also try this >>>>>> >>>>>> Open Command Prompt from Advanced Startup Options or System Recovery >>>>>> Options menu. Note: The Command Prompt available from these >>>>>> diagnostic menus is very similar to the one you may be familiar with >>>>>> within Windows. ... >>>>>> At the prompt, type the bootrec command as shown below and then press >>>>>> Enter: bootrec /rebuildbcd. >>>>>> >>>>>> >>>>> >>>>> Ok, thanks I'll try those after Xmas. see, you are good for something >>>>> after all.. :) >>>>> >>>>> >>>> >>>> couldn't wait. I tried it last night. no different. btw.. the win10 >>>> message I get is 'inaccessible boot device' which still seems to >>>> indicate a hardware problem >>> >>> That's just saying it can't see a boot drive. >>> >>> I'd reset the cmos and see if the SATA ports work again. >> >> ok I'll give that a try tomorrow, thanks >>> >>> Very unlikely to be a hardware failure with all 8 sata ports >>> going missing given that 6 of them are on 1 chip and the >>> other two are on a different one. >> >> makes sense >> >>> >>> Nothing much shows up with google and that >>> motherboard, ask the manufacturer about it. >> >> > > I've established the SATA ports are working. I installed Linux on a DVD > and booted with a SATA drive connected and I could read the drive and load > files. seems it's nothing more than a corrupt win10 64 bit installation Yeah, looks like it. And if you had made the recovery disk when it was still working, it may have been able to recover it.
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-26 11:16 +1100 |
| Message-ID | <ecb5qgFmgatU1@mid.individual.net> |
| In reply to | #56696 |
On Monday, 26 Dec 2016 9:36 AM, Rod Speed wrote: > > > "felix" <me@nothere.invalid> wrote in message > news:ecarj3Fk6d5U1@mid.individual.net... >> On Monday, 26 Dec 2016 12:26 AM, felix wrote: >>> On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >>>> >>>> >>>> "felix" <me@nothere.invalid> wrote in message >>>> news:ec95dpF7tbiU1@mid.individual.net... >>>>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>>>> I've now determined that the problem is that the none of the >>>>>>>>>> SATA ports >>>>>>>>>> are working. the hard drive is not being seen and not showing >>>>>>>>>> up in the >>>>>>>>>> bios. so I assume that can only mean the SATA ports are >>>>>>>>>> cactus, as the >>>>>>>>>> drive has power. >>>>>>>>> Ok it has power, but have you tried it in another PC to see >>>>>>>>> whether the >>>>>>>>> control electronics have thrown in the towl? >>>>>>>>> >>>>>>>>> Any chance that the BIOS settings have got scrambled due to some >>>>>>>>> glitch or a failing backup battery and the SATA controller's >>>>>>>>> simply >>>>>>>>> disabled? >>>>>>>>> >>>>>>>> >>>>>>>> it's showing up in the 'boot' section of the bios, and at >>>>>>>> startup on the >>>>>>>> blank black screen, but it's not showing as detected on the >>>>>>>> sata port in >>>>>>>> bios >>>>>>>> >>>>>>> That's probably because your Bios is in AHCI mode >>>>>> >>>>>> it is >>>>>> >>>>>>> which won't show drives there. Change the Bios to legacy mode >>>>>>> and see if you can get it to boot >>>>>> >>>>>> still won't boot and still doesn't show on the sata port >>>>>> >>>>>>> (Needs to be under 2tb). >>>>>> >>>>>> 1Tb >>>>>> >>>>>>> It's not a faulty MB. It sounds like the standard windows boot >>>>>>> sector issue, which could indicate a drive that has a failed >>>>>>> boot sector or the bcd file has been corrupted. Put it in your >>>>>>> other machine on another sata port and run from an admin dos >>>>>>> prompt chkdsk x: /r where x: is the drive letter given to the >>>>>>> drive by your machine. It may resolve the issue. >>>>>>> >>>>>>> You could also try this >>>>>>> >>>>>>> Open Command Prompt from Advanced Startup Options or System >>>>>>> Recovery Options menu. Note: The Command Prompt available from >>>>>>> these diagnostic menus is very similar to the one you may be >>>>>>> familiar with within Windows. ... >>>>>>> At the prompt, type the bootrec command as shown below and then >>>>>>> press Enter: bootrec /rebuildbcd. >>>>>>> >>>>>>> >>>>>> >>>>>> Ok, thanks I'll try those after Xmas. see, you are good for >>>>>> something after all.. :) >>>>>> >>>>>> >>>>> >>>>> couldn't wait. I tried it last night. no different. btw.. the >>>>> win10 message I get is 'inaccessible boot device' which still >>>>> seems to indicate a hardware problem >>>> >>>> That's just saying it can't see a boot drive. >>>> >>>> I'd reset the cmos and see if the SATA ports work again. >>> >>> ok I'll give that a try tomorrow, thanks >>>> >>>> Very unlikely to be a hardware failure with all 8 sata ports >>>> going missing given that 6 of them are on 1 chip and the >>>> other two are on a different one. >>> >>> makes sense >>> >>>> >>>> Nothing much shows up with google and that >>>> motherboard, ask the manufacturer about it. >>> >>> >> >> I've established the SATA ports are working. I installed Linux on a >> DVD and booted with a SATA drive connected and I could read the drive >> and load files. seems it's nothing more than a corrupt win10 64 bit >> installation > > Yeah, looks like it. And if you had made the recovery disk > when it was still working, it may have been able to recover it. I'll certainly make one when it's up and running again. or maybe there is some third party recovery software I could use? or does M$ have any 'after the event' repair program that can be put on disc? I'll start googling.. -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-26 11:27 +1100 |
| Message-ID | <ecb6gfFml49U1@mid.individual.net> |
| In reply to | #56710 |
On Monday, 26 Dec 2016 11:16 AM, felix wrote: > On Monday, 26 Dec 2016 9:36 AM, Rod Speed wrote: >> >> >> "felix" <me@nothere.invalid> wrote in message >> news:ecarj3Fk6d5U1@mid.individual.net... >>> On Monday, 26 Dec 2016 12:26 AM, felix wrote: >>>> On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >>>>> >>>>> >>>>> "felix" <me@nothere.invalid> wrote in message >>>>> news:ec95dpF7tbiU1@mid.individual.net... >>>>>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>>>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>>>>> I've now determined that the problem is that the none of the >>>>>>>>>>> SATA ports >>>>>>>>>>> are working. the hard drive is not being seen and not >>>>>>>>>>> showing up in the >>>>>>>>>>> bios. so I assume that can only mean the SATA ports are >>>>>>>>>>> cactus, as the >>>>>>>>>>> drive has power. >>>>>>>>>> Ok it has power, but have you tried it in another PC to see >>>>>>>>>> whether the >>>>>>>>>> control electronics have thrown in the towl? >>>>>>>>>> >>>>>>>>>> Any chance that the BIOS settings have got scrambled due to some >>>>>>>>>> glitch or a failing backup battery and the SATA controller's >>>>>>>>>> simply >>>>>>>>>> disabled? >>>>>>>>>> >>>>>>>>> >>>>>>>>> it's showing up in the 'boot' section of the bios, and at >>>>>>>>> startup on the >>>>>>>>> blank black screen, but it's not showing as detected on the >>>>>>>>> sata port in >>>>>>>>> bios >>>>>>>>> >>>>>>>> That's probably because your Bios is in AHCI mode >>>>>>> >>>>>>> it is >>>>>>> >>>>>>>> which won't show drives there. Change the Bios to legacy mode >>>>>>>> and see if you can get it to boot >>>>>>> >>>>>>> still won't boot and still doesn't show on the sata port >>>>>>> >>>>>>>> (Needs to be under 2tb). >>>>>>> >>>>>>> 1Tb >>>>>>> >>>>>>>> It's not a faulty MB. It sounds like the standard windows boot >>>>>>>> sector issue, which could indicate a drive that has a failed >>>>>>>> boot sector or the bcd file has been corrupted. Put it in your >>>>>>>> other machine on another sata port and run from an admin dos >>>>>>>> prompt chkdsk x: /r where x: is the drive letter given to the >>>>>>>> drive by your machine. It may resolve the issue. >>>>>>>> >>>>>>>> You could also try this >>>>>>>> >>>>>>>> Open Command Prompt from Advanced Startup Options or System >>>>>>>> Recovery Options menu. Note: The Command Prompt available from >>>>>>>> these diagnostic menus is very similar to the one you may be >>>>>>>> familiar with within Windows. ... >>>>>>>> At the prompt, type the bootrec command as shown below and then >>>>>>>> press Enter: bootrec /rebuildbcd. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Ok, thanks I'll try those after Xmas. see, you are good for >>>>>>> something after all.. :) >>>>>>> >>>>>>> >>>>>> >>>>>> couldn't wait. I tried it last night. no different. btw.. the >>>>>> win10 message I get is 'inaccessible boot device' which still >>>>>> seems to indicate a hardware problem >>>>> >>>>> That's just saying it can't see a boot drive. >>>>> >>>>> I'd reset the cmos and see if the SATA ports work again. >>>> >>>> ok I'll give that a try tomorrow, thanks >>>>> >>>>> Very unlikely to be a hardware failure with all 8 sata ports >>>>> going missing given that 6 of them are on 1 chip and the >>>>> other two are on a different one. >>>> >>>> makes sense >>>> >>>>> >>>>> Nothing much shows up with google and that >>>>> motherboard, ask the manufacturer about it. >>>> >>>> >>> >>> I've established the SATA ports are working. I installed Linux on a >>> DVD and booted with a SATA drive connected and I could read the >>> drive and load files. seems it's nothing more than a corrupt win10 >>> 64 bit installation >> >> Yeah, looks like it. And if you had made the recovery disk >> when it was still working, it may have been able to recover it. > > I'll certainly make one when it's up and running again. or maybe there > is some third party recovery software I could use? or does M$ have any > 'after the event' repair program that can be put on disc? I'll start > googling.. > Ill try this.. http://www.instructables.com/id/How-to-Repair-Corrupted-Windows-10-System-Files/ -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-26 11:43 +1100 |
| Message-ID | <ecb7dmFmqqtU1@mid.individual.net> |
| In reply to | #56712 |
On Monday, 26 Dec 2016 11:27 AM, felix wrote: > On Monday, 26 Dec 2016 11:16 AM, felix wrote: >> On Monday, 26 Dec 2016 9:36 AM, Rod Speed wrote: >>> >>> >>> "felix" <me@nothere.invalid> wrote in message >>> news:ecarj3Fk6d5U1@mid.individual.net... >>>> On Monday, 26 Dec 2016 12:26 AM, felix wrote: >>>>> On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >>>>>> >>>>>> >>>>>> "felix" <me@nothere.invalid> wrote in message >>>>>> news:ec95dpF7tbiU1@mid.individual.net... >>>>>>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>>>>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>>>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>>>>>> I've now determined that the problem is that the none of >>>>>>>>>>>> the SATA ports >>>>>>>>>>>> are working. the hard drive is not being seen and not >>>>>>>>>>>> showing up in the >>>>>>>>>>>> bios. so I assume that can only mean the SATA ports are >>>>>>>>>>>> cactus, as the >>>>>>>>>>>> drive has power. >>>>>>>>>>> Ok it has power, but have you tried it in another PC to see >>>>>>>>>>> whether the >>>>>>>>>>> control electronics have thrown in the towl? >>>>>>>>>>> >>>>>>>>>>> Any chance that the BIOS settings have got scrambled due to >>>>>>>>>>> some >>>>>>>>>>> glitch or a failing backup battery and the SATA controller's >>>>>>>>>>> simply >>>>>>>>>>> disabled? >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> it's showing up in the 'boot' section of the bios, and at >>>>>>>>>> startup on the >>>>>>>>>> blank black screen, but it's not showing as detected on the >>>>>>>>>> sata port in >>>>>>>>>> bios >>>>>>>>>> >>>>>>>>> That's probably because your Bios is in AHCI mode >>>>>>>> >>>>>>>> it is >>>>>>>> >>>>>>>>> which won't show drives there. Change the Bios to legacy mode >>>>>>>>> and see if you can get it to boot >>>>>>>> >>>>>>>> still won't boot and still doesn't show on the sata port >>>>>>>> >>>>>>>>> (Needs to be under 2tb). >>>>>>>> >>>>>>>> 1Tb >>>>>>>> >>>>>>>>> It's not a faulty MB. It sounds like the standard windows boot >>>>>>>>> sector issue, which could indicate a drive that has a failed >>>>>>>>> boot sector or the bcd file has been corrupted. Put it in your >>>>>>>>> other machine on another sata port and run from an admin dos >>>>>>>>> prompt chkdsk x: /r where x: is the drive letter given to the >>>>>>>>> drive by your machine. It may resolve the issue. >>>>>>>>> >>>>>>>>> You could also try this >>>>>>>>> >>>>>>>>> Open Command Prompt from Advanced Startup Options or System >>>>>>>>> Recovery Options menu. Note: The Command Prompt available from >>>>>>>>> these diagnostic menus is very similar to the one you may be >>>>>>>>> familiar with within Windows. ... >>>>>>>>> At the prompt, type the bootrec command as shown below and >>>>>>>>> then press Enter: bootrec /rebuildbcd. >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> Ok, thanks I'll try those after Xmas. see, you are good for >>>>>>>> something after all.. :) >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> couldn't wait. I tried it last night. no different. btw.. the >>>>>>> win10 message I get is 'inaccessible boot device' which still >>>>>>> seems to indicate a hardware problem >>>>>> >>>>>> That's just saying it can't see a boot drive. >>>>>> >>>>>> I'd reset the cmos and see if the SATA ports work again. >>>>> >>>>> ok I'll give that a try tomorrow, thanks >>>>>> >>>>>> Very unlikely to be a hardware failure with all 8 sata ports >>>>>> going missing given that 6 of them are on 1 chip and the >>>>>> other two are on a different one. >>>>> >>>>> makes sense >>>>> >>>>>> >>>>>> Nothing much shows up with google and that >>>>>> motherboard, ask the manufacturer about it. >>>>> >>>>> >>>> >>>> I've established the SATA ports are working. I installed Linux on a >>>> DVD and booted with a SATA drive connected and I could read the >>>> drive and load files. seems it's nothing more than a corrupt win10 >>>> 64 bit installation >>> >>> Yeah, looks like it. And if you had made the recovery disk >>> when it was still working, it may have been able to recover it. >> >> I'll certainly make one when it's up and running again. or maybe >> there is some third party recovery software I could use? or does M$ >> have any 'after the event' repair program that can be put on disc? >> I'll start googling.. >> > > Ill try this.. > > http://www.instructables.com/id/How-to-Repair-Corrupted-Windows-10-System-Files/ > > > can't. no mouse pointer :( -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-26 11:50 +1100 |
| Message-ID | <ecb7q1Fmt3vU1@mid.individual.net> |
| In reply to | #56713 |
On Monday, 26 Dec 2016 11:43 AM, felix wrote: > On Monday, 26 Dec 2016 11:27 AM, felix wrote: >> On Monday, 26 Dec 2016 11:16 AM, felix wrote: >>> On Monday, 26 Dec 2016 9:36 AM, Rod Speed wrote: >>>> >>>> >>>> "felix" <me@nothere.invalid> wrote in message >>>> news:ecarj3Fk6d5U1@mid.individual.net... >>>>> On Monday, 26 Dec 2016 12:26 AM, felix wrote: >>>>>> On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >>>>>>> >>>>>>> >>>>>>> "felix" <me@nothere.invalid> wrote in message >>>>>>> news:ec95dpF7tbiU1@mid.individual.net... >>>>>>>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>>>>>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>>>>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>>>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>>>>>>> I've now determined that the problem is that the none of >>>>>>>>>>>>> the SATA ports >>>>>>>>>>>>> are working. the hard drive is not being seen and not >>>>>>>>>>>>> showing up in the >>>>>>>>>>>>> bios. so I assume that can only mean the SATA ports are >>>>>>>>>>>>> cactus, as the >>>>>>>>>>>>> drive has power. >>>>>>>>>>>> Ok it has power, but have you tried it in another PC to see >>>>>>>>>>>> whether the >>>>>>>>>>>> control electronics have thrown in the towl? >>>>>>>>>>>> >>>>>>>>>>>> Any chance that the BIOS settings have got scrambled due to >>>>>>>>>>>> some >>>>>>>>>>>> glitch or a failing backup battery and the SATA >>>>>>>>>>>> controller's simply >>>>>>>>>>>> disabled? >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> it's showing up in the 'boot' section of the bios, and at >>>>>>>>>>> startup on the >>>>>>>>>>> blank black screen, but it's not showing as detected on the >>>>>>>>>>> sata port in >>>>>>>>>>> bios >>>>>>>>>>> >>>>>>>>>> That's probably because your Bios is in AHCI mode >>>>>>>>> >>>>>>>>> it is >>>>>>>>> >>>>>>>>>> which won't show drives there. Change the Bios to legacy mode >>>>>>>>>> and see if you can get it to boot >>>>>>>>> >>>>>>>>> still won't boot and still doesn't show on the sata port >>>>>>>>> >>>>>>>>>> (Needs to be under 2tb). >>>>>>>>> >>>>>>>>> 1Tb >>>>>>>>> >>>>>>>>>> It's not a faulty MB. It sounds like the standard windows >>>>>>>>>> boot sector issue, which could indicate a drive that has a >>>>>>>>>> failed boot sector or the bcd file has been corrupted. Put it >>>>>>>>>> in your other machine on another sata port and run from an >>>>>>>>>> admin dos prompt chkdsk x: /r where x: is the drive letter >>>>>>>>>> given to the drive by your machine. It may resolve the issue. >>>>>>>>>> >>>>>>>>>> You could also try this >>>>>>>>>> >>>>>>>>>> Open Command Prompt from Advanced Startup Options or System >>>>>>>>>> Recovery Options menu. Note: The Command Prompt available >>>>>>>>>> from these diagnostic menus is very similar to the one you >>>>>>>>>> may be familiar with within Windows. ... >>>>>>>>>> At the prompt, type the bootrec command as shown below and >>>>>>>>>> then press Enter: bootrec /rebuildbcd. >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> Ok, thanks I'll try those after Xmas. see, you are good for >>>>>>>>> something after all.. :) >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> couldn't wait. I tried it last night. no different. btw.. the >>>>>>>> win10 message I get is 'inaccessible boot device' which still >>>>>>>> seems to indicate a hardware problem >>>>>>> >>>>>>> That's just saying it can't see a boot drive. >>>>>>> >>>>>>> I'd reset the cmos and see if the SATA ports work again. >>>>>> >>>>>> ok I'll give that a try tomorrow, thanks >>>>>>> >>>>>>> Very unlikely to be a hardware failure with all 8 sata ports >>>>>>> going missing given that 6 of them are on 1 chip and the >>>>>>> other two are on a different one. >>>>>> >>>>>> makes sense >>>>>> >>>>>>> >>>>>>> Nothing much shows up with google and that >>>>>>> motherboard, ask the manufacturer about it. >>>>>> >>>>>> >>>>> >>>>> I've established the SATA ports are working. I installed Linux on >>>>> a DVD and booted with a SATA drive connected and I could read the >>>>> drive and load files. seems it's nothing more than a corrupt win10 >>>>> 64 bit installation >>>> >>>> Yeah, looks like it. And if you had made the recovery disk >>>> when it was still working, it may have been able to recover it. >>> >>> I'll certainly make one when it's up and running again. or maybe >>> there is some third party recovery software I could use? or does M$ >>> have any 'after the event' repair program that can be put on disc? >>> I'll start googling.. >>> >> >> Ill try this.. >> >> http://www.instructables.com/id/How-to-Repair-Corrupted-Windows-10-System-Files/ >> >> >> > > can't. no mouse pointer :( > > I see now I can get the dos box via advanced options. if the scan doesn't work, I'll try system restore from the latest restore point (if it's accessible) -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | felix <me@nothere.invalid> |
|---|---|
| Date | 2016-12-26 12:36 +1100 |
| Message-ID | <ecbag5Fnfo4U1@mid.individual.net> |
| In reply to | #56714 |
On Monday, 26 Dec 2016 11:50 AM, felix wrote: > On Monday, 26 Dec 2016 11:43 AM, felix wrote: >> On Monday, 26 Dec 2016 11:27 AM, felix wrote: >>> On Monday, 26 Dec 2016 11:16 AM, felix wrote: >>>> On Monday, 26 Dec 2016 9:36 AM, Rod Speed wrote: >>>>> >>>>> >>>>> "felix" <me@nothere.invalid> wrote in message >>>>> news:ecarj3Fk6d5U1@mid.individual.net... >>>>>> On Monday, 26 Dec 2016 12:26 AM, felix wrote: >>>>>>> On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >>>>>>>> >>>>>>>> >>>>>>>> "felix" <me@nothere.invalid> wrote in message >>>>>>>> news:ec95dpF7tbiU1@mid.individual.net... >>>>>>>>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>>>>>>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>>>>>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>>>>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>>>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>>>>>>>> I've now determined that the problem is that the none of >>>>>>>>>>>>>> the SATA ports >>>>>>>>>>>>>> are working. the hard drive is not being seen and not >>>>>>>>>>>>>> showing up in the >>>>>>>>>>>>>> bios. so I assume that can only mean the SATA ports are >>>>>>>>>>>>>> cactus, as the >>>>>>>>>>>>>> drive has power. >>>>>>>>>>>>> Ok it has power, but have you tried it in another PC to >>>>>>>>>>>>> see whether the >>>>>>>>>>>>> control electronics have thrown in the towl? >>>>>>>>>>>>> >>>>>>>>>>>>> Any chance that the BIOS settings have got scrambled due >>>>>>>>>>>>> to some >>>>>>>>>>>>> glitch or a failing backup battery and the SATA >>>>>>>>>>>>> controller's simply >>>>>>>>>>>>> disabled? >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> it's showing up in the 'boot' section of the bios, and at >>>>>>>>>>>> startup on the >>>>>>>>>>>> blank black screen, but it's not showing as detected on the >>>>>>>>>>>> sata port in >>>>>>>>>>>> bios >>>>>>>>>>>> >>>>>>>>>>> That's probably because your Bios is in AHCI mode >>>>>>>>>> >>>>>>>>>> it is >>>>>>>>>> >>>>>>>>>>> which won't show drives there. Change the Bios to legacy >>>>>>>>>>> mode and see if you can get it to boot >>>>>>>>>> >>>>>>>>>> still won't boot and still doesn't show on the sata port >>>>>>>>>> >>>>>>>>>>> (Needs to be under 2tb). >>>>>>>>>> >>>>>>>>>> 1Tb >>>>>>>>>> >>>>>>>>>>> It's not a faulty MB. It sounds like the standard windows >>>>>>>>>>> boot sector issue, which could indicate a drive that has a >>>>>>>>>>> failed boot sector or the bcd file has been corrupted. Put >>>>>>>>>>> it in your other machine on another sata port and run from >>>>>>>>>>> an admin dos prompt chkdsk x: /r where x: is the drive >>>>>>>>>>> letter given to the drive by your machine. It may resolve >>>>>>>>>>> the issue. >>>>>>>>>>> >>>>>>>>>>> You could also try this >>>>>>>>>>> >>>>>>>>>>> Open Command Prompt from Advanced Startup Options or System >>>>>>>>>>> Recovery Options menu. Note: The Command Prompt available >>>>>>>>>>> from these diagnostic menus is very similar to the one you >>>>>>>>>>> may be familiar with within Windows. ... >>>>>>>>>>> At the prompt, type the bootrec command as shown below and >>>>>>>>>>> then press Enter: bootrec /rebuildbcd. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Ok, thanks I'll try those after Xmas. see, you are good for >>>>>>>>>> something after all.. :) >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> couldn't wait. I tried it last night. no different. btw.. the >>>>>>>>> win10 message I get is 'inaccessible boot device' which still >>>>>>>>> seems to indicate a hardware problem >>>>>>>> >>>>>>>> That's just saying it can't see a boot drive. >>>>>>>> >>>>>>>> I'd reset the cmos and see if the SATA ports work again. >>>>>>> >>>>>>> ok I'll give that a try tomorrow, thanks >>>>>>>> >>>>>>>> Very unlikely to be a hardware failure with all 8 sata ports >>>>>>>> going missing given that 6 of them are on 1 chip and the >>>>>>>> other two are on a different one. >>>>>>> >>>>>>> makes sense >>>>>>> >>>>>>>> >>>>>>>> Nothing much shows up with google and that >>>>>>>> motherboard, ask the manufacturer about it. >>>>>>> >>>>>>> >>>>>> >>>>>> I've established the SATA ports are working. I installed Linux on >>>>>> a DVD and booted with a SATA drive connected and I could read the >>>>>> drive and load files. seems it's nothing more than a corrupt >>>>>> win10 64 bit installation >>>>> >>>>> Yeah, looks like it. And if you had made the recovery disk >>>>> when it was still working, it may have been able to recover it. >>>> >>>> I'll certainly make one when it's up and running again. or maybe >>>> there is some third party recovery software I could use? or does M$ >>>> have any 'after the event' repair program that can be put on disc? >>>> I'll start googling.. >>>> >>> >>> Ill try this.. >>> >>> http://www.instructables.com/id/How-to-Repair-Corrupted-Windows-10-System-Files/ >>> >>> >>> >> >> can't. no mouse pointer :( >> >> > > I see now I can get the dos box via advanced options. if the scan > doesn't work, I'll try system restore from the latest restore point > (if it's accessible) > it's now saying there are no restore points, but there are (were) It's looking like I'll just have to restore from an image of the drive. maybe some virus got thru and screwed the drive? I was using avast on that PC -- I plan on living forever. So far so good!
[toc] | [prev] | [next] | [standalone]
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Date | 2016-12-26 12:57 +1100 |
| Message-ID | <ecbbs1Fnof7U1@mid.individual.net> |
| In reply to | #56720 |
"felix" <me@nothere.invalid> wrote in message news:ecbag5Fnfo4U1@mid.individual.net... > On Monday, 26 Dec 2016 11:50 AM, felix wrote: >> On Monday, 26 Dec 2016 11:43 AM, felix wrote: >>> On Monday, 26 Dec 2016 11:27 AM, felix wrote: >>>> On Monday, 26 Dec 2016 11:16 AM, felix wrote: >>>>> On Monday, 26 Dec 2016 9:36 AM, Rod Speed wrote: >>>>>> >>>>>> >>>>>> "felix" <me@nothere.invalid> wrote in message >>>>>> news:ecarj3Fk6d5U1@mid.individual.net... >>>>>>> On Monday, 26 Dec 2016 12:26 AM, felix wrote: >>>>>>>> On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> "felix" <me@nothere.invalid> wrote in message >>>>>>>>> news:ec95dpF7tbiU1@mid.individual.net... >>>>>>>>>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>>>>>>>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>>>>>>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>>>>>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>>>>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>>>>>>>>> I've now determined that the problem is that the none of the >>>>>>>>>>>>>>> SATA ports >>>>>>>>>>>>>>> are working. the hard drive is not being seen and not >>>>>>>>>>>>>>> showing up in the >>>>>>>>>>>>>>> bios. so I assume that can only mean the SATA ports are >>>>>>>>>>>>>>> cactus, as the >>>>>>>>>>>>>>> drive has power. >>>>>>>>>>>>>> Ok it has power, but have you tried it in another PC to see >>>>>>>>>>>>>> whether the >>>>>>>>>>>>>> control electronics have thrown in the towl? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Any chance that the BIOS settings have got scrambled due to >>>>>>>>>>>>>> some >>>>>>>>>>>>>> glitch or a failing backup battery and the SATA controller's >>>>>>>>>>>>>> simply >>>>>>>>>>>>>> disabled? >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> it's showing up in the 'boot' section of the bios, and at >>>>>>>>>>>>> startup on the >>>>>>>>>>>>> blank black screen, but it's not showing as detected on the >>>>>>>>>>>>> sata port in >>>>>>>>>>>>> bios >>>>>>>>>>>>> >>>>>>>>>>>> That's probably because your Bios is in AHCI mode >>>>>>>>>>> >>>>>>>>>>> it is >>>>>>>>>>> >>>>>>>>>>>> which won't show drives there. Change the Bios to legacy mode >>>>>>>>>>>> and see if you can get it to boot >>>>>>>>>>> >>>>>>>>>>> still won't boot and still doesn't show on the sata port >>>>>>>>>>> >>>>>>>>>>>> (Needs to be under 2tb). >>>>>>>>>>> >>>>>>>>>>> 1Tb >>>>>>>>>>> >>>>>>>>>>>> It's not a faulty MB. It sounds like the standard windows boot >>>>>>>>>>>> sector issue, which could indicate a drive that has a failed >>>>>>>>>>>> boot sector or the bcd file has been corrupted. Put it in your >>>>>>>>>>>> other machine on another sata port and run from an admin dos >>>>>>>>>>>> prompt chkdsk x: /r where x: is the drive letter given to the >>>>>>>>>>>> drive by your machine. It may resolve the issue. >>>>>>>>>>>> >>>>>>>>>>>> You could also try this >>>>>>>>>>>> >>>>>>>>>>>> Open Command Prompt from Advanced Startup Options or System >>>>>>>>>>>> Recovery Options menu. Note: The Command Prompt available from >>>>>>>>>>>> these diagnostic menus is very similar to the one you may be >>>>>>>>>>>> familiar with within Windows. ... >>>>>>>>>>>> At the prompt, type the bootrec command as shown below and then >>>>>>>>>>>> press Enter: bootrec /rebuildbcd. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Ok, thanks I'll try those after Xmas. see, you are good for >>>>>>>>>>> something after all.. :) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> couldn't wait. I tried it last night. no different. btw.. the >>>>>>>>>> win10 message I get is 'inaccessible boot device' which still >>>>>>>>>> seems to indicate a hardware problem >>>>>>>>> >>>>>>>>> That's just saying it can't see a boot drive. >>>>>>>>> >>>>>>>>> I'd reset the cmos and see if the SATA ports work again. >>>>>>>> >>>>>>>> ok I'll give that a try tomorrow, thanks >>>>>>>>> >>>>>>>>> Very unlikely to be a hardware failure with all 8 sata ports >>>>>>>>> going missing given that 6 of them are on 1 chip and the >>>>>>>>> other two are on a different one. >>>>>>>> >>>>>>>> makes sense >>>>>>>> >>>>>>>>> >>>>>>>>> Nothing much shows up with google and that >>>>>>>>> motherboard, ask the manufacturer about it. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> I've established the SATA ports are working. I installed Linux on a >>>>>>> DVD and booted with a SATA drive connected and I could read the >>>>>>> drive and load files. seems it's nothing more than a corrupt win10 >>>>>>> 64 bit installation >>>>>> >>>>>> Yeah, looks like it. And if you had made the recovery disk >>>>>> when it was still working, it may have been able to recover it. >>>>> >>>>> I'll certainly make one when it's up and running again. or maybe there >>>>> is some third party recovery software I could use? or does M$ have any >>>>> 'after the event' repair program that can be put on disc? I'll start >>>>> googling.. >>>>> >>>> >>>> Ill try this.. >>>> >>>> http://www.instructables.com/id/How-to-Repair-Corrupted-Windows-10-System-Files/ >>>> >>>> >>> >>> can't. no mouse pointer :( >>> >>> >> >> I see now I can get the dos box via advanced options. if the scan doesn't >> work, I'll try system restore from the latest restore point (if it's >> accessible) >> > > it's now saying there are no restore points, but there are (were) It's > looking like I'll just have to restore from an image of the drive. That's not that uncommon. > maybe some virus got thru and screwed the drive? More likely win just lost the restore points, that can happen. > I was using avast on that PC
[toc] | [prev] | [next] | [standalone]
| From | Jeßus <j@j.org> |
|---|---|
| Date | 2016-12-26 12:02 +1100 |
| Message-ID | <70r06chj05ldrf6sqo1hn6ap5fa0frifr7@j.net> |
| In reply to | #56713 |
On Mon, 26 Dec 2016 11:43:33 +1100, felix <me@nothere.invalid> wrote: >> Ill try this.. >> >> http://www.instructables.com/id/How-to-Repair-Corrupted-Windows-10-System-Files/ >> >> >> > >can't. no mouse pointer :( Use the keyboard then. That's what it's for.
[toc] | [prev] | [next] | [standalone]
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Date | 2016-12-26 12:51 +1100 |
| Message-ID | <ecbbe1Fnlh1U1@mid.individual.net> |
| In reply to | #56710 |
"felix" <me@nothere.invalid> wrote in message news:ecb5qgFmgatU1@mid.individual.net... > On Monday, 26 Dec 2016 9:36 AM, Rod Speed wrote: >> >> >> "felix" <me@nothere.invalid> wrote in message >> news:ecarj3Fk6d5U1@mid.individual.net... >>> On Monday, 26 Dec 2016 12:26 AM, felix wrote: >>>> On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >>>>> >>>>> >>>>> "felix" <me@nothere.invalid> wrote in message >>>>> news:ec95dpF7tbiU1@mid.individual.net... >>>>>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>>>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>>>>> I've now determined that the problem is that the none of the >>>>>>>>>>> SATA ports >>>>>>>>>>> are working. the hard drive is not being seen and not showing up >>>>>>>>>>> in the >>>>>>>>>>> bios. so I assume that can only mean the SATA ports are cactus, >>>>>>>>>>> as the >>>>>>>>>>> drive has power. >>>>>>>>>> Ok it has power, but have you tried it in another PC to see >>>>>>>>>> whether the >>>>>>>>>> control electronics have thrown in the towl? >>>>>>>>>> >>>>>>>>>> Any chance that the BIOS settings have got scrambled due to some >>>>>>>>>> glitch or a failing backup battery and the SATA controller's >>>>>>>>>> simply >>>>>>>>>> disabled? >>>>>>>>>> >>>>>>>>> >>>>>>>>> it's showing up in the 'boot' section of the bios, and at startup >>>>>>>>> on the >>>>>>>>> blank black screen, but it's not showing as detected on the sata >>>>>>>>> port in >>>>>>>>> bios >>>>>>>>> >>>>>>>> That's probably because your Bios is in AHCI mode >>>>>>> >>>>>>> it is >>>>>>> >>>>>>>> which won't show drives there. Change the Bios to legacy mode and >>>>>>>> see if you can get it to boot >>>>>>> >>>>>>> still won't boot and still doesn't show on the sata port >>>>>>> >>>>>>>> (Needs to be under 2tb). >>>>>>> >>>>>>> 1Tb >>>>>>> >>>>>>>> It's not a faulty MB. It sounds like the standard windows boot >>>>>>>> sector issue, which could indicate a drive that has a failed boot >>>>>>>> sector or the bcd file has been corrupted. Put it in your other >>>>>>>> machine on another sata port and run from an admin dos prompt >>>>>>>> chkdsk x: /r where x: is the drive letter given to the drive by >>>>>>>> your machine. It may resolve the issue. >>>>>>>> >>>>>>>> You could also try this >>>>>>>> >>>>>>>> Open Command Prompt from Advanced Startup Options or System >>>>>>>> Recovery Options menu. Note: The Command Prompt available from >>>>>>>> these diagnostic menus is very similar to the one you may be >>>>>>>> familiar with within Windows. ... >>>>>>>> At the prompt, type the bootrec command as shown below and then >>>>>>>> press Enter: bootrec /rebuildbcd. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Ok, thanks I'll try those after Xmas. see, you are good for >>>>>>> something after all.. :) >>>>>>> >>>>>>> >>>>>> >>>>>> couldn't wait. I tried it last night. no different. btw.. the win10 >>>>>> message I get is 'inaccessible boot device' which still seems to >>>>>> indicate a hardware problem >>>>> >>>>> That's just saying it can't see a boot drive. >>>>> >>>>> I'd reset the cmos and see if the SATA ports work again. >>>> >>>> ok I'll give that a try tomorrow, thanks >>>>> >>>>> Very unlikely to be a hardware failure with all 8 sata ports >>>>> going missing given that 6 of them are on 1 chip and the >>>>> other two are on a different one. >>>> >>>> makes sense >>>> >>>>> >>>>> Nothing much shows up with google and that >>>>> motherboard, ask the manufacturer about it. >>>> >>>> >>> >>> I've established the SATA ports are working. I installed Linux on a DVD >>> and booted with a SATA drive connected and I could read the drive and >>> load files. seems it's nothing more than a corrupt win10 64 bit >>> installation >> >> Yeah, looks like it. And if you had made the recovery disk >> when it was still working, it may have been able to recover it. > > I'll certainly make one when it's up and running again. or maybe there is > some third party recovery software I could use? or does M$ have any 'after > the event' repair program that can be put on disc? I'll start googling.. Yes, you can still do a repair install.
[toc] | [prev] | [next] | [standalone]
| From | "SG1" <lost@the.races.com> |
|---|---|
| Date | 2016-12-26 11:52 +1000 |
| Message-ID | <586077c8$0$53460$c3e8da3$b1356c67@news.astraweb.com> |
| In reply to | #56710 |
"felix" <me@nothere.invalid> wrote in message news:ecb5qgFmgatU1@mid.individual.net... > On Monday, 26 Dec 2016 9:36 AM, Rod Speed wrote: >> >> >> "felix" <me@nothere.invalid> wrote in message >> news:ecarj3Fk6d5U1@mid.individual.net... >>> On Monday, 26 Dec 2016 12:26 AM, felix wrote: >>>> On Sunday, 25 Dec 2016 5:49 PM, Rod Speed wrote: >>>>> >>>>> >>>>> "felix" <me@nothere.invalid> wrote in message >>>>> news:ec95dpF7tbiU1@mid.individual.net... >>>>>> On Sunday, 25 Dec 2016 12:06 AM, felix wrote: >>>>>>> On Saturday, 24 Dec 2016 10:09 PM, Grumpy Tech wrote: >>>>>>>> On 24/12/2016 7:59 PM, felix wrote: >>>>>>>>> On Friday, 23 Dec 2016 10:28 PM, Computer Nerd Kev wrote: >>>>>>>>>> felix <me@nothere.invalid> wrote: >>>>>>>>>>> I've now determined that the problem is that the none of the >>>>>>>>>>> SATA ports >>>>>>>>>>> are working. the hard drive is not being seen and not showing up >>>>>>>>>>> in the >>>>>>>>>>> bios. so I assume that can only mean the SATA ports are cactus, >>>>>>>>>>> as the >>>>>>>>>>> drive has power. >>>>>>>>>> Ok it has power, but have you tried it in another PC to see >>>>>>>>>> whether the >>>>>>>>>> control electronics have thrown in the towl? >>>>>>>>>> >>>>>>>>>> Any chance that the BIOS settings have got scrambled due to some >>>>>>>>>> glitch or a failing backup battery and the SATA controller's >>>>>>>>>> simply >>>>>>>>>> disabled? >>>>>>>>>> >>>>>>>>> >>>>>>>>> it's showing up in the 'boot' section of the bios, and at startup >>>>>>>>> on the >>>>>>>>> blank black screen, but it's not showing as detected on the sata >>>>>>>>> port in >>>>>>>>> bios >>>>>>>>> >>>>>>>> That's probably because your Bios is in AHCI mode >>>>>>> >>>>>>> it is >>>>>>> >>>>>>>> which won't show drives there. Change the Bios to legacy mode and >>>>>>>> see if you can get it to boot >>>>>>> >>>>>>> still won't boot and still doesn't show on the sata port >>>>>>> >>>>>>>> (Needs to be under 2tb). >>>>>>> >>>>>>> 1Tb >>>>>>> >>>>>>>> It's not a faulty MB. It sounds like the standard windows boot >>>>>>>> sector issue, which could indicate a drive that has a failed boot >>>>>>>> sector or the bcd file has been corrupted. Put it in your other >>>>>>>> machine on another sata port and run from an admin dos prompt >>>>>>>> chkdsk x: /r where x: is the drive letter given to the drive by >>>>>>>> your machine. It may resolve the issue. >>>>>>>> >>>>>>>> You could also try this >>>>>>>> >>>>>>>> Open Command Prompt from Advanced Startup Options or System >>>>>>>> Recovery Options menu. Note: The Command Prompt available from >>>>>>>> these diagnostic menus is very similar to the one you may be >>>>>>>> familiar with within Windows. ... >>>>>>>> At the prompt, type the bootrec command as shown below and then >>>>>>>> press Enter: bootrec /rebuildbcd. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Ok, thanks I'll try those after Xmas. see, you are good for >>>>>>> something after all.. :) >>>>>>> >>>>>>> >>>>>> >>>>>> couldn't wait. I tried it last night. no different. btw.. the win10 >>>>>> message I get is 'inaccessible boot device' which still seems to >>>>>> indicate a hardware problem >>>>> >>>>> That's just saying it can't see a boot drive. >>>>> >>>>> I'd reset the cmos and see if the SATA ports work again. >>>> >>>> ok I'll give that a try tomorrow, thanks >>>>> >>>>> Very unlikely to be a hardware failure with all 8 sata ports >>>>> going missing given that 6 of them are on 1 chip and the >>>>> other two are on a different one. >>>> >>>> makes sense >>>> >>>>> >>>>> Nothing much shows up with google and that >>>>> motherboard, ask the manufacturer about it. >>>> >>>> >>> >>> I've established the SATA ports are working. I installed Linux on a DVD >>> and booted with a SATA drive connected and I could read the drive and >>> load files. seems it's nothing more than a corrupt win10 64 bit >>> installation >> >> Yeah, looks like it. And if you had made the recovery disk >> when it was still working, it may have been able to recover it. > > I'll certainly make one when it's up and running again. or maybe there is > some third party recovery software I could use? or does M$ have any 'after > the event' repair program that can be put on disc? I'll start googling.. They do for W7 so there is a good chance. > -- > I plan on living forever. So far so good! >
[toc] | [prev] | [next] | [standalone]
Page 3 of 5 — ← Prev page 1 2 [3] 4 5 Next page →
Back to top | Article view | aus.computers
csiph-web