Jump to content
XPEnology Community

autumnhasfall3n

Rookie
  • Posts

    3
  • Joined

  • Last visited

autumnhasfall3n's Achievements

Newbie

Newbie (1/7)

1

Reputation

  1. So i gave up like 2 years ago, but i had a long weekend so i took another crack at moving from 5.1.7 to 6.2.3 and i did it!!!! This was actually really helpful. My bastard of a router at the time still decided to hide the thing, but hey i learned something about arp thats neat. Ended up using some network scanning utility, all worked out great. for the record you and i were having different problems. What happened to you was you accidentally downloaded the dsm update from the internet instead of manually installing it (in your defence i did this while trying to update). The internet versions are now beyond the bootloader, so if this does happen you can either wipe your storage disks, reset your usb and try again. OR follow this handy guide. Also for the people asking about 2.3.4, it doesnt work.
  2. If you happen to be trying to do this now using a recent version of system rescue cd. The Update files are all marked as hidden, you will only be able to see them with ls -a and more importantly deleting them requires a slightly different command rm -rf /mnt/SynoUpgradePackages becomes rm -rf /mnt/.SynoUpgradePackages they all get little dots. no idea why this is but hopefully i can save someone the half an hour it took me to figure out where the hell they were hiding.
  3. Hi, I've been troubleshooting for a while now and i've come to a dead end. I have had 6.1.7 running on an f2-220 for a good few years now, and figured i'd make the effort to update it to 6.2.x or whatever is newest and compatible. I was running a 1.02b loader i think. I have done a clean install following the processes described by both delavegagr and rcached using the 1.03b bios and the appropriate extra.lzma and the files from the .pat using the vid+pid+nic from my previous working config as well as both a fresh and reused serial i have reconfigured the bios to boot in legacy mode, as well as setting the boot os to "windows 7" From the screen it appears to be booting into the loader just fine, yet despite my best efforts i still cant detect my server on the network either through synology assistant, the web page, or arp -a and its ip. If there is something completely obvious I have overlooked pointing it out would be appreciated, thanks and regards
×
×
  • Create New...