Jump to content
XPEnology Community

sandisxxx

Member
  • Posts

    104
  • Joined

  • Last visited

Recent Profile Visitors

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

sandisxxx's Achievements

Advanced Member

Advanced Member (4/7)

4

Reputation

  1. Well, I am not about to migrate to Tinycire/Redpill/DSM7 just now. I am now seriously thinking of gettin 4 3TB WD Reds, + putting a 500GB SSD into the box for the ESXi OS and creating a RAID volume from all 4 HDDs and go full virtual. Or perhaps passthrough the HDDs directly to the DSM7 VM and make a Synology RAID on those. In that case I could just replace one failing disk with eventually no worries. While performing regular backups of the DSM7 config, I should be pretty much covered. So far, the system works just fine, the shares work OK, I can write to them, nothing seems to be down. But eventually, it will break and get even worse, but at that time, I should have my HDDs ready and can migrate to VM and DSM7.
  2. Hello Community. I am running a DS3615xs version 6.2.3 25426 on a HP Microserver Gen8 bare metal. I have 3 HDDs which are configured as standalone pools each. Menaing I have 3 pools that each utilize each disk alone. On Storage Pool 3 there is one bad sector on the corresponding disk. Seems that the volume is read only now, but data seems intact. I am now copying the data from the disk. All my packages are installed on a different pool. Have some concerns though: 1. The docker storage is located on the crashed pool and I cannot move it, since the pool is read only how to safely export the docker container I have there in order the system crashes or I installa new disk? 2. I do not know where the OS is located, I have tried to check that via SSH, but no clue. What happens if I remove the disk and it is the one that contains the system partition? Will xpenology even boot? I'd appreciate any good advice. Ideally to check where my OS is installed first. Then somehow override the Read only lock so I can move my Docker storage to other volume. Or perhaps I can take the disk out, clone it to a different disk and put it back? Or perhaps unmount the sdx device and rune e2fsck on it ?
  3. My DSM is back in the original state. I cannot express my thanks to IG-88 for his incredible advice. @phinemariatry to follow IG-88's reply here and you should be fine. In case you struggle I will try to help you as IG-88 helped me. Just PM me here and I will help you. Many MANY thanks to IG-88 for his knowledge and willingness. You do not see too many people like him nowadays. Cheers.
  4. Axel, I am following the advice by IG-88 now, you need some experience there, but it is followable. IG-88 is communicating with me and really does extreme good job. I will report how it all ended up with some details, that could help you as well. But there are some things you need to do, like create a linux USB etc etc, which you should be able to find elsewhere, how to do that. By the way in my case I have updated to 6.2.4 which does crash on the HP Micro Gen8 apparently, so the process basically is to revert to 6.2.3...
  5. Thanks for the valuable input, I will boot into a linux distro to check. Actually I am not really sure if I applied update 3 or 6.2.4. I will also check the C1e (but this is unlikely). I will read the article and come back. I still have the original USB though - would that help in any way? Is there a way how to tell what update I actually applied using the Linux bootable distro?
  6. Well there is another user having the same issue. Question is, what was wrong and more importantly, how to recover from the state?
  7. Hello, I have reported this in the Updates reporting section as well, if this is against the rules - please delete my post. If there is someone that can help - will be much appreciated. Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: Jun's Loader v1.03b DS3615XS - Using custom extra.lzma: No - Installation type: BAREMETAL - HP ProLiant MicroServer GEN8 Here are some of my details - please advice if you can: After applying this update, the system rebooted and it boots into synoboot, like normal. However the system is not visible in the network (checked also my DHCP if it got a different IP address by chance). I have tried to create a new USB from scratch. I used the same serial number in the grub.conf file. The system boots up, gets it's IP address from DHCP based on Reservation. Synology assistant can see the device, but the only option is to Recover it. Pressing recover reboots the machine and it is basically in the same state as before. There is no way how to use a different pat file. I have left all disks in the device. I have 3 disks, which each has it's own volume and shares on it. The first disk is used as the Synology primary disk, so I guess the configuration is located on the first disk. Also the first disk contains my Docker image. I have found a .dss backup file from July 2020, that could be perhaps used. Does anyone have an idea what to try to make the system back? Maybe disconnect the disks to try to make the DSM up again and then reconnect them and upload the .dss file with configuration? Thanks in advance for any advice. My guess here is that they removed the drivers for the Onboard NICs, as I see members that have the same system but with Intel NIC and no problem. So maybe also applying the extras.lzma would make sense?
  8. Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: Jun's Loader v1.03b DS3615XS - Using custom extra.lzma: No - Installation type: BAREMETAL - HP ProLiant MicroServer GEN8 Here are some of my details - please advice if you can: After applying this update, the system rebooted and it boots into synoboot, like normal. However the system is not visible in the network (checked also my DHCP if it got a different IP address by chance). I have tried to create a new USB from scratch. I used the same serial number in the grub.conf file. The system boots up, gets it's IP address from DHCP based on Reservation. Synology assistant can see the device, but the only option is to Recover it. Pressing recover reboots the machine and it is basically in the same state as before. There is no way how to use a different pat file. I have left all disks in the device. I have 3 disks, which each has it's own volume and shares on it. The first disk is used as the Synology primary disk, so I guess the configuration is located on the first disk. Also the first disk contains my Docker image. I have found a .dss backup file from July 2020, that could be perhaps used. Does anyone have an idea what to try to make the system back? Maybe disconnect the disks to try to make the DSM up again and then reconnect them and upload the .dss file with configuration? Thanks in advance for any advice. My guess here is that they removed the drivers for the Onboard NICs, as I see members that have the same system but with Intel NIC and no problem. So maybe also applying the extras.lzma would make sense?
  9. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: Jun's Loader v1.03b DS3615XS - Using custom extra.lzma: No - Installation type: BAREMETAL - HP ProLiant MicroServer GEN8 - Additional comment: Did not need FixSynoboot.sh, installed via Web GUI, reboot required
  10. Hello community. What if the output of my Xpenology (HP Microserver Gen8, bare metal, Juns loader 1.03b with no extra lzma, Version DS3615xs / 6.2.3 25426, no PCIE Network card, just the stock ones) ls /dev/synoboot* looks like this? /dev/synoboot /dev/synoboot1 /dev/synoboot2 /dev/synoboot3 Is it safe to install the normal way via the Control panel? Or the script has to be executed before? Thanks in advance.
  11. Thanks for great advice! Everything worked as expected. The 10 minutes when the box was not responding to ping took hours Hope this helps also others with same config. Gerat work!
  12. Found it: 1) Enable SSH and ssh into your DiskStation 2) Become root ( sudo -i ) 3) Make a mount point ( mkdir -p /tmp/mountMe ) 4) cd into /dev ( cd /dev ) 5) mount synoboot2 to your mount point ( mount -t vfat synoboot2 /tmp/mountMe ) Now I see the extra.lzma modified that has 4MiB in size so now I just replace the file with the original from 1.03b that has some 1,8MiB ? Then I use the web interface to manually install the DSM_DS3615xs_25426.pat? Please correct me if I am wrong.
  13. Can you please tell me how to overwrite the extra.lzma from the synoboot2 partition of the USB boot drive? I have tried to mount it but I got some error that I can not understand really.
×
×
  • Create New...