Author Topic: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater  (Read 5345 times)

aharrop

  • Calf
  • *
  • Posts: 1
Guys,

I have a ls-qvl/r5 which has had a checkered existence. It has bricked over firmware a number of times and has been saved. It has been resurrected due to drive failure and EM issues multiple times, mainly through following others' advice on this forum, and some luck.

I hope someone can assist.

Complaint is the same as in this solved thread here http://forums.buffalotech.com/index.php?topic=17553.0, blue flashing power light, however I cannot gain a steady blue light as instructed after resetting using the function button. In the past this, and just restarting, has corrected the issue. I was experiencing it dropping out and freezing for up to 2 weeks, but now it is stuck.

Here is what I have tried.

1) Power off NAS (only way is to cut power by pulling cord).

2) Hold function button, power on. I gain flashing function LED light.

3) Release function and NAS powers up (cannot get it to power up without releasing).

4) Hold function button again for 10 seconds (nothing changes).

The NAS just sits with flashing function and power LEDs in blue. The device cannot be seen by NAS Navigator 2 (Sep 2016). It was running firmware 1.71 (up to date) which I have downloaded again, and cannot see the device when plugged in directly to my Mac through ethernet.

Any suggestions, as I have spent hours trawling forums over this hardware and cannot find anything to take me forward?

Thanks!

flooreus

  • Calf
  • *
  • Posts: 15
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #1 on: August 15, 2018, 05:20:53 am »
Hi,

I would like to try and resurrect this thread, as I am having the same problem. I was running the exact same firmware version, and this post describes exactly my issue and what I have tried to do to resolve the issue. This occurred when I tried to update the firmware through the web UI. This means it was my NAS' own attempt at upgrading its firmware that caused this, and not mine!

Can someone please help, I am at my wits end with this.

davo

  • Really Big Bull
  • VIP
  • *
  • Posts: 5958
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #2 on: August 15, 2018, 09:20:03 am »
How many disks are you using? What RAID mode and do you have a backup?
PM me for TFTP / Boot Images / Recovery files  LSRecovery.exe file.

flooreus

  • Calf
  • *
  • Posts: 15
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #3 on: August 16, 2018, 04:21:31 am »
Not sure how this is relevant, but I am using 4 x 4TB drives in RAID1+0 and no I do not have a backup. I was in the process of purchasing an 8TB external HDD when this happened, in fact, grrrr!

davo

  • Really Big Bull
  • VIP
  • *
  • Posts: 5958
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #4 on: August 16, 2018, 05:13:29 am »
Its completely relevant actually, try removing one disk at a time and rebooting the unit to see if it appears in the NAS Navigator.
PM me for TFTP / Boot Images / Recovery files  LSRecovery.exe file.

flooreus

  • Calf
  • *
  • Posts: 15
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #5 on: August 16, 2018, 05:18:58 am »
Hi,

OK I will try this now for each drive, but can you tell me why? The issue is that I attempted a firmware upgrade through the Web UI and, once it rebooted after installing, it will now not boot into the kernel. This isn't a drive issue so not sure why I'm doing this.

flooreus

  • Calf
  • *
  • Posts: 15
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #6 on: August 16, 2018, 05:48:00 am »
OK I tried pulling them 1 by 1 and booting but nothing worked, the power light still blinks rapidly blue and doesn't boot into the kernel. NAS Navigator2 doesn't show anything.

flooreus

  • Calf
  • *
  • Posts: 15
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #7 on: August 19, 2018, 12:33:46 pm »
Does anyone have any advice for me on this? My NAS is currently unusable due to something it did to itself. My Plex setup relies on this storage, and so I've lost my primary media platform. It was my primary photo backup and I'm scared I may have lost all of my photos from way back. Can someone please suggest something that may help?

oxygen8

  • The Oxy-genuine article
  • El Toro
  • ****
  • Posts: 380
  • Giving you some breathing space.
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #8 on: August 21, 2018, 05:05:45 am »
My tested way is to delete the demaged firmware.
This is on the second partition an any drive as raid1 (mdadm)

My german example with 2 drives from a duo:
http://forum.nas-hilfe.de/buffalo-technology-nas-anleitungen/blaues-blinken-raeparatur-einer-beschaedigten-linkstation-duo-ls-wvl-ls-wxl-t2014.html

flooreus

  • Calf
  • *
  • Posts: 15
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #9 on: August 23, 2018, 01:31:56 pm »
Thanks. I have now manged to remove the old firmware, but now the system is boot looping. I was expecting I'd be able to get the device to boot using TFTP, or I'd be able to use LSUpdater.exe to flash new firmware....how do I get the device into EM mode? It is booting so far, then after realising there's no firmware it shuts down and reboots.

oxygen8

  • The Oxy-genuine article
  • El Toro
  • ****
  • Posts: 380
  • Giving you some breathing space.
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #10 on: August 23, 2018, 02:03:32 pm »
Quote
then after realising there's no firmware it shuts down and reboots.

maybe one first partition is not clean


mount the first partition from one drive
if this is ok, unmount it and try the next drive

please check the SMART values from all 4 drives

oxygen8

  • The Oxy-genuine article
  • El Toro
  • ****
  • Posts: 380
  • Giving you some breathing space.
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #11 on: August 23, 2018, 02:17:01 pm »
also sdX1 is used with mdadm!

Code: [Select]
md0 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
      1000384 blocks [4/4] [UUUU]

flooreus

  • Calf
  • *
  • Posts: 15
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #12 on: August 24, 2018, 05:46:02 am »
also sdX1 is used with mdadm!

Code: [Select]
md0 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
      1000384 blocks [4/4] [UUUU]

I noticed there was basically a full Linux installation on /dev/sdx2 so I deleted the files from there. You're looking at md0, and not md1. I'll bet md0 is the boot sector. I didn't think I'd have to clear this also. I'll take a look.

oxygen8

  • The Oxy-genuine article
  • El Toro
  • ****
  • Posts: 380
  • Giving you some breathing space.
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #13 on: August 24, 2018, 07:06:14 am »
Mache bitte nur, was da steht:

Quote
maybe one first partition is not clean


mount the first partition from one drive
if this is ok, unmount it and try the next drive

please check the SMART values from all 4 drives

Sollte das Dateisystem defekt sein, kannst du es nicht mounten.
Sollte eine Festplatte den SMART-Test nicht bestehen, musst du sie tauschen.



(Ich nutze nun lieber meine Muttersprache, da du mein dürftiges englisch nicht zu verstehen scheinst.)


Quote
I noticed there was basically a full Linux installation on /dev/sdx2 so I deleted the files from there.

Hast du das mit allen 4 Platten gemacht?

flooreus

  • Calf
  • *
  • Posts: 15
Re: Blue flashing lights on ls-qvl/r5 - cannot access via Nasnav or Updater
« Reply #14 on: August 24, 2018, 09:23:22 am »
Oxygen8

Thanks for your reply. I do understand your English I just hadn't reorder to your questions. The SMART status of all 4 disks is fine, and yes I did do the removal of all partition 2 data from all 4 drives. Partition 2 on all 4 is completely blank. I checked again to confirm.

Is there anything I have to do with the boot partition as well? Currently it is still boot looping.