1. Forum
  2. Usenet
  3. UK.COMP.HOMEBUILT

  • Re: 90 sec bootup after swapping sata channels about

    From Lilly the punk@21:1/5 to Lilly the punk on Tue Jun 13 13:05:31 2023
    "Andy Burns" wrote in message news:[email protected]...

    Lilly the punk wrote:

    Any ideas lol?

    If you disconnect the other drives one at a time, is there a particular
    one that makes the delay go away?

    __

    That would be a nightmare andy it takes me about 2 hours and a lot of
    swearing and vows to assasinate the person who invented sata connectors etc just to wire them up but if all else fails I may try it say 2 per day lol

    Thanks

    Let's say I found one that IS causing it....what would that mean....that the drive was faulty?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lilly the punk@21:1/5 to All on Tue Jun 13 12:49:55 2023
    I have 9 hard drives

    I needed another so in order to accommodate I had to switch about power and data leads inside my case and after doing so it knocked the boot order out
    so into bios and set my ssd back to first boot.

    Now it takes 90 seconds to boot up instead of about 17

    I done a chkdsk no use.

    I made sure it was back on sata channel 1 no use

    I done a "last known good config" no use

    Any ideas lol?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Lilly the punk on Tue Jun 13 12:59:27 2023
    Lilly the punk wrote:

    Any ideas lol?

    If you disconnect the other drives one at a time, is there a particular
    one that makes the delay go away?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Lilly the punk on Tue Jun 13 13:42:53 2023
    Lilly the punk wrote:

    I may try it say 2 per day lol

    whatever to narrow it down, unplug half of them, if no different, unplug
    the other half, but ideally you want to find a single drive that's
    somehow causing it.

    Let's say I found one that IS causing it....what would that mean....that
    the drive was faulty?

    maybe drive, maybe cable, something loose?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lilly the punk@21:1/5 to Lilly the punk on Tue Jun 13 16:54:12 2023
    "Andy Burns" wrote in message news:[email protected]...

    Lilly the punk wrote:

    I may try it say 2 per day lol

    whatever to narrow it down, unplug half of them, if no different, unplug
    the other half, but ideally you want to find a single drive that's
    somehow causing it.

    Let's say I found one that IS causing it....what would that mean....that
    the drive was faulty?

    maybe drive, maybe cable, something loose?

    --

    CHEERS aNDY i WILL LET YOU KNOW HOW i GET ON.......

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From SH@21:1/5 to Lilly the punk on Tue Jun 13 19:10:34 2023
    On 13/06/2023 16:54, Lilly the punk wrote:


    "Andy Burns"  wrote in message news:[email protected]... Lilly the punk wrote:

    I may try it say 2 per day lol

    whatever to narrow it down, unplug half of them, if no different, unplug
    the other half, but ideally you want to find a single drive that's
    somehow causing it.

    Let's say I found one that IS causing it....what would that
    mean....that the drive was faulty?

    maybe drive, maybe cable, something loose?


    have a listen to the drives... can you hear oen of them doing lots of
    retries as in clicking, motor stop starting etc?

    You coudl also interrogate the SMART data for all of yoru drives and see
    which one is reporting lots of retries..

    Could mean either a duff drive or a duff SATA cable or one of the
    voltage rails is out of spec.

    Unusual for SATA ports on mobo or controller to go bad, might be woprth blasting some compressed air in the SATA ports you're using for the
    first time in case you have dust between plug & socket

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Vir Campestris@21:1/5 to Andy Burns on Sun Jun 18 17:12:18 2023
    On 13/06/2023 13:42, Andy Burns wrote:
    Lilly the punk wrote:

    I may try it say 2 per day lol

    whatever to narrow it down, unplug half of them, if no different, unplug
    the other half, but ideally you want to find a single drive that's
    somehow causing it.

    Let's say I found one that IS causing it....what would that
    mean....that the drive was faulty?

    maybe drive, maybe cable, something loose?

    Lilly, if you unplug 4 of them and the problem goes away make a note of
    which half it was - then plug a couple of them back in.

    That will tell you which pair of drives has the problem. You can then plug/unplug one drive and you'll then know which is the bad one.

    It's a little harder with the other 5, but the principle is the same.

    Good luck
    Andy

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lilly the punk@21:1/5 to Andy Burns on Fri Jul 28 00:46:50 2023
    "Vir Campestris" wrote in message news:u6nad2$1mp72$[email protected]...

    On 13/06/2023 13:42, Andy Burns wrote:
    Lilly the punk wrote:

    I may try it say 2 per day lol

    whatever to narrow it down, unplug half of them, if no different, unplug
    the other half, but ideally you want to find a single drive that's somehow causing it.

    Let's say I found one that IS causing it....what would that mean....that
    the drive was faulty?

    maybe drive, maybe cable, something loose?

    Lilly, if you unplug 4 of them and the problem goes away make a note of
    which half it was - then plug a couple of them back in.

    That will tell you which pair of drives has the problem. You can then plug/unplug one drive and you'll then know which is the bad one.

    It's a little harder with the other 5, but the principle is the same.

    Good luck
    Andy

    --

    I solved it by accident.

    For a while whenever I shut windows live mail I kept getting an error which
    U fixed by carrying out the instructions to defragment the mail store.

    But the error happened again and this time I couldn't fix it so I just put
    up with it. Then last week a different error happened and all my emails vanished completely and even when I went to the WLM folder all the folders
    were empty.

    By pure luck about 10 days earlier I had run a program which saves all your emails I think its called mail store or something so I put all my emails
    back into their folders and it all worked fine.

    No more error on shutting wlm down either.

    It cured my start up problem.

    No idea why it just did lol

    THANKS FOR ALL THE HELP GUYS!!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)