Recent content by emanuensis

  1. E

    cobbling a compute and storage server from a Symatec 5000 with S2600GZ MB

    i finished the connector mentioned in this Intel forum thread SSD SATA power cable for S2600GZ (serious smoke test caveat though: reverse the polarities and/or use a voltmeter to know the true value of the MB's socket). With that power, using the one of an internal SATA, i was able to boot WX...
  2. E

    cobbling a compute and storage server from a Symatec 5000 with S2600GZ MB

    AFAICT the MB's PSU only produces 12v power (see http://www.intel.com/content/dam/support/us/en/documents/motherboards/server/sb/s2600gzgl_tps_r2_4.pdf p82) so any 5v or 3v power must come from voltage converters on the MB or whatever board the 12v supply is connected to. i just received this...
  3. E

    cobbling a compute and storage server from a Symatec 5000 with S2600GZ MB

    i did go through all the entries in the BIOS. W10 still gives "The drive where Windows is stored is locked, unlock it and try again" when the boot drive is placed in a SATA/SAS bay:-( Perhaps if anyone else owns a s2600(z/l) board they can say what the entry is to change...? Still howls as...
  4. E

    cobbling a compute and storage server from a Symatec 5000 with S2600GZ MB

    @Patrick Yeah super weirdo. Never heard of a drive being forced read only before. The BIOS has lots of settings ... but so far i have not found any that makes drives RO! i drank Champagne when i finally got WX going, even if only through USB!
  5. E

    cobbling a compute and storage server from a Symatec 5000 with S2600GZ MB

    i recently got a barebones Symantec 5000 (SYM5000 2U Server Chassis w/ Intel S2600G Dual 2011 Socket Motherboard 2x PSU) just adding 2xE5-2670's and 64GB ram. i managed to get it to boot into Windows 10! Unfortunately in getting there, i still have a lot of unresolved problems. i see several...