• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About fitman

  • Rank

Recent Profile Visitors

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

  1. Also use --force, no luck! Do you think it is certified as dead
  2. Having had done couple of mdadm options, such as --examine, --assemble, I still cannot get one of RAID on line. Now, I have 2 hard disks. Here are the outputs: 1. cat /proc/mdstat, and it seem it miss another RAID device /dev/md2 Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md1 : active raid1 sda2[0] sdb2[1] 2097088 blocks [12/2] [UU__________] md0 : active raid1 sda1[0](E) 2490176 blocks [12/1] [E___________] unused devices: <none> 2. fdisk -l /dev/sda /dev/sdb Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168
  3. Do you think it is caused by the bad hard disks? Btw, my backup is not latest
  4. Hi there, My Xpenology NAS stop to share files suddenly. Having reboot the NAS, the RAID 1 group and volume are disappeared. I can also check there are some bad sector errors in 2 drives in the event log, and 2 drives are in "Unused Disks" status One of the drive status is in "initialized", and other is in "warning" Can anyone advise how to recover the data? Million thanks. Louie
  5. fitman

    DSM 6.2 Loader

    Outcome of the installation/update: SUCCESSFUL for 6.2u2 - DSM version prior update: New installation - Loader version and model: JUN'S LOADER v1.03b - DS3617 - Using custom extra.lzma: NO - Installation type: VMware Fusion 10.1 - Additional comments: Jun's loader img convert into vmdk as SATA drive, legacy boot,
  6. just solved and it seem it is caused by the SSD cache setup
  7. Hi there, Before update to DSM 6.1.7, it seem it do not have critical issue as searched from this forum. However, I try to update my existing DSM 6.1.6 to 6.17 and it is bricked. I can see the bootable screen, but, I cannot access it thru web or synology assistance. I try to reboot/reinstall, but, it seem it cannot be helped. Can anyone provide any guidance to recover it as well as the data? Here is my config: - ds3617xs on baremetal (J3455) - Loader is 1.0.2-b2 - Running SATA with 4 disks using Synology RAID(SHR)
  8. fitman

    DSM 6.1.x Loader

    Bare-metal ds3617xs from 6.1.2 to 6.1.3 using 1.02b loader, thx, Jun, work like a charm... no problem!!!
  9. fitman

    DSM 6.1.x Loader

    I use this tool
  10. fitman

    DSM 6.1.x Loader

    Yes, it fixed for baremetal... 1st boot, it ask to "recover" the disk, then reboot.. and can be accessed the GUI. thx
  11. fitman

    DSM 6.1.x Loader

    @jun, is it 1.02b? It seem it cannot boot up for ds3617 in baremetal, always said migratable. Even, I use it for new install, it still got the same issue. Use back 1.02a2, no problem on clean installation, 6.11 or 6.12
  12. fitman

    DSM 6.1.x Loader

    How to copy kernel modules if I am using baremetal version?
  13. fitman

    DSM 6.1.x Loader

    Yes, I am doing in same way in baremetal... also cannot access....
  14. fitman

    DSM 6.1.x Loader

    DS3617xs 6.1.1-15101 u4 upgrade from u2 and it is working fine for bare-metal!!
  15. fitman

    DSM 6.1.x Loader

    Finally, I can install DSM 6.1.1 using ds3617xs on bare-metal. Here is my installation procedure: 1. Using v1.02a2 and create the boot image with correct SN and MAC1 onto a USB drive 2. Only install 2 hard disk (I have 4 disks for RAID5) 3. Use and install thru web with default value 4. Wait for installation and reboot again 5. Install 6.1.1 update2 and wait for reboot 6. Install the remain 2 disks, and it is working now... Good luck to all...