Author Topic: LS-Q6.0TL/R5 E15 Error Following NTFS Format  (Read 3477 times)

newked

  • Calf
  • *
  • Posts: 7
LS-Q6.0TL/R5 E15 Error Following NTFS Format
« on: February 18, 2020, 09:32:55 PM »
Hello everyone,

I am hoping someone can help me, I recently purchased what I thought was a working NAS from ebay and I could not for the life of me get it to connect to the buffalo nas navigator. Finally out of frustration I formatted the 4 drives in the unit to NTFS using my windows PC. I now have what looks like an e15 error and have no clue in hell what to do. I have searched the forums and keep finding info on TFTP and needing to download my specific file but all the links seem dead. Any help is greatly appreciated! Thanks in advance!

As3nd0r

  • Tatanka
  • **
  • Posts: 55
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #1 on: February 19, 2020, 12:51:30 AM »
Its the second post in the stickies... https://forums.buffalotech.com/index.php?topic=30419.0 however if I recall correctly on those models E15 was some HDD issue (bad sectors?), it would show E06 if it needs the boot files. can you double-check what error this is showing?
Aspirat primo Fortuna labori
Me duce tutus eris

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 1128
  • There's no problem so bad you cannot make it worse
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #2 on: February 19, 2020, 06:45:05 AM »
If the drives were all formatted NTFS it won’t be able to boot far enough to check for bad sectors/etc, though it would be worth running diagnostics on them before proceeding.


newked

  • Calf
  • *
  • Posts: 7
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #3 on: February 19, 2020, 08:39:34 AM »
The first link tells me to unzip the file but I don't even know where they want me to unzip it? To one of the 4 drives? do I format the drive to ext3 then unzip the files to it? Sorry it's not clear for me...

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 1128
  • There's no problem so bad you cannot make it worse
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #4 on: February 19, 2020, 09:20:11 AM »
The first step is to unzip the files, after that you can either load them onto an Ext3 partition on the first disk or use them with the TFTP process you've seen described elsewhere (but using a generic TFTP program).


If you load directly to the disk you'll need to create a small partition (512M will work) using fdisk (this model needs to not be GPT). Then you'll want to format it as ext3 with inode size of 128 ex.
Code: [Select]
mkfs.ext3 -I 128 /dev/sdx1. Then copy the files to that partition and insert it as disk 1 along with the other (still blank) drives. It should then boot into EM mode from that disk.

newked

  • Calf
  • *
  • Posts: 7
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #5 on: February 20, 2020, 03:24:41 PM »
So I formatted the 1 first drive as EXT3 and copied over the initrd.buffalo & uImage.buffalo to the drive. I then removed the drive from my pc and put it back in the nas in the first spot (no other drives are installed) I still get the flashing E15 error, what am I doing wrong? Should I try doing the above with a different drive or do my .buffalo files need to be in a specific folder?

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 1128
  • There's no problem so bad you cannot make it worse
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #6 on: February 20, 2020, 04:00:53 PM »
If you provide more detail around how you are partitioning/formatting/unzipping/copying we can probably identify where it is going wrong.

You’ll want all the drives inserted when it comes time for the install bit you should be able to reach EM mode with just one.

newked

  • Calf
  • *
  • Posts: 7
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #7 on: February 20, 2020, 05:32:47 PM »
I formatted the first drive using aoemi partition assistant in EXT3 format, I then used ext2fsd to transfer the 2 .buffalo files to the drive. Then I put that drive in the nas slot #1 without any other drives. The unit powered on and then I get one 1.0sec red light followed by 5 quick .3 sec lights. I am assuming the code is E15. That didn't work so I repeated the above process with another drive only to have it flash the same code.

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 1128
  • There's no problem so bad you cannot make it worse
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #8 on: February 20, 2020, 05:42:12 PM »
It needs to be in a partition (the first one) rather than the whole drive. The inode size is also important, though your program may default to the correct value.

newked

  • Calf
  • *
  • Posts: 7
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #9 on: February 20, 2020, 07:00:55 PM »
I made 2 partitions, the first partition was 1gb and I tossed the 2 .buffalo files on the first partition which is in EXT3 format. I still get this darn red light E15 code :(

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 1128
  • There's no problem so bad you cannot make it worse
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #10 on: February 20, 2020, 07:22:24 PM »
I think those older devices may need a smaller partition, it’s been a while since I did it with that model. Try with a 512MB partition and see if that helps.

I’m assuming you were able to extract the password protected zip images, if you were trying to boot the zips rather than the extracted files.

If that still doesn’t work you’ll need to verify the following:
-you’re using an MBR not a GPT
-that the partition is partition 1
-your EXT3 filesystem is using 128 byte inodes (the modern default is 256)
-that you’ve got the correct files with the correct filenames.

These are all fairly easy to validate if you boot into a linux environment, I’m not familiar with the tools for doing so under windows.

« Last Edit: February 20, 2020, 08:17:40 PM by 1000001101000 »

newked

  • Calf
  • *
  • Posts: 7
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #11 on: February 22, 2020, 05:48:19 AM »
The only thing is the list is the inode size that could be the issue. But I feel like the error is something messed up as I get the same error with the drive in, is that normal in itself?

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 1128
  • There's no problem so bad you cannot make it worse
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #12 on: February 22, 2020, 06:25:54 AM »
That sentence didn’t quite make sense to me.

If you are saying you keep getting the same error no matter what you do, that would make sense since failing to read the boot files is just 1 error code though it can have several causes. If you start it with no drives at all I would expect it to switch to 7 red blinks (though I’m a bit unsure with that particular model).

Very few things care what the inode size is (the bootloader on these older devices being one of the) it’s possible your utility sets them as 256 without fanfare. I think this is pretty likely to be your problem.

If I get time later i’ll walk through the process on mine and record each of the commands I use.

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 1128
  • There's no problem so bad you cannot make it worse
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #13 on: February 22, 2020, 10:06:56 AM »
I ran through this on a Debian Buster system and it worked for my LS-QL. It should work from any Linux live environment.

One note is that the initrd.img has to be unzipped but uImage.buffalo does not need to be.

Code: [Select]
root@localhost:~/scratch# unzip lsql-111.zip
Archive:  lsql-111.zip
   creating: lsql-111/
  inflating: lsql-111/hddrootfs.img 
  inflating: lsql-111/initrd.img     
  inflating: lsql-111/linkstation_version.txt 
  inflating: lsql-111/LSUpdater.exe 
  inflating: lsql-111/LSUpdater.ini 
  inflating: lsql-111/u-boot.buffalo.updated 
  inflating: lsql-111/uImage.buffalo
root@localhost:~/scratch# cp lsql-111/uImage.buffalo .
root@localhost:~/scratch# unzip lsql-111/initrd.img
Archive:  lsql-111/initrd.img
[lsql-111/initrd.img] initrd.buffalo password:
  inflating: initrd.buffalo
root@localhost:~/scratch# ls
initrd.buffalo lsql-111  lsql-111.zip uImage.buffalo
root@localhost:~/scratch# dd if=/dev/zero of=/dev/sdx bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 14.0496 s, 76.4 MB/s
root@localhost:~/scratch# fdisk /dev/sdx

Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x8f909987.

Command (m for help): n
Partition type
   p   primary (0 primary, 0 extended, 4 free)
   e   extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-976773167, default 2048): 2048
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-976773167, default 976773167): +512M

Created a new partition 1 of type 'Linux' and of size 512 MiB.

Command (m for help): p
Disk /dev/sdx: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Hitachi HDS72105
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: dos
Disk identifier: 0x8f909987

Device     Boot Start     End Sectors  Size Id Type
/dev/sdx1        2048 1050623 1048576  512M 83 Linux

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

root@localhost:~/scratch# mkfs.ext3 -I 128 /dev/sdx1
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 131072 4k blocks and 32768 inodes
Filesystem UUID: b33a2d54-a2bd-482a-a1c3-5b712a683b15
Superblock backups stored on blocks:
32768, 98304

Allocating group tables: done                           
Writing inode tables: done                           
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

root@localhost:~/scratch# mount /dev/sdx1 /mnt
root@localhost:~/scratch# cp *.buffalo /mnt/
root@localhost:~/scratch# ls /mnt
initrd.buffalo lost+found  uImage.buffalo
root@localhost:~/scratch# umount /mnt


newked

  • Calf
  • *
  • Posts: 7
Re: LS-Q6.0TL/R5 E15 Error Following NTFS Format
« Reply #14 on: March 08, 2020, 07:09:33 PM »
I literally had the intrd.buffalo and uImage.buffalo on an ext3 formatted drive, that did not remotely work then I created a 1gb partition and through both those files on it and no dice. Judging by the log you posted I am not remotely doing this properly