Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About GodZone

  • Rank
  1. Hmm just copied my backup to a USB drive on my Mac and it showed the following /dev/disk4 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *1.0 GB disk4 1: Linux ⁨⁩ 1.0 GB disk4s1 Mounting this on a linux VM, it has everything in the one partition which has an ext2 file system (fedora)9e61c3f0-6b13-4a06-ac2c-b28ee43f38fc: la total 2304 drwxrwxrwx. 10 root root 4096 Jan 17 17:
  2. That looks pretty much identical to what I have so I am not sure what to try next. And yes I did swap the VID/PID but that mad no difference. It doesnt look like the firmware loader is starting grub at all. Disk /dev/sdv: 979.3 MiB, 1026822144 bytes, 2005512 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AFB38D11-BCEA-4409-B348-F4FEEE602114 Device Start End Sectors Size Type /dev/sdv1 2048 32
  3. Swapping the values didn't achieve anything. I still get a blank screen. Its interesting that during the boot of the external USB, there are messages to say that sdv1 and 2 may be corrupt as the volume was not properly unmounted. The filesystem on the internal is FAT-fs which I assume to be correct. I have a vague recollection that the original internal usb oly had a single partition, I am starting to think I need to copy it to another stick and have a closer look.
  4. On my px4, that socket is empty as per the photo. So I am still asumming it is a chip. Trying to read the tiny writing on the chips is pretty hard so I havent managed to find it. sudo lsusb -icu Password: |__usb2 1d6b:0002:0310 09 2.00 480MBit/s 0mA 1IF (ehci_hcd 0000:00:1d.7) hub |__2-7 05dc:a761:1100 00 2.00 480MBit/s 100mA 1IF (Lexar JD FireFly R98A675RYBQ3BJAG5YX1) 2-7:1.0 (IF) 08:06:50 2EPs () usb-storage host1 (sdu) |__usb3 1d6b:0001:0310 09 1.10 12MBit/s 0mA 1IF (uhci_hcd 0000:00:1a.0) hub |__3-1
  5. Hmm, not getting very far. I have dd'ed the individual partitions to the onboard USB, mounted /dev/sdv1 and edited the grub.cfg file replacing the VID and PID values with those above. Not able to boot from it, I dont get the grub screen on the serial console. I can still boot using the external USB and as yet I havent tried swapping the VID and PID values. I get a 'Prepare to Boot to OS', but then a blank screen.
  6. The onboard one is; P: Vendor=1307 ProdID=0165 Rev= 1.00 S: Manufacturer=USBest Technology S: Product=USB Mass Storage Device The only I used to boot from i.e. the XPenology loader is; P: Vendor=05dc ProdID=a761 Rev=11.00 S: Manufacturer=Lexar S: Product=JD FireFly
  7. I successfully upgraded to Release 3 after adding the Fixup script and am now up to trying to get booting sorted out. I cant find the onboard USB so I am assuming its just a chip on the mother board (hence not removable). It gets identified during the boot as sdv 'Ut165 USB Flash Disk'. I have dd'ed the content to an image file using 'dd if=/dev/sdv of=/PX4.img' but now I am a bit confused. During the boot, the kernel found my usb stick as sdu 'Lexar JD FireFly 1100 PQ' but once DSM was up, there are no device files for it so just dd from it isnt an option. I am also now con
  8. Please post your experience with the USB, I have had to put my project on hold for the time being as other stuff has risen to the top of the ToDo pile
  9. Did you overwrite the internal USB ? I haven't yet
  10. For the time being I'm going to just run with the 2GB of RAM. I have disabled everything I am not intending to use. Is it safe to install Update 3? The Updates screen says its available so it wasnt installed automatically. My biggest query is booting. I would really like to be able to just power it on and have it boot from the internal USB drive. I can ssh to the box and that drive would appear to have the IOMega software still on it. I am tempted to format that drive and duplicate the XPenology USB drive to it but have no idea whether that is a sensible thing to do or not. I thin
  11. I just booted the PX4 again intending to do some more diagnostics and the system booted, did a lot of updates (to the drivers I believe) and now I can log in via the web and have completed the setup. The PX4 only has 2Gb of RAM so I had OOM busy killing stuff off but have disabled stuff I dont use and it looks very promising.
  12. I think I have missed something, I think I somehow need to make the installed version of xpenology use the serial console AND use the drivers you have packaged but I am nor sure how I go about that
  13. Much closer, using your extra.lzma allowed the installer to find the disk and I went ahead and did a manual install of DSM_DS3615xs_25426.pat which I think is what I should be using but that OS will not boot, I just get a blank screen on the console.
  14. Hmm, looks like I might be out of luck with XPenology on this hardware then. putty.log
  15. Some progress, the load now boots 1.03b and I can find the NAS over the network but when I try to connect, it says there are no disks. I had the original PX4 configured with a 3 disk RAID-5 + spare, I am hoping I can possible retrieve stuff off the RAID volume so at the stage I only put the spare into the 1st disk position. But it isnt seen. Can I login at the Diskstation logn: prompt? If so what are the credentials? I'd like to see what the kernel actual sees as devices.