Ls-wxl Firmware

0 views

Skip to first unread message

Chris Richard

unread,

Aug 4, 2024, 5:49:15 PM8/4/24

to vieporavib

Im using Buffalo's Linkstation Duo NAS and at the very beginning I used to have some problems like FTP functionality issues and some more. But then I updated to firmware version 1.37 it all went different in a very good way. Everything worked just fine and the drive was solid as a rock. Even the FTP was working! :)

But then Buffalo released a new firmware v. 1.41 and now the drive is just a piece of sh*t! It's constantly unreachable, dropped somewhere in the network and my beloved FTP is simply gone. Not to be mistaken with faulty working - it's simply not there!

I got the same problem, but I was upgraded from 1.54 to 1.56 of LinkStation LS-WXL/R1 Series. I want to downgrade to 1.54, but the 1.54 firmware program don't discover any LinkStation needed to be "UPGRADE".

Now, iPhoneS and iPad of my relatives can't reach the LinkStation through DLNA clients. I am receiving complains, all the time. No matter I upgrade the software, like NasNavi. I found out, they cannot discover Linkstation through wireless network, even the firewall is off. I did try restore/erase, but nothing work.

I tried cloning the 1TB drive to the 2TB drive, that worked somehow I was able to start the device with only the cloned 2TB disk inside, BUT it still had only 1 TB allocated and I could not resize the disk (example GParted did not pick up the partitions as usable) and the Linkstation admin page could not resize it. I tried removing the RAID1 from the disk, after which, I cannot access it anymore. Just get the 6 blinking red lights, with both new disks, installed together, or individually. Tried as toitally unpartitioned, as NTFS partitioned, nothing worked.

There are several ways, but it is not that easy as with the older boxes. Just putting in a blank drive and updating the firmware does not work as the Firmware updater does not find the box. Why? Because in contrast to the older boxes everything but the bootloader(UBoot) is on the hdd. so even EM Mode got implemented via an initrd in /boot (=/dev/sda1).

Thanks Andy for the guide. My adventure of getting out of EM mode did not require the TFTP method and amazingly (and *very* thankfully), I did not lose data. Reading your guide as well as a couple of others gave me the information to resolve my issue (my Linkstation IP address would not update after a new router was installed).

After I assigned a static IP to my machine on the same subnet as the Linkstation, LSUpdater successfully ran a firmware update on the Linkstation. I then used the NAS Navigator to bring up the properties on the Linkstation and manually assigned a new IP address to it.

After troubleshooting some connectivity with the NAS, I power-cycled the NAS. The NAS grabbed a DHCP address, which took me a minute to figure out. After discovering the new IP, I was able to ping the NAS but not connect to it via or via URI (\\nasname or \\nasIP).

After starting LSUpdate.exe, my router shows that the NAS rebooted a couple of times, and the interface sent approximately 235000 packets and just under 300000000 bytes towards the NAS. After which point the LSUpdate tool reported that it could no longer contact the NAS. This process took approximately 10 minutes.

Recently I picked up a Buffalo Linkstation 220 to play around with at home as I felt that I could use a bit of additional storage to play around with. Note that this previous statement is pretty much a lie. I have tons of storage, and was really just looking for an new toy to play around with. Basically I just had a few disks laying around that I wanted to put to use.

Fortunately the site that I borrowed the above image from (here) and this site (here) give advice on how to fix the issue. First step is to download the Buffalo Linkstation Firmware Updater that you can get here. Both pages advise you to modify the LSUpdater.ini file. However their instructions did not work for me. The exact changes, and the LSUpdater.ini in its entirety are below.

At this point you launch the updater again, and select Update. This fully partitions the drives and then updates the firmware. This process takes a while, so be patient. Now you can launch the NAS Navigator and configure the device.

Excellent post. I have just bought an enclosure and put 2 Seagate 2TB disks in after deleting everything on them and initializing them. The firmware updater said there was no partition and aborted. After finding this post I made the necessary changes and it worked perfectly.

Thanks very much.

I just bought new one and it was bricked right out of packet. No help with buffalo help desk. Now with your instruction, I got it working and no need to return it. This is very bad product I must say.

absolutely one of the really necessary times the internet and google have saved me. this came up in one of the first 3 or 4 links to the EM / format error. i used your .ini exactly as written and within 15 minutes my NAS drive is up and running. Thank you so much Christopher !! You are the bomb diggity !!

Yes I have the same problem on LS 220D. I made a 1GB partition in my HDD (EXT3) and stored the files firmware files (initrd.buffalo and ulmage.buffalo) maybe that is the reason. I will try to format the HDD with only one partition and retry tomorrow

I wanted some way of playing my music collection to a network music player, and Squeezeboxes seemed the best option. I'd been looking at using the DLNA server on the LS (Twonky Media Server) but the players didn't look so good. Trouble was Squeezeboxes don't work with the Twonky, they need their own server. So it needed to have SBS installed.

As with all these things, I need to say you could brick your box doing this. I wouldn't've done any of this if I thought there was a big chance of that. I think it takes some careless messing to really brick the box unrecoverably. That said, it could take some time and skill to recover it if it needed to be brought back to life from a failed firmware upgrade.

I'm using Windows 10 pro and have an X10 R9000 Router that's been working great since 2019. Two days ago I installed version V1.0.5.42 firmware update and rebooted the router. Since then I can't access my network drive. When I log into the router it's showing as an attached device but at times it doesn't have any IP address. I've refreshed and rebooted again and restarted my PC and It finally shows an IP. When I use NAS Navigator 2 program to view the drive I'm able to see information like IP, default gateway, subnet mask, mac address and firmware version but I can't browse any folders. I get a message that "The shared folder cannot be opened". Tried to map a Share while still in Navigator and get message "Could not map the Share. Create Folder named Share before mapping drive. When trying to access the drive in windows explorer I get a message that "The remote device won't accept the connection". Help for this problem would be much appreciated. Since I had no problems with accessing the NAS prior to firmware update and reboot I have to assume that it changed something.

Network is, and has always been set to private and troubleshooter can't identify the problem. Since both the router and NAS are out of warranty I don't have access to their factory support so can't get help from either of them. I really need the data stored on the NAS.

Not sure how to safely roll back to previous firmware. I've always logged in to router from my computer to update, but I don't see an option in router settings to accomplish that. I don't want to do something wrong that might brick my router. I downloaded the previous version from the Netgear website but I'm not 100% sure if it's the one that was in use prior to updating to the latest ver. It might be possible that I missed an update. Is it safe just to run the downloaded update, or do I need to perform any other steps first?

I am not trying to discourage you from learning how to roll back your router firmware and do so properly (i.e. with a web browser and a computer connected via Ethernet to your router). But, rolling back your router firmware will do nothing to correct or restore your windows settings so you can access your NAS files.

You were right about rolling back the firmware, it didn't solve the problem so I updated to the newest version again. I've tried everything the internet offered for a fix and still cant access my NAS. I can successfully ping the router and I tried accessing it using it's ip address under Map Network Drive but it returns a Network Error "Windows cannot access". Clicking on Diagnose shows the message Details: "The device or resource (LS-WTGL7AF) is not set up to accept connections on port "The Fire and printer sharing (SMB)" I've triple checked and ALL the SMB boxes are checked. Any other suggestions?

You can do your own review of the threads. There were recent updates to Windows that impacted devices that use SMB1 for network communication. I recall Windows disabled SMB1 and it is possible to re-enable it in Windows settings.

Put Windows SMB1 in your web browser search engine. Lots of information available. You just have to sort through it. Some may be scams and recommend you don't download and install "Help Site" software. Steer toward links to Microsoft articles.

Tried to print to my HP network printer today that has been working for years and is now showing offline. I printed yesterday without any issues, the computer and router were not powered off or rebooted, and no changes were made to the network in any way. I used troubleshooter and it's giving a similar message that 'The device is not set up to accept connections on port "9100"'. I signed into router through web access to view 'Attached Devices'. The printer and the NAS are listed but their ip addresses are 0.0.0.0 I tried rebooting both the router and computer with no luck. When viewing through 'access control' the ip addresses show up there. I've now lost 2 devices from my network and I'm about ready to try fixing the router with a sledge hammer. Any other suggestions?