sbv3000

Moderators
  • Content count

    888
  • Joined

  • Last visited

  • Days Won

    8

sbv3000 last won the day on July 16

sbv3000 had the most liked content!

Community Reputation

50 Excellent

3 Followers

About sbv3000

  • Rank
    Guru

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. sbv3000

    Port multipliers - JMB322 - Gigabyte Motherboard.

    The testing I've done with 6.x and multipliers all work out the same, drive 1 seems ok, but any that are on other ports no show. I think its the same historical limitation of the 'syno bios'. Even my tests with the multiplers using the chipsets used in genuine Syno boxes dont work. I think your best option is a known compatible add on card, simpler and more chance of support from the forum if you need it.
  2. Glad it worked. You are correct about the spare drive not being needed for raid rebuild, thats why I say dont create a volume on it, avoids volume/raid naming issues. What this process does is to make a clean 'master' copy of DSM on the system partition of clean drive, using standard install processes (ie no need to mount ubuntu mdadm etc). DSM then finds 'corrupted' system parts on the other drives (because of the version mismatch) and in Storage Manager there should be the option to 'Repair System Partition' and when clicked warns to keep DRIVE 1 connected etc. On boot, the system looks for a 'good' version of DSM on the lowest sata channel drive, hence use sata 1 etc
  3. This is a variation of the 'Clean Drive' downgrade process I've described before in several threads 1) Disconnect your raid drives 2) Connect spare HDD to SATA port 1 3) Install DSM 6.x from fresh 1.02b loader, create admin user and server name matching live system, DONT create volume/raid. Update DSM to match your pre-beta version 4) Shutdown, reconnect raid drives to SATA ports 2-n 5) Boot, login, repair system partitions on raid, shutdown 6) Remove spare HDD and reconnect raid drives to SATA ports 1-n 7) Boot, repair packages etc My additional steps would be to power down the server between drive swaps and update DSM on the clean drive to the version matching the one running before crash.
  4. something that jumps out to me is the lack of IRQ resources. In the bios, disable all unnecessary devices; parallel port, sound chip, com2, (if present), additional USB controllers etc
  5. you might need to go the difficult path of attaching a serial port adapter to the onboard header.
  6. Com port redirection in bios advanced ?
  7. try an ubuntu live boot and identify the pci devices to cross check the exact drivers the nic is using vs the extra.lzma also try a serial console connection to check the boot log and see if there are any kernel panics/driver issues.
  8. try the clean drive process in this thread, adjusted for your virtual disks
  9. try a serial port/putty connection to check the full boot loader progress (if you mobo has a serial port). Also try a clean install on a spare hdd to check all your hardware. If thats all ok you could re-attach your raid drives together with the clean hdd and see if that repairs the dsm install on the raid
  10. sbv3000

    HW for Basic XPEnology Trial

    everything you list looks like it will work 'out of the box', just follow the standard tutorial
  11. Some thoughts 1) Its unlikely you will get help from Synology, unless its an issue migrating between their hardware 2) Check the drives for jumpers (normally near the power/data connection), as these are older drives there might be options to set various modes, eg speed, emulation 3) Try a setup with a drive that is found by the bios on sata channel 1, plus the other drives on 2-n 4) Try another (add on?) controller 5) Try IDE mode in the bios (XPE/DSM won't work with this, but it might help drive detection elimination) I hope you have a data backup as messing about as above could affect the array/data
  12. as you have <=12 drives then that is the standard 36xx config so no editing is normally necessary. suggest you check your drive enumeration in dsm, looks like you have 14 sata ports (6 onboard+8sas), so the two 'missing' ones might be higher than the 12 default, and your sataport edit is forcing it to work I would attach drives to internal sata 1-6 and check the physical port vs dsm storage manager drive number, then do the same for the channels on the sas controller. Once you know the first 9 channels use them.
  13. sbv3000

    DSM 6.1.x Loader

    So it looks like you have 14 drive channels (6+8) but 12 is the default unless syno info.conf is altered but somehow it looks like your sataport edit is fixing it until update. I would check and ensure your 9 drives are connected to the first 9 channels (6 onboard and 3 sas) but you will need to determine the drive numbers/channels in DSM. If your 9 drives are on the first 9 channels seen by DSM no config changes should be needed and no rebuilds on update
  14. If you updating your existing boot drive (via control panel or manual .pat) that would usually retain your customised sataportcfg. How are you doing your updates? Also, what controllers are 'seen' with the default sataportcfg? you may be changing it and dont need to.
  15. sbv3000

    DSM Server not listed under network

    Look in; Control Panel > File Services > SMB > Advanced Settings (button) You can set SMB versions, WINS, master browser etc.