Buffalo Forums
Products => Storage => : billy June 07, 2019, 08:47:44 PM
-
hi all could i please ask if someone could please help me, after have a power cut in my house my nas has all gone wrong all i get is Emergency Mode on my Buffalo NAS Navigator and for the life of me i cant get it to work, my nas is a ls-wxl/r1 thanks for your time
-
That indicates your device is booting but there is some sort of problem with the root filesystem. You can try running the the firmware updater to reinstall the firmware to correct this.
If that doesn’t work you can use the debug options to do a force-update or if necessary repartition and reformat the device if all else fails. As always, proceed with caution if there is any sata on the device that you care about.
Here are instructions for enabling debug mode on lsupdater:
https://buffalonas.miraheze.org/wiki/Enable_Debug_mode
-
can anyone please tell me what i'm doing wrong ?? https://ibb.co/Zz2NnRJ
-
What have you tried?
-
sorry forgot to add photos https://ibb.co/Zz2NnRJ
-
You have a faulty disk, identify which one and then replace it. Is there a backup? What RAID mode was set?
-
You have a faulty disk, identify which one and then replace it. Is there a backup? What RAID mode was set?
hi davo i have replaced all drives with new ones the photo above is from the new drives
-
can anyone please tell me if ls_series-v174 is the right update for the LS-WXL/R1 ? (LSWXL-WM42E) THANKS
-
yes it is.
http://buffalo.jp/support_ap/support/products/ls_wxl.html
-
yes it is.
http://buffalo.jp/support_ap/support/products/ls_wxl.html
Thank you that is the one i was trying , get feed up now spent last 3 days trying to fix this with no joy >:( >:( :(
-
what debug options did you enable when trying to format the new drives?
-
what debug options did you enable when trying to format the new drives?
Thank you for your time , in the LSUupdater i edited
[Application]
Title = BUFFALO LinkStation Series Updater Ver.1.74
WaitReboot = 1200
WaitFormat = 600
WaitFileSend = 600
WaitDiscover = 120
[Target]
ProductID = 0x00000011
ProductID2 = 0x00000012
ProductID3 = 0x00000013
ProductID4 = 0x00000014
ProductID5 = 0x00003006
ProductID6 = 0x00003007
ProductID7 = 0x00000015
ProductID8 = 0x00000016
ProductID9 = 0x00003008
ProductID10 = 0x00004001
ProductID11 = 0x00000017
ProductID12 = 0x00000019
ProductID13 = 0x00000020
ProductID14 = 0x00003010
Name = LinkStation
[Flags]
VersionCheck = 0
NoFormatting = 0
[SpecialFlags]
Debug=1
i then restart LSUpdater and get this
partition not detected
The TARGET will be formatted and data will be lost
continue to update
I press yes
_______________________________________
I then get LSUpdater popup
farmat failed
update aborted
-
to get the updater to actually perform the repartition/reformat you need to go into the debug menu (upper-left) enable the relevant options (force format, force partition, force update).
This will wipe out any data on the drives and then do a fresh firmware install.
-
to get the updater to actually perform the repartition/reformat you need to go into the debug menu (upper-left) enable the relevant options (force format, force partition, force update).
This will wipe out any data on the drives and then do a fresh firmware install.
yes sorry done all that and still get
i then restart LSUpdater and get this
partition not detected
The TARGET will be formatted and data will be lost
continue to update
I press yes
_______________________________________
I then get LSUpdater popup
farmat failed
update aborted
-
do you have both drives installed?
-
yes tried it with 2 drives and then tried with one drive
tried not using DHCP AND put in a new ip address
what i did see on NAS Navigator2 the gateway is 0.0.0.0 as seeing in photo above
when i close NAS Navigator2 and reopen it use DHCP is backed ticked but last 3 digits missing ??
-
Have you checked those discs externally? Most of the time if the updater gives a format failed there is an issue (errors on disc/incompatible)
-
Yeah, it sounds like you best bet is to completely wipe, or at least remove the partition tables of both disks and start fresh.
This procedure should be able to get it working for you:
https://buffalonas.miraheze.org/wiki/Restoring_Stock_Firmware_without_TFTP
-
THANKS GUYS i have tried with 4 new WD red drives and and 2 green drives also tried a Samsung 500GB i had lying around still got nothing is there any test i can run on the nas to see if the problem is there ??? thanks
-
Can you be more specific about what you tried exactly?
If you give us the steps that you've tried with sufficient detail we may be able to figure out where you're going wrong.
-
ok all was working very well for 4+ years with no problems at all, i then had a power cut in my house and when power came back on the nas was in EM MODE on BUFFALO NAS Navigator2 as seen in photos i then tried ls_series-v174 to do update again this also filed as seen in photos here https://ibb.co/Zz2NnRJ
drives that where in the nes when it failed are 1 WD 2TB green & 1 hitachi Deskstar 500GB
this is now where i'm at
pulled all drives and cleaned all dust from nas
put drives back power up nas i get some blue blinking blue light (Function LED) on setup and then a solid Blue LED: Power on
i then open LSUdate find my nas and hit update and get Partition not detected i then hit yes continue update at this point i get format failed
next i tried
to edit the LSUpdater with this
[Application]
Title = BUFFALO LinkStation Series Updater Ver.1.74
WaitReboot = 1200
WaitFormat = 600
WaitFileSend = 600
WaitDiscover = 120
[Target]
ProductID = 0x00000011
ProductID2 = 0x00000012
ProductID3 = 0x00000013
ProductID4 = 0x00000014
ProductID5 = 0x00003006
ProductID6 = 0x00003007
ProductID7 = 0x00000015
ProductID8 = 0x00000016
ProductID9 = 0x00003008
ProductID10 = 0x00004001
ProductID11 = 0x00000017
ProductID12 = 0x00000019
ProductID13 = 0x00000020
ProductID14 = 0x00003010
Name = LinkStation
[Flags]
VersionCheck = 0
NoFormatting = 0
[SpecialFlags]
Debug=1
closed LSUdate and re opened
on the top left i go into Debug Mode
first i try default setting
update BOOT
update KERNEL
update initrd
update rootfs
do not check version and click ok hit update and get the fails in photos
i then go back to Debug Mode
update BOOT
update KERNEL
update initrd
update rootfs
do not check version
and now click force update
still getting the fails in photos
i have also tried settings in Debug Mode
rebuild partition table
and delete user partition
still getting the fails in photos
so at this stage i pull all old drives and put in new ones
first with 2 drives in power up nas
and follow whats above all over again still getting the fails in photos
i have tried only using one drive still nothing
new hdd are
3 WD red 2TB new
2 WD green 2TB NEW
1 SAMSUNG 500GB NEW
ALL come back saying Partition not detected i then hit yes continue update at this point i get format failed
all this is done with my AV off
i also see a red led lite up in side nas never seen this before as i all ways put cover back on after drives
thanks for your time
-
There are a few oddities that show up with some of these devices though I wouldn't think you would be running into any of them. some devices won't install the firmware unless minimum number of drives are present or the drives are bigger than a certain size. None of that should apply to you trying to install firmware to 2 matching drives in an ls-wxl.
what are you doing to prepare the drives before you put them in?
I'll try with one of mine when I get a chance and see if I run into anything unusual.
-
ok starting to thing there may be a problem with nas
removed all drives from nas and powered up again all i get is a blue flashing led power light for a bout 15-20 secs and then a solid blue power light
should i not be getting an error mgs with no hdd in the nas ???
-
It depends, I can try that too when I get mine out.It might just mean that it’s in TFTP mode or it booted from internal NAND. Either way if you’ve been managing to get the device into EM mode and it’s been showing up in LSUpdater there can’t be that much wrong with it.
-
It depends, I can try that too when I get mine out.It might just mean that it’s in TFTP mode or it booted from internal NAND. Either way if you’ve been managing to get the device into EM mode and it’s been showing up in LSUpdater there can’t be that much wrong with it.
Thanks 1000001101000
-
me thinks its time to scrap and look for a new nas :( :'(
-
That may be true either way, it is a rather old device at this point.
-
That may be true either way, it is a rather old device at this point.
true just a shame the problem only happened for a power cut , would there be any why to try and recover data ?? for the 2 drives ?? thanks
-
would there be a guide on doing a TFTP Boot Recovery ?? do see one on the site
Thanks
-
would there be any why to try and recover data ?? for the 2 drives ?? thanks
The data is stored in an XFS filesystem which can be accessed from a linux environment. Where you using Raid0, Raid1 or just two drives with separate shares?
-
I just restored the stock firmware on my ls-wxl with two old wd green 1.5tb drives.
I followed this method:
https://buffalonas.miraheze.org/wiki/Restoring_Stock_Firmware_without_TFTP
The key was to use uImage-lsp.5.x.buffalo as the uImage.buffalo file.
for my lsupdater debug options I selected everything except "update boot"
I put a completely blank drive in slot2, In slot 1 I put a drive with a gpt partition table with a single 1gb partition formatted ext3 with the initrd.buffalo and uImage.buffalo extracted from the firmware.
The commands I used to build drive 1 were:
/ls_series-v174/LinkStation_FW1.74# ls
hddrootfs.img linkstation_version.ini LSUpdater.exe u-boot.img
initrd.img linkstation_version.txt LSUpdater.ini uImage.img
/ls_series-v174/LinkStation_FW1.74# unzip initrd.img
Archive: initrd.img
[initrd.img] initrd.buffalo password:
inflating: initrd.buffalo
/ls_series-v174/LinkStation_FW1.74# unzip uImage.img
Archive: uImage.img
[uImage.img] builddate.txt password:
inflating: builddate.txt
inflating: uImage-88f5182.buffalo
inflating: uImage-lsp.5.x.buffalo
inflating: uImage.map
~# lsblk /dev/sdm
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdm 8:192 0 1.4T 0 disk
~# gdisk /dev/sdm
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-2930277134, default = 2048) or {+-}size{KMGTP}:
Last sector (2048-2930277134, default = 2930277134) or {+-}size{KMGTP}: +1G
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300):
Changed type of partition to 'Linux filesystem'
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdm.
The operation has completed successfully.
~# mkfs.ext3 /dev/sdm1
mke2fs 1.43.4 (31-Jan-2017)
Creating filesystem with 262144 4k blocks and 65536 inodes
Filesystem UUID: 8a4ddb7e-44ae-4bd9-8dc7-2f5f4563e54a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
~# mount /dev/sdm1 /mnt/image
~# cd /mnt/image
/mnt/image# cp /ls_series-v174/LinkStation_FW1.74/*.buffalo .
/mnt/image# cp uImage-lsp.5.x.buffalo uImage.buffalo
/mnt/image# ls
initrd.buffalo lost+found uImage-88f5182.buffalo uImage.buffalo uImage-lsp.5.x.buffalo
/mnt/image# cd
/mnt/image# sync
~# umount /mnt/image