theimpimp

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About theimpimp

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Were you using SHR? Is it always the sda1 sdb1 sdc1 partitions? Sent from my XT1092 using Tapatalk
  2. Ok so I am continuing my quest to recover my NAS as I hope you'll continue with me along the ride... BIOS is all correctly set up and normal. I thought I'd try both a new USB and the Force Install / Reinstall options - The new USB has improved things a little bit - now it boots reliably to the kernel and I can see the box in Synology Assistant - I also can choose to recover my disks and I can choose a pat file - the new change now is that whenever I choose a PAT file it complains that "Failed to install the file. The file is probably corrupted (13)" so naturally I re-downloaded the file from the OP and tried again, and again. I then thought fine, I'll resort to a clean install instead of a migration - same issue. I've tried all 4 of the options in the bootloader - normal, Reinstall, Force Install and even AMD on my intel Gen8 microserver and every single time it complains the pat file is corrupted. Now I'm assuming that the DSM partition has been wiped, so how can I overcome this wonderful obstacle? I'm feeling like at the moment even a clean install wouldn't work. Is there a chance that a 6.1 install made its way on there and is preventing the "downgrade"? I am literally trying to think of anything now!
  3. Does anyone have any ideas? I've tried searching for other people with the "recoverable" loop issue but they seem to either have solved it themselves and not posted how or it was easy solutions like VID/PID mismatch - could it be worth trying a diff USB stick? I figure it has to be an issue with the update applied though as it can be found via the Synology Assistant... Stumped! Is there anyway of "Reapplying" the manual update pat file in case it was a bad upload or somesuch? Is there a way to wipe the DSM update but retain the data and try again? Any thoughts welcome & very much appreciated! Make sure Bios is configured properly to start with and that all required info on grub file is correct. Careful with typos. Reboot your router before starting an install to make sure it's running fresh. You can start with a re-install or force install see if that fixes anything. Otherwise you can wipe the DSM partition with a live ubuntu USB drive then install DSM again. All settings and apps will be gone obviously but your data is on a different partition so it should be safe. Since you have 4 drives the DSM partitions are normally these: dev/sda1, dev/sdb1, dev/sdc1, and dev/sdd1. Here is a tutorial I made on how to access the partitions in case you want to make a backup priori doing anything just in case: https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ I think there were a few gen8 questions in the original Jun loader thread. Also check there. Sent while on the move Thank you to both of you for this, very much appreciated! Will come back and post what happened in a bit in case anyone else has the same issues. Sent from my Android phone, so likely full of hilarious typos....
  4. Does anyone have any ideas? I've tried searching for other people with the "recoverable" loop issue but they seem to either have solved it themselves and not posted how or it was easy solutions like VID/PID mismatch - could it be worth trying a diff USB stick? I figure it has to be an issue with the update applied though as it can be found via the Synology Assistant... Stumped! Is there anyway of "Reapplying" the manual update pat file in case it was a bad upload or somesuch? Is there a way to wipe the DSM update but retain the data and try again? Any thoughts welcome & very much appreciated!
  5. I'm hoping someone can help me too . I had an HP Gen8 Microserver running 5.2 for a while now. It is a “stock” Gen8 Microserver running nothing unusual or out of the ordinary. I finally got fed up of the limits of 5.X and thought I’d make the jump, especially with this wonderfully helpful tutorial and several reports of Gen8 Microservers operating correctly. The machine is fully loaded, with 4 drives set up in SHR and a SSD acting as a cache disk. I followed all the steps, and all was going fine and saw that I was upgrading - however upon final reboot, the Microserver seems to have gone into a loop showing as “recoverable” and always rebooting to the “recoverable" state, but never successfully booting to DSM. I have my router giving out a fixed IP to the MAC address of the server, and correctly copied by VID, PID, MAC1, MAC2 and also the serial from my old 5.2 install across. Synology Assistant shows it as being on Version 6.0.2-8451 currently. If I choose to 'recover' the DSM install, the server reboots, and then cannot boot to the USB and has to be powered off, and then powered on again before it will successfully boot to the USB again. At this point it returns to the "recoverable" status and the whole thing starts again. I’d like to get 6.X running and I assume that going back to 5.2 isn’t possible (I do have my old USB for 5.2 here though safe and sound as per the instructions). Can anyone help? I’d prefer to not have to get ruthless and try wiping and starting again as while I have a backup of the data, this should be working correctly! (not blaming the instructions AT ALL or all the hard work that has gone into this - just makes no sense to me! and the tinkerer in me wants it to work!) Can anyone suggest a way forwards? I miss my home server massively already! Many thanks in advance. Let me know if you need more data and I can see what I can do!
  6. theimpimp

    Printer Issues

    Thanks, I'll have a dig around and post it I find anything useful. Currently resorted to carrying the laptop back to the printer and plugging it in like some luddite...!
  7. theimpimp

    Printer Issues

    Damn I was hoping you wouldn't say that! It's a device supported on the Synology pages - any idea why it wouldn't work in synology itself? Is there any way I can update/ change the synology provided drivers? I'll have to see if I can print from the app or from a windows box.... so frustrating - makes me tempted to go to a proper OS just to avoid these issues sometimes... but I love DSM!
  8. theimpimp

    Printer Issues

    Oh and the setup you have - exactly the same as mine... :-/ Sent from my XT1092 using Tapatalk
  9. theimpimp

    Printer Issues

    How did you manually install this? I'm printing from OSX and from google cloud print from various other devices - uninstalling it and reinstalling it didn't work Can't even get a test print out of it!
  10. theimpimp

    Printer Issues

    Hi billat29 Excellent, glad it is working for someone! I'm actually connected wired and am still having the same issue. Any other thoughts? I'm stumped as the box can see it but just refuses to print. Any sense in "uninstalling" the printer and reinstalling? Cheers. Sent from my XT1092 using Tapatalk
  11. theimpimp

    Printer Issues

    Hi Brantje No no, good question always good to check the obvious! Yes it is shared for windows, apple and via Google Cloud Print. None of them work over the network, although all can see the printer - the printer itself just doesn't print except when directly connected to a pc/mac. It is listed as a supported printer on Synology's website...
  12. theimpimp

    Printer Issues

    Hi all First post here - been lurking and learning as much as I can up until now! I've got XPEnology running on a gen8 microserver bare metal - works wonderfully, thank you so much! currently having fun trying to use docker to run a Home Assistant instance... docker could be so powerful on this box! One small issue though - I've got a Samsung ML-1660 B&W laser printer, which while recognised by the system, won't actually print anything. The printer works fine when directly connected to a pc - anyone got any suggestions? I've had issues with a USB wireless card on this machine in the past too (replaced it with a wire to a wireless bridge instead) so wondering if it has anything to do with that? Any assistance greatly appreciated!