GA-K8N Pro & Sil3512 "unmountable boot volume"

edited July 2004 in Hardware
after reading the thread i am still in limbo about what exactly to do.

I have a Ga-k8n pro mobo witht he sil3512 chip
i have two SATA hitachit 80 gig hard drives with 8 mb buffer
nec dvdrw nd 2500
sony cd/dvd rom
sony floppy
i have the latest drivers for the sil3512 chip (10050)
i have updated the bios to k8np.f11
i have turned off gigaraid in the bios
i have the computer to boot to scsi/raid/sata (but just shows scsi), then cdrom then floppy
and i have the sata raid set to "raid" and not base
i have created a raid 0 config with the two drives ( i did the auto config for the raid 0)
i am able to boot to the windows xp setup, press f6 and finds the right drivers, then goes thru the installition and then loads the drivers for the controller, i selected the one that says windows xp/ server 2k3
setup continues and then when the gray bar at the bottom of the blue screen says "setup is startign windows" it then gives me the error "unmountable boot volume"

so i have loaded the drivers for the sil3512 chip but it still doesnt seem to see the hard drives or just problem prevents me from installing.

can any one please help and tell me what i can do.
thanks in advance for any help
if you have more questions please reply and ill post questions.
thanks

Comments

  • SpinnerSpinner Birmingham, UK
    edited June 2004
    after reading the thread i am still in limbo about what exactly to do.

    I have a Ga-k8n pro mobo witht he sil3512 chip
    i have two SATA hitachit 80 gig hard drives with 8 mb buffer
    nec dvdrw nd 2500
    sony cd/dvd rom
    sony floppy
    i have the latest drivers for the sil3512 chip (10050)
    i have updated the bios to k8np.f11
    i have turned off gigaraid in the bios
    i have the computer to boot to scsi/raid/sata (but just shows scsi), then cdrom then floppy
    and i have the sata raid set to "raid" and not base
    i have created a raid 0 config with the two drives ( i did the auto config for the raid 0)
    i am able to boot to the windows xp setup, press f6 and finds the right drivers, then goes thru the installition and then loads the drivers for the controller, i selected the one that says windows xp/ server 2k3
    setup continues and then when the gray bar at the bottom of the blue screen says "setup is startign windows" it then gives me the error "unmountable boot volume"

    so i have loaded the drivers for the sil3512 chip but it still doesnt seem to see the hard drives or just problem prevents me from installing.

    can any one please help and tell me what i can do.
    thanks in advance for any help
    if you have more questions please reply and ill post questions.
    thanks
    Try downloading the latest drivers for your controller. You can get them from the Short-Media downloads section on the main page. v1.0.0.50 is currently the latest, you want the file labelled 3x12 SATA Raid Controller Driver (or something to that effect). Try that, and then post back.

    Cheers :)
  • edited June 2004
    i downloaded the drivers version 1.0.0.50 exctracted them to a floppy and ran the setup again, same problem. what else can i try to do to fix the problem. thanks again
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    i downloaded the drivers version 1.0.0.50 exctracted them to a floppy and ran the setup again, same problem. what else can i try to do to fix the problem. thanks again
    Forgive me for my delayed response, and I apologise for this post only covering rudimentary things, I'm really really busy at the moment. But anyways...

    I first suggest you check to make sure the hardware side of things is fully functioning. Check both drives are being detected correctly in the SATA Bios, (if you can see both drives listed when the SATA Bios display flashes up upon post, then that's fine). Check/swap out SATA cables, check/alter jumper settings on your drives, demolish then rebuild your RAID 0 array manually (The RAID FAQ's thread should offer you some tips for doing that) and double check everything, e.g. boot disk assignment in the SATA Bios, stuff like that (I'm just throwing random stuff at you here, it may not be applicable).

    The last thing you could do to fully test the two disks, is get a third, load the OS onto that (that disk running as an independent) and see if you can get the array working that way (just for testing purposes obviously).

    Do as much of that as you can, then post back. Also have a scout around other threads in, this, the Storage and Controller forum, as well as the Drivers and BIOS forum for posts that I've made which outline more specifically the correct BIOS settings etc for your kind of setup.

    But like I said, have a mess around with the things I've thrown at ya, then post back. Hopefully by then I'll have more time to really work through the problem with ya. We'll get it working one way or the other.

    Cheers

    Spinner

    EDIT: Also, disable all of your additional USB controller ports i.e the ones on the mobo not at the back of the case that require the attachment of a PCI slot back plate. Unplug any such connections manually aswell e.g Make sure no cables are attached to them.
  • edited June 2004
    Spinner thanks for the time

    both drives are being detected in the SATA Bios.
    i have deleted and created the raid 0 configuration.

    i have also disabeld the usb on the back and front of the computer. i also disabled the firewire on the mobo. I also disconnected the usb wires.

    i am also using windows fd, but this shouldnt make any difference when installing.

    i dont have an extra drive so i am unable to install xp on another drive and test the array from windows.

    i have also read some raid threads but still no advice i can seem to use.

    thanks
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    Spinner thanks for the time

    both drives are being detected in the SATA Bios.
    i have deleted and created the raid 0 configuration.

    i have also disabeld the usb on the back and front of the computer. i also disabled the firewire on the mobo. I also disconnected the usb wires.

    i am also using windows fd, but this shouldnt make any difference when installing.

    i dont have an extra drive so i am unable to install xp on another drive and test the array from windows.

    i have also read some raid threads but still no advice i can seem to use.

    thanks
    I presume you mean Windows XP Home when you say "Windows fd", correct me if that presumption is wrong. Anyways...

    I'm gonna keep us on the hardware route for now, I think we need to confirm the status of both the drives in question. You should...

    1) Download (if they have one) a HD diagnostic utility from IBM/Hitachi and test your drives individually. This is usually done in DOS or from floppy boot. This will confirm both your drives are healthy and functioning as they should. We need to eliminate drive failure before we can really move on.

    2) Try and install Windows on each drive individually on the SI 3512 controller, not setup in a RAID 0 array, but with the controller still set to function in RAID mode and not Base, just to confirm the integrity of the drive's as well as whether it is a RAID array problem or not. You'll still have to throw a driver at the installation as before (F6), but if it installs it means that it's a RAID array problem and not a controller or drive problem. If it doesn't install, then we'll know it's either a controller problem, or a HD problem. However the latter is something point 1) should eliminate for us.

    Do all of the above, then post back mate.

    Cheers
  • edited June 2004
    i am using windows xp fd, a version that fits on a dvd with lots of other programs bundled with it. found it on bittorrent. seems to be pretty promising, the guy who made it is from england.

    tested both drives with the extensive test which took about 30-45 min for each drive. both times the drives came back as fully functional and no errors.

    tried installing windows with no raid 0 config and usign the sataraid drivers with both disks, still same problem.

    tried isntalling windows with no raid 0 config for just one drive with drivers, still the same problem.

    next i will try a different copy of windows xp.

    thanks
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    next i will try a different copy of windows xp.

    thanks
    Yeah, I think that might be a good idea. LOL. ;D

    Post back though if you still have trouble after you've tried a more genuine copy of Windows XP.

    Cheers mate.
  • edited June 2004
    i just tried another version of windows xp still gives me the same problem

    happens at the same time as it did before durign the installition.

    what else can i try ?

    does that mean the controller is shot

    try installing to a ide drive

    thanks again
    :thumbsup:
  • SpinnerSpinner Birmingham, UK
    edited June 2004
    i just tried another version of windows xp still gives me the same problem

    happens at the same time as it did before durign the installition.

    what else can i try ?

    does that mean the controller is shot

    try installing to a ide drive

    thanks again
    :thumbsup:
    What SATA Controller BIOS version are you running? e.g v4.3.47
  • edited July 2004
    i am running sata controller bios verison v 4.3.43
  • SpinnerSpinner Birmingham, UK
    edited July 2004
    i am running sata controller bios verison v 4.3.43
    OK. Hang on in there, I'll wip you up a modded version of the latest BIOS for your board containing a slightly newer SATA bios version.

    I honestly don't think it will help, but it's the next thing to try.

    Forgive my delays in replying to you, I'm extremely busy at the moment. I'll post back later tonight.

    Spinner
  • SpinnerSpinner Birmingham, UK
    edited July 2004
    There you go. This will bring your SATA controller BIOS version to v4.3.47.

    Try it and post back. Remember to reset your BIOS and yank out your CMOS battery for a few minutes after you've successfully flashed.

    Also get docmemory from the downloads section here at Short-Media and test your memory chip(s).

    Cheers
    k8np.zip 294.8K
  • edited July 2004
    i used the new bios and flashed it to the board, then reset it, then poped the battery out.

    same problem comes up

    the doc memory disk i made wouldnt work on the computer ill try again in a bit.

    post back if i can do anythign else. thanks again i really am thankful.

    u can contact me on aim sn: stunhcterts
  • SpinnerSpinner Birmingham, UK
    edited July 2004
    i used the new bios and flashed it to the board, then reset it, then poped the battery out.

    same problem comes up

    the doc memory disk i made wouldnt work on the computer ill try again in a bit.

    post back if i can do anythign else. thanks again i really am thankful.

    u can contact me on aim sn: stunhcterts
    I think we need to get your memory tested. We need to eliminate it as a cause of the problem. Post back with exactly what the problem is you're having with Docmemory. It could be an indication of the existence of the actual problem we're trying to detect. :)
  • edited July 2004
    i open up the program use a blank floppy disk and run the docmemory program and load three files to the disk then i put it into my computer to test it out and it says its a non-system disk , repalce when ready blah blah

    so how do i make a boot disk for it
  • SpinnerSpinner Birmingham, UK
    edited July 2004
    i open up the program use a blank floppy disk and run the docmemory program and load three files to the disk then i put it into my computer to test it out and it says its a non-system disk , repalce when ready blah blah

    so how do i make a boot disk for it
    Hmm, try this:

    1) Insert blank floppy
    2) My Computer - Right Click Floppy Drive - Format - Tick the Make MS-Dos Startup Disk check box (or something to that effect). Then Format.
    3) Run the Docmemory installation application as usual

    I do it that way, and it works for me. Try that, if it still doesn't work post back.

    Cheers mate. :)
  • edited July 2004
    i was able to get the bootdisk to work and able to run docmemory
    but when i started the quick test or burn-in test the test starts and then the computer restarts and have tried like 10 times so i dont know what the problem is now.

    but when i do run the test i do see that it brings back a lot of "passed" results. it happens so quick i dont see if their are any failed tests.

    so whats next spinner?
  • SpinnerSpinner Birmingham, UK
    edited July 2004
    i was able to get the bootdisk to work and able to run docmemory
    but when i started the quick test or burn-in test the test starts and then the computer restarts and have tried like 10 times so i dont know what the problem is now.

    but when i do run the test i do see that it brings back a lot of "passed" results. it happens so quick i dont see if their are any failed tests.

    so whats next spinner?
    Okay, well to me, that's a pretty typical sign that one or more of your memory modules are up the shoot. Try testing them individually, i.e. take one out and run Docmemory then switch. That will tell us if it is either just one or both of your memory chips.

    Docmemory should be able run fine, it only tests the memory, so if it fails (e.g reboots) it means your memory is naff. That might well explain the unmountable boot volume problem you're having.

    So identify if both or just one of your memory modules are bad, and if they both are get yourself a basic replacement (borrow or buy) and use that for now, or if only one of your modules is dead, then just take it out and use the the good one.

    Try all that, then post back.
  • edited July 2004
    okay i tried each memory stick by its self and the computer restarts during the test. so i am guessing i have bad memory.

    i will borrow some memory from a friend tomorrow. until then i will regret buying simpletech memory for 184 dollars for 1 gig of ddr400. ill check into rmaing the memory so i can buy better memory. thanks again spinner ill post back after i get the memory.
  • SpinnerSpinner Birmingham, UK
    edited July 2004
    okay i tried each memory stick by its self and the computer restarts during the test. so i am guessing i have bad memory.

    i will borrow some memory from a friend tomorrow. until then i will regret buying simpletech memory for 184 dollars for 1 gig of ddr400. ill check into rmaing the memory so i can buy better memory. thanks again spinner ill post back after i get the memory.
    Okay, that sounds like a plan. Borrow before you buy. Let's just be 100% sure your memory is knackered before you go out and buy some more. I'm pretty sure it is the problem, but let's just make sure.

    Cheers
  • edited July 2004
    i have borrowed some memory from a friend ddr 2100 128 mbs. the problem is still the same keeps rebooting durign the test. this memory i know works on my friends machine.

    so why is the program rebooting while testing his memory if it work on his computer.

    could it be something with a memory controller on the board.

    so what nexts. i have till the 22 or so to rma my board, im thinkign about getting a new board with a different sata controller prolly from asus.
  • SpinnerSpinner Birmingham, UK
    edited July 2004
    i have borrowed some memory from a friend ddr 2100 128 mbs. the problem is still the same keeps rebooting durign the test. this memory i know works on my friends machine.

    so why is the program rebooting while testing his memory if it work on his computer.

    could it be something with a memory controller on the board.

    so what nexts. i have till the 22 or so to rma my board, im thinkign about getting a new board with a different sata controller prolly from asus.
    Okay, well have you tried the memory in various slots? Have you reset your BIOS to fail safe defaults? What CPU are you running? (Forgive me if I've missed it). Just try a few of those basic things before you read what I'm about to say next.

    Sadly, it is starting to sound more and more like a mobo problem and I think RMA'ing the thing wouldn't be the worst idea in the world.

    Here's the thing. Every time I start replying to threads like this, e.g. "GA-whatever problem", I'm always aware that most of the time the thread will end with the user replacing his motherboard. Why? Because Gigabyte can't make motherboards of any acceptable quality. You can come to this conclusion pretty easily yourself by just looking around the Drivers and BIOS forum as well as this one. 90% of all SATA related problems we deal with here are Gigabyte based. Fact. Whether it be "unmountable boot volumes", "hanging" or whatever, it's Gigabyte to blame, not the end-user, not the third party chips they use, but the company themselves. Gigabyte sell motherboards for pretty much the lowest prices in the main stream arena, and quite frankly, that's because they don't work and they know they can't get away with a higher price tag.

    I honestly think me and you, here and now, have pretty much tried everything we can to get your Gigabyte product working. My advice, take it back, get a refund, buy a new motherboard from say MSI, ASUS, or even fork out for ABIT, but never ever buy Gigabyte again, at least not until they can prove themselves worthy or your money. The Silicon Image 3512 controller is not to blame for your troubles, many of my systems use those exact chips and they run great.

    Sorry we couldn't resolve your problems, but like I said, it looks like it is not a config or other component problem, but a fault or flaw with the motherboard.

    Let us know how you get on.

    Regards

    Spinner
  • edited July 2004
    thanks spinner for all the advice

    i have a couple more questions thou.
    i looked at boards from asus and abit, found both with sata. they need to have sata since i have sata drives.

    so i be considered with any memory issues imight have with these boards.

    i dont really want to return the memory either i think it will work.

    i purchased my hardware from newegg, and actuallly i have gone over the refund limit of 30 days, so i have 90 days from 5/24/04 to send in my board to get a replacement, only thing is i dont want the same board. i want credit towards my new board, so i will call up tomorrow and see if that can happen, i am hopeful.

    im decidign between these boards, tell me what you think
    ASUS "K8V SE Deluxe"

    ABIT "KV8 Pro"

    ABIT "KV8-MAX3"

    thanks again
  • edited July 2004
    ok newegg wont give me a credit they will only replace the stupid mobo.

    so i can send in the mobo and get another one back.

    any ideas
  • SpinnerSpinner Birmingham, UK
    edited July 2004
    ok newegg wont give me a credit they will only replace the stupid mobo.

    so i can send in the mobo and get another one back.

    any ideas
    Well, that sucks. I have no reason to believe an exact replacement of the board will solve your problems. It just think the board is inherently dodgy, like with most stuff from GIGABYTE.

    If you don't want to run the risk of having a repeat of your recent problems, you just will need to fork out for a new board. You shouldn't have any issues with ASUS or ABIT, I mean, they're the best. ABIT in my opinion is the better board maker but ASUS are great too.

    Sorry to hear you can't get your money back. Let me know how you get on.

    Cheers
  • edited July 2004
    well i wrote a complaint email to newegg and they respond in a couple of days after they checked it out and decided to give me a full refund. along with 2nd day free shipping. so thats tight. ill get a credit once i send in my old mobo. its cool because now i get credit instead of the same board.

    i think ill go with the abit board.

    ill post back in a bit.
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited July 2004
    well i wrote a complaint email to newegg and they respond in a couple of days after they checked it out and decided to give me a full refund.
    Kudos to you for your persistance! Good job.

    The fact that Newegg changed their mind leads me to believe your Gigabyte problem is one they've heard often before. Spinner was right: our forums here are replete with users detailing problems with Gigabyte motherboards.

    Welcome to Short-Media. Make yourself at home. You've found a great computer tech forum!
  • edited July 2004
    Windows XP 64 bit addition now up and running on Gigabyte GA-K8N Pro!!!!!!!!

    Ok -- just got basic stuff loaded -- working off wife's pc to write this as I install software on 64 bit.

    Oddly - had to disable onboard lan and yet intalled a PCI Realtek card that I thought was equivalent -- yet the PCI card works on the built-in does not. Yet the built in worked fine in 32bit XP pro all along! Go figure, must be a 64bit-beta bug.

    Also - no luck with ITE raid in 64bit -- don't care right now as I have:

    1. Silicon Image raid correctly running on 2 Mirrored Maxtor 250 gig SATA drives. These run XP 32 bit edition
    2. On standard IDE – have 20 gig hard drive ata 66 with XP 64bit.

    I switch between them by simply change BOOT ORDER from scsi, scsi, scsi to hd0,scsi,scsi.

    Just starting with this – so seen no other issues yet.

    Windows update has nothing for the 64 bit OS! Microsoft asleep at wheel.

    BTW- played with a free download version Mandrake 10.0 will run – but very limited w/o Mozilla, flashplayer etc.
    Will have the Actual Mandrake 10.0 AMD64 bit version on Monday – let you know how that goes when have time to setup.



    Cheers
    Larry

    AMD XP 64 – 3200+
    512mb ram
    CD-RW
    Cd/Dvd reader
    30gig ide hard drive
    2x 250 g SATA drives (mirrored)
    Floppy Drive
    Nvidia Ge-force 8x AGP MX4400/ 64 mb by Maddog


    Almost forgot -- can see the 2 SATA drives while booted to XP 64-bit on the ide. The 64bit SATA driver works.
Sign In or Register to comment.