My Passport Wireless Pro - System Recovery or Hard Drive replacement

Ane news about fixing issue?
Can I buy MPWP + SDSSDA-960GB-G26 instead of SDSSDHII-1T00-G25?

Can I use this workflow:
put SD card and attach USB SSD and copy files from SD to USB SSD with phone via wifi?

Successfully upgraded MPWP 3TB with 512GB SSD

Hi guys,

thanks to all for all information you have posted here, based on them and after a few trials and stucks I have managed to convert MPWP 3TB to MPW SSD with Sandisk X600 512GB. My steps are following, and some of them may be unnecessary:

  1. reset MPWP via web UI
  2. take 3TB drive out and connect to virtualbox linux machine. There I realized the drive has total 5860533168 sectors and last 8457136 are not used (there are all those hidden partitions)
  3. connect new blank SSD X600 512GB to linux (I have bought this model because someone here had success with it), create GPT, create FAT32 primary partition, leave 8457136 sectors at the end (orginal disk has 190MB EFI partition in the beginning, that is not needed)
  4. dd 8457136 sectors from old drive to new (careful here, with dd you can mess things up easily and I’m not sure if this step is necessary)
  5. connect new ssd to windows and format fat32 partition to exfat (parted I have does not support exfat)
  6. put SSD to MPWP, insert SD with firmware MyPassportWirelessGen2_1.04.17.bin in update folder and plug power (not from PC)
  7. turn on MPWP and immediately hold SD button for 5 seconds (I forgot this many times and ended up with full led flashing)
  8. after several minutes disk and wifi led both lit on and there were both wifi ready to connect (password is last 8 digit from new SSD drive SN, don’t forgot to note it)
  9. setup the drive via web UI, but first it throws error during Plex install and in the main UI there was strange disk size and UI says it is MPW SSD 256GB and there was NAS bug (disk not writable via network)
    I tried apply chmod and chown to /media/sdb1, but it didn’t help with NAS bug, but maybe it also played its role.
  10. I was quite frustrated at this moment, but at last I did System reset via web UI as a last resort before ordering UART and Voila! After that I have MPW SSD 512GB fully functional.

Question is if it was worth all the time invested, but I’m satisfied now and also I have learned lot of things about linux thanks to this :smiley:

2 Likes

Hi Divovlas, can you upload image from system partition from your MPWP?

mi try to repair my MPWP but i need system partitions

Yes, you can get it here https://www.dropbox.com/s/bm1t4fpxh75nv99/wdmpwp.7z?dl=0

Thank you, please help me - how to restore from your image? I’m nub in linux

Me too, so no guaranties :slight_smile: Reading about dd command will help. As I understood, this command is able to copy anything to anywhere, so there can be severe causalities when not used properly, like destroyed boot sectors, partition tables or filesystems. You have been warned.
These MPWP system partitions are not visible to classic partition programs - as they are marked as deleted/hidden. So this is byte to byte copy of disk sectors after the regular partition for data.

dd if=image_file of=/dev/sdx bs=512 seek=write_at_sector count=8457136

sdx = new disk (sda, sdb, sdc, …)
write_at_sector = total new disk sectors - 8457136

from the beginning of the disk to (write_at_sector -1) sector there is a place for regular exfat or NTFS data partition

Thank you so much, but repair my MPWP is fail

?hbj

U-Boot 2012.07 (Dec 17 2015 - 01:19:14)

CPU : Cortex-A7 dual core
Board: Realtek QA Board
DRAM: 512 MiB
Watchdog: Disabled
Cache: Enabled
Non-Cache Region: 1 MB@0x07900000
nor flash id [0x00c22017]
sector 256k en: 0
sector 64k en: 1
sector 32k en: 0
sector 4k en: 0
page_program : 1
max capacity : 0x00800000
spi type name : MX 64Mbit
Factory: NOR
Factory: pp:0, seq#:0x2, size:0x200
get_bootparam:
Factory RO: NOR
[ENV] read_env from factory failed
[ENV] Using default environment variables

In: serial
Out: serial
Err: serial
Net: Hit Esc or Tab key to enter console mode or rescue linux: 0
[PMX] : GPIO check…
[PMX] : Get GPIO 18 = 0
[PMX] : Press battery status buttom, go into recovery mode…
[PMX] : prepare recovery config…
(Re)start USB…
USB0: USB EHCI 1.00
scanning bus 0 for devices… 1 USB Device(s) found
scanning usb for storage devices… 0 Storage Device(s) found

1: Hub, USB Revision 2.0

  • u-boot EHCI Host Controller
  • Class: Hub
  • PacketSize: 64 Configurations: 1
  • Vendor: 0x0000 Product 0x0000 Version 1.0
    Configuration: 1
    • Interfaces: 1 Self Powered 0mA
      Interface: 0
      • Alternate Setting 0, Endpoints: 1
      • Class Hub
      • Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

** Invalid boot device **
[PMX] : recovery fail
Load bootcode2
*** header magic_tag 0xbeef1195
*** header secue_mode 0x00000001
*** header data size 0x00052ca0
*** header entry addr 0x01400000

hash 1(base=0x08000000)
000 : fa aa 84 bc 3c a9 39 c7 69 1b e8 42 86 7b 53 33
010 : d7 47 6b fc e7 72 30 08 cc 08 a4 d0 05 56 e6 8f

hash 2(base=0x01452c80)
000 : fa aa 84 bc 3c a9 39 c7 69 1b e8 42 86 7b 53 33
010 : d7 47 6b fc e7 72 30 08 cc 08 a4 d0 05 56 e6 8f
Start bootcode2 at 0x01400000 …

U-Boot 2012.07 (Dec 19 2016 - 15:36:21)

CPU : Cortex-A7 dual core
Board: Realtek QA Board
[WARNING] TLB was overlaped with kernel. (addr: 0x014b0000)
DRAM: 512 MiB
Watchdog: Disabled
Cache: Enabled
Non-Cache Region: 1 MB@0x07900000
nor flash id [0x00c22017]
sector 256k en: 0
sector 64k en: 1
sector 32k en: 0
sector 4k en: 0
page_program : 1
max capacity : 0x00800000
spi type name : MX 64Mbit
Factory: NOR
Factory: pp:0, seq#:0x2, size:0x200
get_bootparam:
Factory RO: NOR
[ENV] read_env from factory failed
[ENV] Using default environment variables

In: serial
Out: serial
Err: serial
Net: Hit Esc or Tab key to enter console mode or rescue linux: 0
[PMX] : GPIO check…
[PMX] : Get GPIO 18 = 0
[PMX] : Press battery status buttom, go into recovery mode…
Firmware Version: β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’
FWtable CheckSum error: fwtable_crc32[6a3b8a21], fwtable.checksum[ffffffff]
[PMX] : recovery fail
[PMX] : prepare recovery config…
(Re)start USB…
USB0: Realtek-ehci: init hccr 18020000 and hcor 18020020 hc_length 32
RTK USB3 phy init
No power optimization available
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices… Unknown request , typeReq = 0x200c
2 USB Device(s) found
scanning usb for storage devices… 4 Storage Device(s) found

1: Hub, USB Revision 3.0

  • u-boot XHCI Host Controller
  • Class: Hub
  • PacketSize: 9 Configurations: 1
  • Vendor: 0x0000 Product 0x0000 Version 1.0
    Configuration: 1
    • Interfaces: 1 Self Powered 0mA
      Interface: 0
      • Alternate Setting 0, Endpoints: 1
      • Class Hub
      • Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Mass Storage, USB Revision 3.0

  • Western Digital My Passport Wireless 533330434A394346333335313739
  • Class: (from Interface) Mass Storage
  • PacketSize: 9 Configurations: 1
  • Vendor: 0x1058 Product 0x25af Version 16.6
    Configuration: 1
    • Interfaces: 1 Bus Powered 224mA
      Interface: 0
      • Alternate Setting 0, Endpoints: 2
      • Class Mass Storage, Transp. SCSI, Bulk only
      • Endpoint 1 In Bulk MaxPacket 1024
      • Endpoint 2 Out Bulk MaxPacket 1024

** Partition 1 on device 2 is not FAT filesystem **

** Unable to use usb 2:1 for fatload **
[PMX] : recovery fail
Firmware Version: β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’
FWtable CheckSum error: fwtable_crc32[6a3b8a21], fwtable.checksum[ffffffff]
[PMX] : prepare firmware form USB fail
[PMX] : prepare normal firemware config…
** Partition 1 on device 2 is not FAT filesystem **

** Unable to use usb 2:1 for fatload **
[PMX] : prepare firmware form USB fail
Firmware Version: β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’β–’
FWtable CheckSum error: fwtable_crc32[6a3b8a21], fwtable.checksum[ffffffff]
[PMX] : recovery fail
[PMX] : prepare recovery config…
** Partition 1 on device 2 is not FAT filesystem **

** Unable to use usb 2:1 for fatload **
[PMX] : recovery fail
[PMX] : Enter RTK recovery proceduree…
[PMX] : prepare recovery config…
** Partition 1 on device 2 is not FAT filesystem **

** Unable to use usb 2:1 for fatload **
[PMX] : recovery fail
Enter console mode, disable watchdog …

Lot of " Partition 1 on device 2 is not FAT filesystem" errors - what format is your data partition? And SD card? SD card should be formated to FAT32

Of course, i try to format Data partition to exFat, NTFS, Fat32. EXT4, try to use SD with FAT and FAT32, but recovery doesn’t see fat partitions.
In recovery via UART and Putty has a command usb - i try to usb part, but with any connected HDD i see
that disk have a 1tb ( i try ssd 256) and have a partitions 1g 1g 2g - but ssd hasn’t this partitions.

Does anyone have a sense of whether the method described above (by Divovlas) works with other capacities of SSD in the x600 line? As in, the 1TB version of the x600?

It depends on if it’s detected or not… if it’s detected, the process should work fine… I had an issue with a Samsung SSD not being detected for some reason. Sadly, before I was able to test a modified script that wrote a lot of debug info to the SD card, I lost it and I didn’t have a backup on my nas. :’(

Always remember to backup files that you spent more than a couple minutes on and triple check it’s the latest copy! I’m currently in process of going through the whole script and making comments on what each section/block does. I’m hoping to finish the commenting tonight/tomorrow so I can start on the modifications again.

I have success using a m.2 WD blue 1TB SATA + 2.5 enclosure using the SD card method. All using Windows Disk Manager

  1. format the SSD into GPT, it will create a 200MB parition
  2. create a partition (don’t use all of the remaining space (say 95368MB is all the space avail), enter 95368 - 4130. You should see a black 4.03GB Unallocated partition in Disk Manager
  3. format the partition to exfat
  4. Use the SD card method as stated above
  5. wait for a bit and viola! Magic happens

Initially when I went to the GUI, I realize the reporting size is like 768MB! Plug the drive into Windows and I do see 1TB, so I went to the admin tab and do a factory restore (with disk option), after the next reboot, it shows up at 1TB now. Even the picture shows up as My Passport Wireless SSD!

2 Likes

Great tip, Jayband, very helpful! That worked for me with a WD Blue M.2 1TB and a third-party M.2-to-SATA enclosure. (Incidentally, I didn’t find I needed the β€œdd” step Divovlas was unsure of above.)

Hi,

After some experimenting, I’ve managed to get it to work on:
WD Blue 1TB SSD 2.5"
Lite-on 240GB SSD 2.5" (OEM)

And failed on:
Samsung QVO 1TB SSD 2.5"
ADATA SU800 128GB SSD 2.5" (Somehow bricked this one, becareful…)

The only conclusion I can draw from this is it will only work if it is a SATA SSD with a Marvell controller.
However, my sample size is too small to draw any definite conclusions, so for anyone that has a MPWP and a Marvell controller SSD, it would be great if you could give it a shot and report back!
Just follow the steps outlined by Jayband (step 1 did not create a 200mb partition for me) and report your results!

Also note that the password from serial is not the last 8 characters in the serial, but more specifically is (from memory) something like the 4th-12th characters in the serial, excluding stuff before the dash etc. Use command prompt/terminal to check the serial of the drive and then count the characters.

1 Like

my hard drive started clicking and the lights blinked so i searched and came across this thread.

Thanks to the info in here i was able to change out the hard drive to one i had available, i think it came out of an old laptop.

i can’t seem to find the password though. i entered the SN of the replacement hard drive (its only 8 characters in total) and it didnt work. i tried my old changed password, i tried the old hard drive SN as the password. does anybody have any suggestions? yes i tried 6P240WJN and 6p240wjn

attached is an image of the hard drive i put in it.

Hi, the label is a little off from what is actually read.

Plug the hdd into a computer and read it that way.
In windows, open command prompt and type:
wmic diskdrive get Name, Manufacturer, Model, InterfaceType, MediaType, SerialNumber

This should give you a serial. The length might differ from your original drive so you may have to guess and check where the 8 characters starts and stops. It should be something like the 4th to 12th characters.

Tell us how it goes!

thank you for your information, does the NAS function work well on your changes or still malfunction as mentioned above?

thanks.

Everything works just like a genuine β€œMy Wireless Pro SSD”

1 Like

@Newzj82 the wifi password is stored in the following files:

/etc/nas/config/wifinetwork-param.conf:AP_ENCRYPTION_KEY="AAAAAAAA"
/etc/nas/config/wifinetwork-param.conf:AP5G_ENCRYPTION_KEY="AAAAAAAA"
/etc/hostapd/hostapd.conf.2G:serial_number=WX71AAAAAAAA
/etc/hostapd/hostapd.conf.2G:wpa_passphrase=AAAAAAAA
/etc/hostapd/hostapd.conf.5G:serial_number=WX71AAAAAAAA
/etc/hostapd/hostapd.conf.5G:wpa_passphrase=AAAAAAAA
/etc/wpa2G4_supplicant.conf:serial_number=WX71AAAAAAAA
/etc/HDSerial:WX71AAAAAAAA
/etc/wpa_supplicant.conf:serial_number=WX71AAAAAAAA

You should be able to DD the last 4gB of the disk to a file, open it in a hex editor, and search for wpa_passphrase= On Windows you can use DiskInternals Linux Reader, right click the unallocated space, click hex preview, and search for wpa_passphrase=

In order to get @jayband 's process to work I needed to create a partition in the remaining 4130mB and format it to fat32 using a slow format, and then delete the 4130mB partition. The OS is stored in that unallocated slack space and if you don’t properly delete it you may have some issues.

If you extract the firmware update file with

tar xf file.bin

There’s a rootfs.tar.gz if you extract that you will have a filesystem that gets written to disk in

/etc/init.d

You’ll see a bunch of scripts that run at boot. Inside S60hostapd there is a β€œReGerneateSSID” function that creates the password from the HDD Serial number using hdparm. If you are unconfigured it will generate the password using this.

SN=/usr/local/sbin/getSerialNumber.sh | cut -c 5-12

Which calls

serial_number=hdparm -I ${Node} | sed -n -e 's/.*Serial Number:\(.*\)/\1/p' | sed -e 's/^[ \t]*//' | awk '{gsub("WD-","",$0); print $0}'

If you are configured it will call a similar function. So if your serial number is 6P240WJN your password will be the last 4 digits 0WJN. Which is going to cause some issues because wifi passwords need to be at least 8 digits. I have a seagate drive that is in the same boat that I’m trying to figure out. Perhaps @PuDLeZ can better explain how you use losetup so we can fix this script.