{"id":1008,"date":"2013-11-18T08:49:41","date_gmt":"2013-11-18T14:49:41","guid":{"rendered":"http:\/\/www.poweradmin.com\/blog\/?p=1008"},"modified":"2015-04-27T08:26:41","modified_gmt":"2015-04-27T13:26:41","slug":"fixing-a-buffalo-ls-qv4-0tlr5-nas","status":"publish","type":"post","link":"https:\/\/www.poweradmin.com\/blog\/fixing-a-buffalo-ls-qv4-0tlr5-nas\/","title":{"rendered":"Fixing a Buffalo LS-QV4.0TL\/R5 NAS"},"content":{"rendered":"

\n\t\"Buffalo<\/a>We got a little NAS device to play around with, do some back ups to, etc. \u00a0The Buffalo\u00a0LS-QV4.0TL\/R5 comes with 4 x 1TB drives, but we wanted some more space, so we replaced the 1TB drives with 2TB drives. \u00a0Mistake \ud83d\ude41 \u00a0 It turns out the OS is on those drives (duh!). \u00a0What you'll see in this case is the power button blinking red 6 times (called ES6 or ES06). \u00a0It's not listed in the manual, but that error means the disks were found, but they didn't boot. \u00a0Makes sense.\n<\/p>\n

\n\tThere is a popular FAQ about what to do about this:<\/span>\n<\/p>\n

\n\thttp:\/\/forums.buffalotech.com\/index.php?topic=10185.0<\/a>\n<\/p>\n

\n\tBasically the device _should_ make an tftp request to a fixed IP to download it's boot files and then start up. \u00a0We could not make that happen in this state though. \u00a0After hours of scouring the internet and reading blogs and forums, we came upon a post in that same thread that held the secret:\n<\/p>\n

\n\thttp:\/\/forums.buffalotech.com\/index.php?topic=10185.msg48409#msg48409<\/a>\n<\/p>\n

\n\tIn particular, the boot files apparently needed to be named\u00a0initrd.buffalo and uImage.buffalo. \u00a0<\/span>\n<\/p>\n

\n\tSo we downloaded and burned a\u00a0Linux Mint ISO to CD. \u00a0Opened a computer, disconnected the Windows drive (a little paranoia to keep it safe!) and connected the drive from the NAS. \u00a0Then booted up into Linux. \u00a0A few quick Google queries showed how to format the disk and mark as bootable, and then we just needed to copy the\u00a0boot files. \u00a0Put the drive back into the NAS and power up. \u00a0<\/span>Once we did that, it at least connected to the network but there was still some jumping through hoops to come.<\/span>\n<\/p>\n

\n\tBuffalo's NasNavi could find the device, so we ran the firmware updater (we used firmware 1.65 \u2014 the latest at this time). \u00a0Then it rebooted, still the ES06 error but was at least on the network. \u00a0THEN it started pulling the boot files via tftp. \u00a0When tftp works, it works quickly \u2014 the files are pulled down within a minute of the device booting up.<\/span>\n<\/p>\n

\n\tOne more hitch \u2013 once it was booting up on it's own and seemed healthy, it was time to connect to its web interface\u00a0and configure the device. \u00a0But the user interface was in Japanese \ud83d\ude41 \u00a0 \u00a0Easiest fix we could find: Use Chrome and load a translator add-on. \u00a0Once that was done, we poked around the menu until we found a language setting, switched it to English, and we were finally in business.\n<\/p>\n

\n\tHope these pointers help someone else!\n<\/p>\n

\n\t\"Tweet<\/a>\n<\/p>\n

\n\t\"Share<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

We got a little NAS device to play around with, do some back ups to, etc. \u00a0The Buffalo\u00a0LS-QV4.0TL\/R5 comes with 4 x 1TB drives, but we wanted some more space, so we replaced the 1TB drives with 2TB drives. \u00a0Mistake \ud83d\ude41 \u00a0 It turns out the OS is on those drives (duh!). \u00a0What you’ll see […]<\/p>\n","protected":false},"author":3,"featured_media":1012,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,9,8],"tags":[],"class_list":["post-1008","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general-it","category-how-to","category-technical","category-windows"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t