Jump to content
XPEnology Community

wedgehog

Rookie
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

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

wedgehog's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Hi IG, I'm sorry you have lost me, First of all yes I can see in my flash image there is a vendor section and it has the S/n and check sum in it, also when you extract the files from a .PAT they are not included as they are specific for the machine and have to be added. You say because mine is an Arm CPU I will not be able to boot with a bootloader from "Here" Do you mean from this forum? If that's the case I did not intend to. You can see from the top of my log that I am using Bus Pirate, and I just press the esc key after boot and access the Uboot Menu, that's where I was getting the command "Bootm" which should boot linux from the memory if I was able to load Zimage directly to another memory location to avoid the "Unable to write to Block 9,0" problem. Well that was my plan but I may be talking rubish, I am no where as good at this as you and I need things explained clearly, you speak of the first and second partition? Are you speaking of the disk structure created in memory which is refered to as the ramdisk in the log? or are you refering to different locations in the flash file? So just to be clear, I downloaded an older DSM file from Synology I extracted it and created a flash file placing Uboot (Redboot) at 00 and Zimage and RD.gz at exactly the same locations as they were in the original flash which I got when I first read the chip, I presumed that it was Zimage which got corrupted when the power went off. I then added the Vendor and serial number stuff at exactly the same position as they were in, in the original flash image. All I could do to get the offsets was to look at the original flash read from the chip with a hex editor and build mine to match. Now having said that, the files with the exeption of Uboot were different sizes in the older image, I presumed that as long as their start was at the same offsets as the original that wouldn't matter? Pleas could you confirm for me, in the flash memory image, the 64k chip, is the file order Uboot, Zimage, RD.gz than the Vendor and s/n stuff, I am worried that maybe zimae should have been the second file, but as you confirmed the log does say it was initially loading ok from my flash file. To be honest I doubt I am good enough to resurect this NAS, but I am very determined.
  2. Hi Ig, thanks for your help. I came here because I was told on another forum that you guys here were clever and would be able to help. It has been some time since I posted and during the wait I thought of what you said so I downloaded an older PAT file and constructed a new flash image, I am fairly sure I got it correct as It obviously runs Uboot as that's the first in the file but later in the log I can see it says it has fond the image but cannot write it to memory, this fail line end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0) I am not good enough to know exactly what that means, I am guessing it's trying to write to a certain part of memory to creat the linux directory tree and can't, I was thinking of using the commands in Uboot to copy Zimage to memory at another location and then using Bootm to run it but I don't know exactly how to write the command or what memory start and finish addresses to use. While I have over 40 years experience as an electronics engineer I am no coder, Please could you help me with this? PS: I did post in the Synology forum at the same time I posted here and no one has answered me there either. I also added the log just in case you have time to read it. Bob putty.log
  3. No one interested in helping me?
  4. DSFuchs, I have contacted you in a PM Please respond
  5. Hi Guys, my apologies if I am in the wrong forum. I had the house power go off during an update, I have had a look at the serial log during startup and it looks like Uboot and RD are ok, I get pages of sensible instructions until it comes to it loading Zimage and it says it's corrupt, I removed the flash memory and read the contents and saved it with a view to re constructing the file, but I find Synology have decided to encrypt the .PAT files to prevent us from repairing our equipment! Please could someone give me a copy of their flash chip for the DS418, dosn't matter which version of DSM as the board should boot with no drives in it and say please insert a drive, I know the drives are ok as I put them in my DS920 and it reds them fine and all the data is ok, This is still a £350.00 or more machine so I would really like to save it Once again please can anyone give me a zip containing a DS418 flash image with the s/n and mac removed if you don't trust me not to use it. Or If no one want's to help me with a copy of the flash I would be happy with a list of the file Offsets for Zimage and RD.bin in any of the images below 711 (ones we can extract) I would need to know which 418 DSM it is from as I think they are all different as the file sizes vary. Please Bob
  6. Hi Guys, first post, I am pulling my hair out with this. I have had Rutorrent working on my synology for over a year, suddenly it won't work after your firmware updates so I decided to do a complete re install, Uninstalled webstation and apache servers and PHP etc. Installed Webstation, then installed Apache 2.4 but it does not show in webstation, Installed Apache 2.2 that doesn't show as installed in Webstation either so I can't select either of them in the general settings page. Exactly the same for the PHP niether of them show as installed in webststion, but they are all running?
×
×
  • Create New...