07-02-2010 04:56 PM
08-08-2011 04:28 PM
I also have this "non-system disc press any key" issue after trying to use the windows updater to update my second (storage only) Maxtor hard drive and NOT my boot-up Seagate hard drive. Like others, I actually managed to update the drive by creating a bootable CD as the Maxtor drive totally failed to do the upgrade following the Windows updater running. As I result I get the annoying non-system disc message every time my computer starts.
I will try the Windows 7 64 bit equivalent of the Vista repair and see if it works for me too (but not now - it's late and I want a fresh mind for this). I did raise a ticket for it last week but no response at all from Seagate on it. However, after my experience I also believe that this issue is caused by the Seagate Windows firmware updating software and recommend that until it is fixed (how will ytou know??) that you should only update your hard drive firmware using the bootable CD solution
08-08-2011 04:32 PM - edited 08-08-2011 04:33 PM
Non system disk is because it's trying to boot to another drive, F12, select the drive by name and it should then find the correct disk, no O/S on the disk, means no boot.
p.s never flash a drive in dos with another drive connected, always run the drive on it's own when updating FW.
10-20-2011 01:15 PM
One of my most popular IT pages
Sadly if the disk is now a brick, look into a warranty replacement
10-20-2011 01:30 PM
10-20-2011 01:32 PM
I have experienced issues with the Windows installer, so I suggest the CD version which seems to work perfect every time
01-08-2012 07:34 PM - edited 01-08-2012 07:51 PM
Hi, I wonder how your story went on? I tried the same firmware upgrade also having a Intel SSD510 in my PC and beside the annoying "non system disk" message, the Intel SSD tool now also claims that the drive needs replacement.
Did you actually have to replace your SSD and did you find a different solution?
03-27-2012 11:18 AM
Have the same problem. (Non-System Disk, Press any key massage, then system boots normally)
It is because firware updater modyfied MBR. To recover the MBR you need to use System Recovery from Windows 7 installation dvd. There type in console: bootsect /nt60 C: /mbr