• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About volospin

  • Rank
    Junior Member
  1. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 (bricked) - Loader version and model: Jun'S Loader v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen7 N54L - Additional hardware: -- Orico 1106ss CDROM to 3.5inch HDD drive bay -- IBM® 49Y4240 (Intel 82580) quad RJ-45 ports -- NEC D720201 quad USB 3.0 (optional SATA supply power) Recovery upgrade install
  2. Hi guys, Thanks for this thread. I would like to share experience which is a little bid different. The story is that my HP N54L 6.2.1-23824 suddenly cannot be found on the network one day. Then I build another 1.03b DS3615xs USB stick, unplug all FIVE drives and insert an empty one (called A) at port 1. Installed and upgrade to 6.2.3-25426, then plug the old 2 3 4 5, got a message saying CRASH / DEGRADED. Then I click Repair which works very quick, then I shutdown and unplug A and plug 1, boot with the ANOTHER USB stick. Then I got the Welcome
  3. Hi pocopico, I am trying to use the loader on HP T610 (and T610P which is the same hardware) and it takes a long time to search in "Synology Assistant" (it can identify and add tg3 extension during build) When I try to install the PAT file, it say that the hard drive (2) is having error. It identified SATAPortMap = "3" and DiskIdxMap = "00" Currently it is running 6.1.7 with 1.02b DS3615xs. Can you give me some advise? tc@box:~$ lspci -nnq 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 14h Processor Roo
  4. I have not find my answer after some searching. Can the USB stick be unplug after DSM boot?
  5. I finally get both HP T610 and HP T610P to installed with DSM 6.1 and see all the available packages. I used the Unknown 64MB USB on HP T610 and CBM 1GB USB on HP T610P. I start thinking that the Buffalo 1GB USB is the reason I cannot get things through. I used to use another Buffalo 1GB USB in my HP N54L for like a month or two and recently it just stop working. I don't know why but that Buffalo 1GB USB is SLC USB and should last very long. Now I think I will start using the Toshiba 2GB USB as the loader. I start thinking the reason of no pac
  6. Well, let me list my steps... I boot System Rescue 9.0.1 USB to memory then unplug the USB then insert the USB with the img files then insert the target USB I use the following three USBs: ID 1221:3234 (Unknown, Red) ID 0204:6025 (CBM2000, EagleTec) ID 0411:0098 (Black, Buffalo) Every time I just insert one of them then dd if="the target img file" of=/dev/sdb (usually but double check before) mount /dev/sdb1 /mnt/sdb nano grub/grub.cfg then modify five lines set vid=0x0204 set pid=0x6025 set sn=1430LWN123456 (sample)
  7. I did copy the BIOS configuration from T610 to T610P but it does not seems to change anything. I still stuck with the same error message: 1) DS3617xs -> pat file corrupted or need to use some version or later (any files does not work) 2) DS3615xs -> Package Center shows nothing except file station and universal search. 3) Redpill -> SATAmap issue
  8. Somehow the T610P 1.20 BIOS behavior is different from T610 1.20 BIOS but it should not be. Now I installed 6.1.7 update 3 with Jun's 1.02b DS3615xs on T610P but having trouble will "All packages installed" while I only got several default ones and no others to choose from except SynoCommunity (which I added). I tried Redpill Tinycore but still got the SATAMAP issue. No matter I tried Jun's default or MBR version, I still cannot get pass 6.1.7 on T610P. But I did get to 6.2.3 on T610. Strange feeling... I think I need to reinstall again on T61
  9. This time it is interesting though. With T610, I get a flashing cursor with EFI 1.03b With T610P, it boot all the way with EFI 1.03b Strange difference same result
  10. Well, I stop HP T610 project for now since I need to fix my T610P with OMV. I want to apply my experience on T610 to T610P but the experience does not help. I updated the T610P to 1.20 K30 firmware same as the T610. But it seems my T610P likes EFI boot more than T610 did. T610 uses EFI 1.02b then MBR 1.03b but T610P fails on all ground. Well, stay tune while I try to get 6.2.3 working on T610P. Update~ I used 3617xs 1.02b and successfully installed 6.1 and then upgrade to 6.1.7 but when I shutdown and insert 3617xs 1.03b USB,
  11. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 - Loader version and model: Jun's Loader v1.03b - DS3615xs MBR mod - Using custom extra.lzma: No - Installation type: Baremetal - HP T610 - Additional comments: Disable EFI boot
  12. Breakthrough and big thanks IG-88 I downloaded the DS3615xs 1.03b MBR mod -> dd to USB and disable the HP T610 boot the EFI DSM is now upgraded to 6.2.3 25426 Update 3 Next step is fixing the satamap issue with RedPill TinyCore 6.2.4 and / or 7.0.1
  13. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 3 - Loader version and model: Jun'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: No - Installation type: Baremetal - HP T610 - Additional comments: None
  14. Sure, I tried booting under legacy and it just give me a flashing cursor with nothing further.
  15. I tried replace the extra.lzma for loader 1.03b ds3615 DSM 6.2.3 v0.12.1_test to try to boot T610 with 1.03b but failed to find in network. I think I will use ds3617 1.02b and 1.03b stock again. then I will use the Redpill Tinycore to tackle the sata issue to see if I can do 7.0.1. after these experience I will build a fresh HP N54L and might find it easier. Still learning, thank you, IG-88