Patreon - A subscription-based, kickstarter-like for artists

Stop the press: you have to check out Patreon. Go there now, I’ll wait.

Isn’t it such a simple but clever concept?

It gets the best of Kickstarter (the crowdfunding model for personal projects), but eliminates the burden of having to create a project worth tens of thousands of dollars.

Kickstarter works well for large and well defined projects - a game, a movie, a new gadget, or a new product. But it doesn’t work so well for small, frequent, always on, content-driven efforts. This includes youtubers, bloggers, musicians, photographers, writers of short stories, and artists in general.

Patreon was created by the amazingly talented Jack Conte and the lovely (and equally talented) Nataly Dawn, together with the serial entrepreneur Sam Yam.

This is not the first time that the duo is playing with crowdfunding ideas. Nataly launched her first solo album via Kickstarter a few years ago (I was a proud backer), and frequently performs live for her fans on StageIt.

Jack is a prolific multi-instrumentist and video producer, with millions of views on his YouTube channel. You may remember them from the also awesome (but now on a vacation of undetermined length) Pomplamoose. Here’s one of their old hits:


Even if you don’t want to contribute now, you should check Patreon and at least download Jack’s latest EP for free. But you should seriously consider sponsoring. C’mon, an hexapod robotic spider as a guest star? Way better than spending your hard-earned money on pebbles…

How to enable Google Now for iOS devices (iPhone, iPad) with Google Apps for Business Accounts

Google Now is finally available for iOS since earlier this week. But if you’re using Google Apps for Business domain like me, you may have received an annoying “your administrator hasn’t enabled Google Now for your domain”.

Fear not, the solution is easy. You just have to enable Google Now, within the (non-intuitive) Setting / Mobile / Android Setting / Enable Google Now.

For detailed instructions, head to this post on Scott Hanselman’s blog, that has pretty pictures and the exact details.

Scammers Targeting MMORPG Players

Just received this interesting phishing email:


From: noreply@Blizzard.com [mailto:talktoeric911@yahoo.com] 
Sent: Friday, January 25, 2013 10:41 PM
To: startrekonline@mydomain.com
Subject: World of Warcraft Diablo III Account-Notice

Greetings! startrekonline@mydomain.com 

We have already noted that you are trying to sell your personal World of Warcraft Diablo III account(s). 

Terms of Use 

It will be ongoing for further investigation by Blizzard Entertainment's employees. 

If you wish to not get your account suspended you should immediately verify your account ownership. You must complete the steps below to secure the account and your computer. 

STEP 1: ACCOUNT startrekonline@mydomain.com INVESTIGATION 
We now provide a secure website for you to verify that you have taken the appropriate steps to secure the account, your computer, and your email address. Please go to this site and follow the instructions: 
http://www.blizzard.com/support/article/securitywebform 

STEP 2: VERIFY YOUR SUBMISSION WAS RECEIVED 
We will contact you with further instructions once we have received and processed your submission. If you do not receive a reply within 48 hours of submitting this form, please resend it from the address listed above. 

Please be aware that if unauthorized access to this account, it may lead to further action against the account. 

Fare Thee Well, 

Game Master Dunarthra 
Customer Services 
Blizzard Entertainment


Normally I would disregard it as just another regular stupid phishing by script kiddies, but there was something special about this one. This one was a bit more clever, just like those new Nigerian scams — cleverly put together to not look too clever.

The trick used in this one is that it targeted current MMORPG players.

To reach MMORPG players, scammers used the database stolen from Cryptic Studios in December 2010. Cryptic is the developer behind Star Trek Online. You’ll notice in the phishing email above that they sent to an email address I used only on STO (my email was obfuscated above, but you got the idea).

Cryptic folks took more than ONE YEAR to disclose the breach publicly, supposedly detected due to an “increased security analysis” (which is management speak for: “we tried to cover it up, but somebody leaked so we had to come clean”). In April 2012 they declared that “first and last name, e-mail address, date of birth, billing address, and the first six digits and the last four digits of credit cards registered on the site may have been accessed”. Great.

This is not the first time scammers try to use Blizzard’s account system to steal your personal information, but they’re starting to use basic direct marketing tactics. I wouldn’t be surprised if they’re doing A/B testing , and the typos and grammar errors were intentional.

By the way, the author of the phishing was talktoeric911@yahoo.com, and came from Singapore. Full hearders here.

Entering Single User Mode On A Synology

I hope this will be my last post about Synology for a while.

After dealing for a few weeks with an unstable environment, then hacking a serial console to troubleshoot the issues, then cracking the secret recovery telnet password just for fun, and then solving the weird mistery of SSH not accepting /bin/bash as default shell, I think that now I have a stable environment.

Except… when I don’t.

This time, though, it was my fault.

After solving the conflict with bash, I changed all user shells on /etc/passwd to /bin/bash. The only problem is that Synology wipes the system partition during DSM upgrades, so when I upgraded to 4.1.2668, /bin/bash was gone. Of course this locked me out of the system. No SSH, SCP or FTP. Even ssh --noprofile didn’t work, as the shell didn’t exist. Great.

After a few seconds of panic, I remembered I still had the serial console. So I could put Linux in single user mode, which would drop me in recovery mode.

If you ever get yourself in the same situation, here’s the instructions to fix:

1. First, you need a serial console. This is the only annoying step, but there’s no way around it.

2. During U-Boot, press any key to cancel the automatic kernel boot (Hit any key to stop autoboot).

3. Enter printenv to check the environment variables. Search for bootargs and bootm variables (they will be different for different models and CPUs, so do NOT copy and paste, unless you have a Synology DS212+ with the same DSM):


bootargs='console=ttyS0,115200 ip=off initrd=0x00800040,4M root=/dev/md0 rw syno_hw_version=DS212pv20 ihd_num=2 netif_num=1 esata_7042=1'
...
bootcmd='bootm F8080000 F8280000'


4. You now need to append reboot=cold,hard emergency init=/bin/sh to the end of bootargs variable. In my case, this is what I’d use:

    
setenv bootargs 'console=ttyS0,115200 ip=off initrd=0x00800040,4M root=/dev/md0 rw syno_hw_version=DS212pv20 ihd_num=2 netif_num=1 esata_7042=1 reboot=cold,hard emergency init=/bin/sh'


5. Now you can boot your kernel normally, via


bootm F8080000 F8280000


Done. That’s all you need. Now your Synology will boot normally in single user mode, and drop you to a /bin/sh, regardless of /etc/passwd. Just do what you have to do to fix the system, and then reboot normally.

This can also be used to try to recover your system partition, if you screwed up in any other way.

Going Down the Rabbit Hole - Chasing Bugs on Synology’s OpenSSH

Going Down the Rabbit Hole - Chasing Bugs on Synology's OpenSSH

I’ve been spending my evenings for the past few weekends trying to fix an odd problem with SSH on my Synology DS212+. In a nutshell, I can’t set the shell of any user other than root to anything different than /bin/sh or /bin/ash. Specifically, I’d like to set my own shell to /bin/bash, for multiple reasons.

It makes absolutely no sense. The logins are terminated with “Permission denied, please try again.”. Permission denied? WTF!

I did tons of testing trying to isolate the problem. No, it wasn’t config, it wasn’t permissions, it wasn’t sshd_config nor PAM modules. I even cross-compiled bash. You can see all the tests I did here.

The only thing that was left to test: OpenSSH’s source code.

Thankfully Synology distributes the source code under GPL, so I was able to dive into the code and discover exactly what was going on.

The OpenSSH version used by Synology is a highly customized version, and it does not behave like the original code. It has lots of hacks and ad-hoc customizations - e.g., additional checking before accepting a login to see if the SSH service is enabled within the web interface, or stripping special chars (;, |, ‘) from rsync commands, or… wait for it… avoiding regular users to use a shell different than /bin/sh or /bin/ash.

Yeah, it is hard coded within the binary.

Here’s the piece of code from their version of OpenSSH 5.8p1, file session.c:


void do_child(Session *s, const char *command)
{
...

#ifdef MY_ABC_HERE
   char szValue[8];
   int RunSSH = 0;
   SSH_CMD SSHCmd = REQ_UNKNOWN;

   if (1 == GetKeyValue("/etc/synoinfo.conf", "runssh", szValue, sizeof(szValue))) {
           if (strcasecmp(szValue, "yes") == 0) {
                   RunSSH = 1;
           }
   }

   if (IsSFTPReq(command)){
           SSHCmd = REQ_SFTP;
   } else if (IsRsyncReq(command)){
           SSHCmd = REQ_RSYNC;
   } else if (IsTimebkpRequest(command)){
           SSHCmd = REQ_TIMEBKP;
   } else if (RunSSH && IsAllowShell(pw)){
           SSHCmd = REQ_SHELL;
   } else {
           goto Err;
   }

   if (REQ_RSYNC == SSHCmd) {
           pw = SYNOChgValForRsync(pw);
   }
   if (!SSHCanLogin(SSHCmd, pw)) {
           goto Err;
   }
   goto Pass;

 Err:
   fprintf(stderr, "Permission denied, please try again.\n");
   exit(1);

 Pass:
   #endif /* MY_ABC_HERE */
...
}



As you can imagine, the IsAllowShell(pw) was the culprit:


static int IsAllowShell(const struct passwd *pw)
{
     struct passwd *pUnPrivilege = NULL;
     char *szUserName = NULL;
     if (!pw || !pw->pw_name) {
             return 0;
     }
     szUserName = pw->pw_name;
     if(!strcmp(szUserName, "root") || !strcmp(szUserName, "admin")){
             return 1;
     }
     if (NULL != (pUnPrivilege = getpwnam(szUserName))){
             if (!strcmp(pUnPrivilege->pw_shell, "/bin/sh") || 
                     !strcmp(pUnPrivilege->pw_shell, "/bin/ash")) {
                     return 1;
             }
     }
     return 0;
}



No wonder why I was experiencing such an odd behavior. Only /bin/sh and /bin/ash shells would be accepted for users different than root or admin. And this regardless of the uid (I had tested also making joeuser uid=0, and it didn’t work. Now it’s obvious why).

Once identified the cause, the fix was easy: just remove the call to IsAllowShell(). It took me a while to the right configuration to cross-compile openssh and all its dependencies, but in the end it worked well.

If anyone is interested in cross-compiling OpenSSH - or any other kernel modules for the Synology - here’s my version of the modified Makefile. It was tested with OpenSSH-5.8p1 from DSM4.1 source code, branch 2636, on models with Marvell Kirkwood mv6281/mv6282 CPU (like DS212+). I’m running Ubuntu 12.10 x64.

Bottom line: bad practice, terrible code, and a great example of what not to do. I understand sometimes OEMs need to develop special customizations for their products, but they should think twice before going the rabbit hole. Not only this results in unmaintainable code for them, but also creates all sorts of unforeseen issues down the road for users.

Thankfully there’s GPL to keep them honest - and open.

Synology’s “secret” telnet password

If you have a Synology NAS and had some sort of disk crash in the past, you’ve probably encountered the dreary “Cannot format system partition” and “Please configure your router to forward port 23 to DiskStation and contact Synology online support”.

Yeah, it sucks. It sucks even more when you know the disk is perfectly fine, and you still have hope to recover your data. Or you simply don’t like the idea of having your port 23 open to the world for god-knows-how-long until Synology tech support can look into your case.

If you’re a savvy user, you’ve probably tried telneting to your NAS. Heck, if you are a savvy user maybe you already opened the case and connected the serial port, only to be discover that you don’t have the password for root. The one you just entered on DS Assistant doesn’t work, and you exhausted all obvious guesses - blank, synopass, synology, password, admin, root, etc.

Well, what about c12-0804? That’s the password today. But if you’re reading this a few days from now, bad luck; it won’t work. Unless it’s again December 8th, on any future year.

That’s because Synology hacked the login within the embedded firmware that starts before your system partition is installed, in order to accept a dynamically generated password for root, that changes every day.

In theory only Synology folks would have the password. Well… Synology and anybody else that care to look at the source code, more specifically at the file synogpl-2636-6281\source\busybox-1.16.1\libbb\correct_password.c. I put the original file on Gist, if you want to take a look.

Based on the original source, I hacked a short snippet to generate the daily password. Without further due, here’s it is:


#include <stdlib.h> 
#include <time.h> 
#include <stdio.h> 

void main()
{
    struct timeval tvTime;
    struct tm tmOutput;

    gettimeofday(&tvTime, 0);
    localtime_r(&(tvTime.tv_sec), &tmOutput);

    tmOutput.tm_mon += 1;
    printf("password for today is: %x%02d-%02x%02d\n\n",
        tmOutput.tm_mon, tmOutput.tm_mon, tmOutput.tm_mday,
        gcd(tmOutput.tm_mon, tmOutput.tm_mday));
}

int gcd(int a, int b)
{
    return (b?gcd(b,a%b):a);
}


Fire your gcc and compile the code above, and you’ll get the password for today. Or use one of the several online C compilers. Here’s the code using the excellent Codepad.

Bonus tip: if you’re curious how exactly the password is generated, or want to be able to simply infer it quickly without running any code, here’s the formula:

  • 1st character = month in hexadecimal, lower case (1=Jan, … , a=Oct, b=Nov, c=Dec)
  • 2-3 = month in decimal, zero padded and starting in 1 (01, 02, 03, …, 11, 12)
  • 4 = dash
  • 5-6 = day of the month: 01, 02,.., 31 EDIT: day of the month in hex (01, 02 .., 0A, .., 1F)
  • 7-8 = greatest common divisor between month and day, zero padded. This is always a number between 01 and 12.

So, let’s say today is October 15, the password would be: a10-0f05 (a = month in hex, 10 = month in dec, 0f = day in hex, 05 = greatest divisor between 10 and 15).

You shouldn’t have much trouble calculating the common divisor (otherwise you wouldn’t be reading this), but if you just want to double check your calculation Wolfram Alpha is your friend.

Note: this was tested on a Synology DS212+, which has a Marvell Kirkwood mv6282 processor. It may be possible (unlikely, but still possible) that other models use a different algorithm, so your mileage may vary. If that’s the case, you can always check the source code.

Recovering a Failed Synology Diskstation DS2xx + Serial Console

Synology Serial Console

I thought I’d post this here for anyone looking for help on troubleshooting a failed Synology Diskstation NAS.

I’m a happy user of a Synology DS-212+, with RAID1 and 2x2TB. The software is ten times better than the limited and buggy Drobo Dashboard, and the fact that it is entirely open source is a big plus — the device runs Linux 2.6.32 on ARM, the RAID system is basically md + lvm, and their software is (relatively) open source.

Disclaimer: make sure you have backup before you touch your disks! I am not responsible if you lose all your data, void your warranty, burn your house or kill your dog.

Keep in mind that I have a daily on-site and another offsite back to Amazon Glacier (using the excellent CloudBerry Online Backup, Server edition. So I’m not afraid of messing up with my life collection of photos, emails and archives. Your mileage may vary, so proceed accordingly.

I recently upgraded the firmware to DSM 2661. Everything worked fine, for 10-12 hours. Next morning, it was dead. Just the power led blinking (Blue Blink of Death). Was it the firmware upgrade? Was it an unfortunate coincidence with a disk crash? Who knows.

The basic motherboard test (by removing both disks and waiting 30s for a long beep) indicated that the DS was still alive. It also responded to ping and showed up on DS Assistant, so it wasn’t the motherboard.

Thankfully, nothing on Synology is proprietary, so you can mount the disks and read your data on any Linux platform. I connected one of the disks to my standard Ubuntu distro, and everything was there (funny: a mere ten years ago, this would be like science fiction. RAIDs were all proprietary and data recovery was almost impossible, unless you paid several thousands of dollars to a specialized company).

Below you have a brain dump of my progress. If you prefer, you can also use a virtual machine — I tested on both VMWare Workstation 8 and Oracle’s VirtualBox, by connecting the disk in raw mode (but be extra careful to not select the wrong disk, or you can trash your host operating system. If you’re on a Windows host, wmic diskdrive list is your friend).


# install md and lvm2 packages, if needed
apt-get install mdadm lvm2

# check status of md before anything. Discover where is your
# disks (i.e., /dev/sdaX)
fdisk -l
cat /proc/mdstat

# check partitions
sfdisk -l /dev/sdaX

# check the status of the RAID. Hopefully everything will be fine
lvscan
mdadm --examine --scan /dev/sdaX

# mount the raid
mdadm -A -s

# if all good, set volgroup as active (if needed, in the case it's
# set as inactive due to a crash) and proceed to mount
vgchange -a y
mount -o ro /dev/vg1/volume_1 /mnt

# to dismount the RAID
umount /mnt
vgchange -an
mdadm --stop /dev/mdXXX


# Note:
# It's *strongly* recommended to save your /etc/lvm/backup/*. It'll be
# handy if you screw up later on. Trust me, I erased ALL partitions
# and screwed up the RAID, and was still able to recover everything
# just by using the saved metadata.
# 
# To recreate the LVM metadata: (vg1 is the name of the old metadata)
# pvcreate --uid "...." --restorefile vg1 /dev/md126 -ff
# vgcfgrestore vg1


Everything was back online, so I rebuilt the RAID using a spare disk. Life is good.

Till it crashed again the next day.

Clearly there was something crashing the system partition. I needed to see inside the NAS, well before the kernel is fully booted and sshd is initiated. I needed a serial console.

Thankfully, Synology folks kindly put a serial port there. It’s not documented, but it’s not hard to find once you manage to open the case. Of course, keep in mind that this will likely void your warranty. And do not proceed unless you really know what you’re doing.

  • Start by opening the NAS. Here’s a good video showing how to open the case. Be aware this may break some small internal hooks, and you’ll need to use tape or hot glue to put it back together (what’s wrong with manufacturers these days? Why not just some good old screws? Phew)
  • Inside the case, look for a 6-pin header, normally labeled JP2 (or COM1 on older models).
  • The pins are:
Pin Number Function
Confirmed on Synology DS212+  
13.3V
2GND
4TX
6RX
  • Now connect the pins 2, 4 and 6 (respectively GNS, TX, RX) to your USB-TTL 3v3 cable (if using the FTDI cable from Adafruit, it’ll be 1-black, 5-yellow, 4-orange. Make sure you don’t short-circuit any of the pins. These male-female jumper wires could be useful.
  • Open your preferred terminal program (ExtraPutty is the best in town), set to 115200, disable xon/xoff, and you’re all set.

Now you can turn on your DS, and see all the beauty of what’s going on under the hood. Here’s the output of mine (including connecting one of the disks at the 118s mark):


         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** LOADER **
 ** MARVELL BOARD: Synology Disk Station LE

U-Boot 1.1.4 (Dec  2 2011 - 15:56:02) Marvell version: 3.5.9

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 0068B3D4

Soc: 88F6282 A1CPU running @ 2000Mhz L2 running @ 500Mhz
SysClock = 500Mhz , TClock = 200Mhz

DRAM (DDR3) CAS Latency = 7 tRP = 7 tRAS = 20 tRCD=7
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
Using default environment

[4096kB@f8000000] Flash:  4 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
PEX 1: PCI Express Root Complex Interface
PEX interface detected Link X1

Synology Model: DS212+r1
Fan Status: Good

Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
## Booting image at f8080000 ...
   Image Name:   Linux-2.6.32.12
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1476672 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at f8280000 ...
   Image Name:   synology_88f6282_212+ 2661
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    677043 Bytes = 661.2 kB
   Load Address: 00800000
   Entry Point:  00800000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Linux version 2.6.32.12 (root@build3) (gcc version 4.2.1) #2661 Mon Nov 12 23:10:15 CST 2012
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Synology 6282 board
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Sys Clk = 200000000, Tclk = 166666667
[    0.000000] Synology Board ID: 27
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 130048
[    0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x00800040,4M root=/dev/md0 rw     syno_hw_                                          version=DS212pv20 ihd_num=2 netif_num=1 esata_7042=1
[    0.000000] Synology Hareware Version: DS212pv20-j
[    0.000000] Internal HD num: 2
[    0.000000] Internal netif num: 1
[    0.000000] Esata chip use 7042: 1
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 256MB 256MB = 512MB total
[    0.000000] Memory: 506880KB available (3508K code, 530K data, 124K init, 0K highmem)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:128
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Calibrating delay loop... 1985.74 BogoMIPS (lpj=9928704)
[    0.250000] Mount-cache hash table entries: 512
[    0.250000] CPU: Testing write buffer coherency: ok
[    0.250000] xor: measuring software checksum speed
[    0.300000]    arm4regs  :  1688.400 MB/sec
[    0.350000]    8regs     :  1372.400 MB/sec
[    0.400000]    32regs    :  1477.600 MB/sec
[    0.400000] xor: using function: arm4regs (1688.400 MB/sec)
[    0.400000] NET: Registered protocol family 16
[    0.400000] Feroceon L2: Enabling L2
[    0.400000] Feroceon L2: Cache support initialised, in WT override mode.
[    0.420000]
[    0.420000] CPU Interface
[    0.420000] -------------
[    0.420000] SDRAM_CS0 ....base 00000000, size 256MB
[    0.420000] SDRAM_CS1 ....base 10000000, size 256MB
[    0.420000] SDRAM_CS2 ....disable
[    0.420000] SDRAM_CS3 ....disable
[    0.420000] PEX0_MEM ....base e0000000, size 128MB
[    0.420000] PEX0_IO ....base f2000000, size   1MB
[    0.420000] PEX1_MEM ....base e8000000, size 128MB
[    0.420000] PEX1_IO ....base f2100000, size   1MB
[    0.420000] INTER_REGS ....base f1000000, size   1MB
[    0.420000] NFLASH_CS ....base fa000000, size   2MB
[    0.420000] SPI_CS ....base f4000000, size  16MB
[    0.420000] BOOT_ROM_CS ....no such
[    0.420000] DEV_BOOTCS ....no such
[    0.420000] CRYPT_ENG ....base f0000000, size   2MB
[    0.420000]  Detected Tclk 200000000 and SysClk 500000000
[    0.420000] Apply DS 212 GPIO
[    0.420000] Synology 6282 1, 2 bay GPIO Init
[    0.420000] PCIe link is enable, apply PCIe workaround
[    0.920000] PEX0 interface detected Link X4
[    1.420000] PEX1 interface detected Link X1
[    1.420000] PCI: bus0: Fast back to back transfers disabled
[    1.420000] pci 0000:01:01.0: PME# supported from D0 D3hot
[    1.420000] pci 0000:01:01.0: PME# disabled
[    1.420000] PCI: bus1: Fast back to back transfers disabled
[    1.430000] bio: create slab  at 0
[    1.430000] vgaarb: loaded
[    1.430000] SCSI subsystem initialized
[    1.600000] raid6: int32x1    141 MB/s
[    1.770000] raid6: int32x2    169 MB/s
[    1.940000] raid6: int32x4    197 MB/s
[    2.110000] raid6: int32x8    175 MB/s
[    2.110000] raid6: using algorithm int32x4 (197 MB/s)
[    2.110000] Switching to clocksource kw_clocksource
[    2.110000] NET: Registered protocol family 2
[    2.110000] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[    2.110000] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[    2.110000] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[    2.110000] TCP: Hash tables configured (established 16384 bind 16384)
[    2.110000] TCP reno registered
[    2.110000] NET: Registered protocol family 1
[    2.110000] RPC: Registered udp transport module.
[    2.110000] RPC: Registered tcp transport module.
[    2.110000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    2.110000] Trying to unpack rootfs image as initramfs...
[    2.720000] rootfs image is not initramfs (no cpio magic); looks like an initrd
[    2.730000] Freeing initrd memory: 4096K
[    2.730000] XOR registered 4 channels
[    2.730000] XOR 2nd invalidate WA enabled
[    2.730000] VFS: Disk quotas dquot_6.5.2
[    2.730000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    2.730000] msgmni has been set to 998
[    2.730000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[    2.730000] io scheduler noop registered
[    2.730000] io scheduler anticipatory registered (default)
[    2.740000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    2.740000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    2.750000] console [ttyS0] enabled
[    2.760000] serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
[    2.770000] brd: module loaded
[    2.770000] sata_mv sata_mv.0: version 1.28
[    2.770000] sata_mv sata_mv.0: slots 32 ports 2
[    2.780000] scsi0 : sata_mv
[    2.780000] scsi1 : sata_mv
[    2.790000] ata1: SATA max UDMA/133 irq 21
[    2.790000] ata2: SATA max UDMA/133 irq 21
[    6.140000] ata1: SATA link down (SStatus 0 SControl F300)
[    9.140000] Delay 5 seconds to wait for disk 2 ready.
[   19.320000] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[   19.520000] ata2.00: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133
[   19.520000] ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   19.570000] ata2.00: configured for UDMA/133
[   19.570000] scsi 1:0:0:0: Direct-Access     WDC      WD20EARX-00PASB0 51.0 PQ: 0 ANSI: 5
[   19.580000] sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[   19.590000] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[   19.590000] sd 1:0:0:0: [sdb] Write Protect is off
[   19.600000] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   19.610000]  sdb: sdb1 sdb2
[   19.620000] sd 1:0:0:0: [sdb] Attached SCSI disk
[   19.630000] sata_mv 0000:00:01.0: version 1.28
[   19.630000] PCI: enabling device 0000:00:01.0 (0140 -> 0143)
[   19.640000] sata_mv 0000:00:01.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
[   19.650000] scsi2 : sata_mv
[   19.650000] scsi3 : sata_mv
[   19.650000] scsi4 : sata_mv
[   19.660000] scsi5 : sata_mv
[   19.660000] ata3: SATA max UDMA/133 mmio m1048576@0xe0000000 port 0xe0022000 irq 9
[   19.670000] ata4: SATA max UDMA/133 mmio m1048576@0xe0000000 port 0xe0024000 irq 9
[   19.670000] ata5: SATA max UDMA/133 mmio m1048576@0xe0000000 port 0xe0026000 irq 9
[   19.680000] ata6: SATA max UDMA/133 mmio m1048576@0xe0000000 port 0xe0028000 irq 9
[   20.040000] ata3: SATA link down (SStatus 0 SControl 300)
[   20.390000] ata4: SATA link down (SStatus 0 SControl 300)
[   20.740000] ata5: SATA link down (SStatus 0 SControl 300)
[   21.090000] ata6: SATA link down (SStatus 0 SControl 300)
[   21.090000] physmap platform flash device: 00400000 at f8000000
[   21.100000] SPI Serial flash detected @ 0xf8000000, 4096KB (64sec x 64KB)
[   21.110000] Searching for RedBoot partition table in SYNOMTD-0 at offset 0x3f0000
[   21.120000] 6 RedBoot partitions found on MTD device SYNOMTD-0
[   21.120000] SYNOMTD flash bank 0: Using RedBoot partition definition
[   21.130000] Creating 6 MTD partitions on "SYNOMTD-0":
[   21.140000] 0x000000000000-0x000000080000 : "RedBoot"
[   21.140000] 0x000000080000-0x000000280000 : "zImage"
[   21.150000] 0x000000280000-0x0000003c0000 : "rd.gz"
[   21.150000] 0x0000003c0000-0x0000003d0000 : "vendor"
[   21.160000] vender Mac1 checksum error ucSum:0x00 Buf:0x00 Sum:0.
[   21.160000] vender Mac2 checksum error ucSum:0x00 Buf:0x00 Sum:0.
[   21.170000] vender Mac3 checksum error ucSum:0x00 Buf:0x00 Sum:0.
[   21.180000] Serial Number: C1KNNxxxxx
[   21.180000] 0x0000003d0000-0x0000003f0000 : "RedBoot Config"
[   21.190000] 0x0000003f0000-0x000000400000 : "FIS directory"
[   21.190000] SPI Serial flash detected @ 0xf4000000, 4096KB (64sec x 64KB)
[   21.200000] cmdlinepart partition parsing not available
[   21.210000] Loading Marvell Ethernet Driver:
[   21.210000]   o Cached descriptors in DRAM
[   21.220000]   o DRAM SW cache-coherency
[   21.220000]   o 2 Giga ports supported
[   21.220000]   o Single RX Queue support - ETH_DEF_RXQ=0
[   21.230000]   o Single TX Queue support - ETH_DEF_TXQ=0
[   21.230000]   o TCP segmentation offload (TSO) supported
[   21.240000]   o Receive checksum offload supported
[   21.240000]   o Transmit checksum offload supported
[   21.250000]   o SKB Recycle supported - (Enabled)
[   21.250000]   o Rx descripors: q0=128
[   21.260000]   o Tx descripors: q0=532
[   21.260000]   o Loading network interface(s):
[   21.270000]     o  register under mv88fx_eth platform
[   21.270000]     o eth0, ifindex = 2, GbE port = 0
[   21.280000]     o eth0, phy chipid = 1410e90, Support WOL = 32
[   21.280000]
[   21.280000] md: linear personality registered for level -1
[   21.290000] md: raid0 personality registered for level 0
[   21.290000] md: raid1 personality registered for level 1
[   21.300000] md: raid10 personality registered for level 10
[   21.310000] md: raid6 personality registered for level 6
[   21.310000] md: raid5 personality registered for level 5
[   21.320000] md: raid4 personality registered for level 4
[   21.320000] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[   21.330000] cpuidle: using governor ladder
[   21.330000] TCP cubic registered
[   21.340000] NET: Registered protocol family 17
[   21.340000] md: Waiting for all devices to be available before autodetect
[   21.350000] md: If you don't use raid, use raid=noautodetect
[   21.360000] md: Autodetecting RAID arrays.
[   21.370000] md: Scanned 2 and added 2 devices.
[   21.380000] md: autorun ...
[   21.380000] md: considering sdb1 ...
[   21.390000] md:  adding sdb1 ...
[   21.390000] md: sdb2 has different UUID to sdb1
[   21.390000] md: created md0
[   21.400000] md: bind
[   21.400000] md: running: 
[   21.400000] raid1: raid set md0 active with 1 out of 2 mirrors
[   21.410000] md0: detected capacity change from 0 to 2549940224
[   21.410000] md: considering sdb2 ...
[   21.420000] md:  adding sdb2 ...
[   21.420000] md: created md1
[   21.420000] md: bind
[   21.430000] md: running: 
[   21.430000] raid1: raid set md1 active with 1 out of 2 mirrors
[   21.440000] md1: detected capacity change from 0 to 2147418112
[   21.440000] md: ... autorun DONE.
[   21.450000] RAMDISK: lzma image found at block 0
[   22.130000] VFS: Mounted root (ext2 filesystem) on device 1:0.
START /linuxrc.syno
[   22.150000] ds212+_synobios: module license 'Synology Inc.' taints kernel.
[   22.160000] Disabling lock debugging due to kernel taint
[   22.200000] correction with 0x0f
[   22.260000] synobios: load, major number 201
[   22.260000] Brand: Synology
[   22.270000] Model: DS-212+
[   22.270000] This is default settings: set group disks wakeup number to 1, spinup time deno 1
mknod: /dev/synobios: File exists
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
[   22.300000] synobios: unload
Partition Version=7
 /sbin/e2fsck exists, checking /dev/md0...
[   22.340000]  md0: unknown partition table

   16112 inodes used (10.35%)
       3 non-contiguous files (0.0%)
       2 non-contiguous directories (0.0%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 13447/1
  117302 blocks used (18.84%)
       0 bad blocks
       1 large file

   11628 regular files
    1818 directories
     146 character device files
    1805 block device files
       0 fifos
       3 links
     704 symbolic links (702 fast symbolic links)
       2 sockets
--------
   16106 files
/sbin/e2fsck returns 0
Mounting /dev/md0 /tmpRoot
[   23.070000] EXT4-fs (md0): barriers disabled
[   23.080000] EXT4-fs (md0): mounted filesystem with ordered data mode
------------upgrade
use default /dev/md0
Begin upgrade procedure
No upgrade file exists
End upgrade procedure
============upgrade
/dev/md0 /tmpRoot ext4 rw,relatime,barrier=0,journal_checksum,data=ordered 0 0
[   23.450000] synoacl module [synoacl_ext4] is not loaded
[   23.450000] synoacl module [synoacl_vfs] is not loaded
none /sys sysfs rw,relatime 0 0
linuxrc.syno executed successfully.
[   23.490000] EXT3-fs: md0: couldn't mount because of unsupported optional features (240).
[   23.490000] EXT2-fs: md0: couldn't mount because of unsupported optional features (240).
[   23.510000] EXT4-fs (md0): barriers disabled
[   23.530000] EXT4-fs (md0): mounted filesystem with ordered data mode
[   23.530000] VFS: Mounted root (ext4 filesystem) on device 9:0.
[   23.540000] Trying to move old root to /initrd ... okay
[   23.560000] Freeing init memory: 124K
:: Starting /etc/rc
:: Prepare var ... [  OK  ]
:: Mounting procfs ... [  OK  ]
:: Mounting tmpfs ... [  OK  ]
:: Mounting devpts ... [  OK  ]
:: Mounting sysfs ... [  OK  ]
:: Checking new disks ...
No new disk. Do nothing.
[   25.450000]  md1: unknown partition table
[   25.470000] Adding 2097080k swap on /dev/md1.  Priority:-1 extents:1 across:2097080k
/dev/root on / type ext4 (rw,relatime,barrier=0,journal_checksum,data=ordered)
/tmp on /tmp type tmpfs (0)
none on /dev/pts type devpts (gid=4,mode=620)
/sys on /sys type sysfs (0)
Hostname DiskStation
192.168.3.121   DiskStation
:: Loading module ipv6[   25.780000] NET: Registered protocol family 10
[   25.780000] lo: Disabled Privacy Extensions
 ... [  OK  ]
:: Loading module llc ... [  OK  ]
:: Loading module psnap ... [  OK  ]
:: Loading module sg[   25.870000] sd 1:0:0:0: Attached scsi generic sg0 type 0
 ... [  OK  ]
:: Loading module usbcore[   26.000000] usbcore: registered new interface driver usbfs
[   26.010000] usbcore: registered new interface driver hub
[   26.010000] usbcore: registered new interface driver ethub
[   26.040000] usbcore: registered new device driver usb
 ... [  OK  ]
:: Loading module quota_tree ... [  OK  ]
:: Loading module quota_v2 ... [  OK  ]
:: Loading module crc-ccitt ... [  OK  ]
:: Loading module crc-itu-t ... [  OK  ]
:: Loading module dm-snapshot ... [  OK  ]
:: Loading module freq_table ... [  OK  ]
:: Loading module cpufreq_stats ... [  OK  ]
:: Loading module cpufreq[   26.190000] cpufreq: Init kirkwood cpufreq driver
 ... [  OK  ]
:: Loading module crypto_algapi ... [  OK  ]
:: Loading module crypto_wq ... [  OK  ]
:: Loading module crypto_blkcipher ... [  OK  ]
:: Loading module crypto_hash ... [  OK  ]
:: Loading module aead ... [  OK  ]
:: Loading module pcompress ... [  OK  ]
:: Loading module cryptomgr ... [  OK  ]
:: Loading module cbc ... [  OK  ]
:: Loading module md5[   26.410000] alg: No test for md5 (md5-generic)
 ... [  OK  ]
:: Loading module aes_generic[   26.440000] alg: No test for aes (aes-generic)
 ... [  OK  ]
:: Loading module rng ... [  OK  ]
:: Loading module ansi_cprng[   26.480000] alg: No test for stdrng (ansi_cprng)
 ... [  OK  ]
:: Loading module krng[   26.490000] alg: No test for stdrng (krng)
 ... [  OK  ]
:: Loading module eseqiv ... [  OK  ]
:: Loading module crc32c[   26.530000] alg: No test for crc32c (crc32c-generic)
 ... [  OK  ]
:: Loading module des_generic[   26.550000] alg: No test for des (des-generic)
[   26.560000] alg: No test for des3_ede (des3_ede-generic)
 ... [  OK  ]
:: Loading module chainiv ... [  OK  ]
:: Loading module ocf ... [  OK  ]
:: Loading module cryptodev ... [  OK  ]
:: Loading module cesa_dev[   26.640000] cesadev_init(bf182000)
 ... [  OK  ]
:: Loading module cesa_ocf_drv[   26.660000] mvCesaInit: sessions=10240, queue=64, pSram=f0000000
 ... [  OK  ]
:: Loading module ecb ... [  OK  ]
:: Loading module sha1_generic[   26.710000] alg: No test for sha1 (sha1-generic)
 ... [  OK  ]
:: Loading module sha256_generic[   26.720000] alg: No test for sha224 (sha224-generic)
[   26.730000] alg: No test for sha256 (sha256-generic)
 ... [  OK  ]
:: Loading module sha512_generic[   26.750000] alg: No test for sha384 (sha384-generic)
[   26.760000] alg: No test for sha512 (sha512-generic)
 ... [  OK  ]
:: Loading module ecryptfs[   26.810000] encryptfs using the OCF package.
 ... [  OK  ]
:: Loading module cryptosoft ... [  OK  ]
:: Loading module fat ... [  OK  ]
:: Loading module vfat ... [  OK  ]
:: Loading module fuse[   26.970000] fuse init (API version 7.13)
 ... [  OK  ]
:: Loading module hfsplus ... [  OK  ]
:: Loading module synoacl_vfs ... [  OK  ]
:: Loading module synoacl_ext4 ... [  OK  ]
:: Mounting usbfs ... [  OK  ]
:: Loading module sky2[   27.110000] sky2 driver version 1.25
 ... [  OK  ]
:: Loading module synobios[   27.200000] correction with 0x0f
[   27.250000] synobios: load, major number 201
[   27.260000] Brand: Synology
[   27.260000] Model: DS-212+
[   27.260000] This is default settings: set group disks wakeup number to 1, spinup time deno 1
 ... [  OK  ]
synochecknetworkcfg: Pass
[   27.600000] eth0: mac address changed
[   29.670000] eth0: link down
[   29.670000] eth0: started
[   29.670000] ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0      Link encap:Ethernet  HWaddr 00:11:32:11:18:F3
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:11

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
      [   30.730000] eth0: link up    inet6 addr: , full duplex::1/128 Scope:Ho, speed 1 Gbpsst
          UP
 LOOPBACK RUNNIN[   30.740000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
G  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ls: /etc/dhcpd/dhcpd-*.conf: No such file or directory
ls: /etc/dhcpd/dhcpd-*.info: No such file or directory
grep: /etc/dhcpd/dhcpd.info: No such file or directory
kernel.panic = 3
:: Starting syslogd ... [  OK  ]
Pass s00_synocheckfstab ...
Pass CheckSynoinfo ...
Pass CheckUser
Pass CheckSmbConf ...
Pass CheckCronTab ...
Pass CheckGroup.
Pass s62_synocheckapple ...
start findhostd
synokerneltz: set kernel time zone to 300
kernel.core_pattern = /volume1/@%e.core
fs.suid_dumpable = 2
vm.min_free_kbytes = 8192
:: Starting scemd
[   37.980000] ata2.00: configured for UDMA/133
[   37.980000] ata2: EH complete
:: Starting services in background
[   38.170000] ata2.00: Disable disk write cache in EH:: Loading module ehci-hcd
[   38.270000] ata2.00: configured for UDMA/133
[   38.270000] ata2: EH complete
[   38.270000] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   38.310000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   38.310000] orion-ehci orion-ehci.0: Marvell Orion EHCI
[   38.320000] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   38.360000] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   38.380000] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   38.380000] usb usb1: configuration #1 chosen from 1 choice
[   38.400000] hub 1-0:1.0: USB hub found
[   38.400000] hub 1-0:1.0: 1 port detected
 ... [  OK  ]
:: Loading module ohci-hcd[   38.510000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
 ... [  OK  ]
:: Loading module xhci-hcd[   38.600000] xhci_hcd 0000:01:01.0: xHCI Host Controller
[   38.610000] xhci_hcd 0000:01:01.0: new USB bus registered, assigned bus number 2
[   38.610000] xhci_hcd 0000:01:01.0: irq 10, io mem 0xe8000000
[   38.680000] usb usb2: No SuperSpeed endpoint companion for config 1  interface 0 altsetting 0 ep 129: using minimum values
[   38.730000] usb usb2: configuration #1 chosen from 1 choice
[   38.730000] hub 2-0:1.0: USB hub found
[   38.740000] hub 2-0:1.0: 4 ports detected
[   38.740000] usb 1-1: new high speed USB device using orion-ehci and address 2
 ... [  OK  ]
:: Loading module etxhci-hcd[   38.930000] Got empty serial number. Generate serial number from product.
[   38.940000] usb 1-1: configuration #1 chosen from 1 choice
[   38.950000] hub 1-1:1.0: USB hub found
[   38.950000] hub 1-1:1.0: 4 ports detected
 ... [  OK  ]
:: Loading module usb-storage[   39.070000] Initializing USB Mass Storage driver...
[   39.080000] usbcore: registered new interface driver usb-storage
[   39.090000] USB Mass Storage support registered.
 ... [  OK  ]
:: Loading module usblp[   39.240000] usb 1-1.4: new high speed USB device using orion-ehci and address 3
[   39.250000] usbcore: registered new interface driver usblp
No rules exists, remove tc modules...
cat: can't open '/proc/net/ip6_tables_names': No such file or directory
Tc modules has not been started...
cat: can't open '/proc/net/ip_tables_names': No such file or directory
 ... [  OK  ]
:: Loading module hid[   39.350000] usb 1-1.4: configuration #1 chosen from 1 choice
[   39.360000] scsi6 : SCSI emulation for USB Mass Storage devices
Tc modules has not been started...
 ... [  OK  ]
:: Loading module usbhid[   39.600000] usbcore: registered new interface driver hiddev
[   39.660000] usbcore: registered new interface driver usbhid
[   39.660000] usbhid: v2.6:USB HID core driver
 ... [  OK  ]
startup daemons
Sat Dec  1 22:12:31 EST 2012

 Disk Usage Status:
        [sdb]
 --------------------------------
 [md0]:  [1]
 [md1]:  [1]
 Partition Layout Version:
/dev/sdb: [V7]
synocheckvolume: Pass
synocheckshare: Pass SYNOICheckShare()
synocheckshare: Pass SYNOICheckShareExt()
synocheckshare: Pass SYNOICheckServiceLink()
synocheckshare: Pass SYNOICheckAutoDecrypt()
synocheckshare: Pass SYNOIServiceShareEnableDefaultDS()
synocheckiscsitrg: Pass
synobootup: BEGIN
synobootup: END
Starting Hotplug Handling Daemon ...

DiskStation login: Starting inetd...
Starting crond...
 Starting Snmpd
synorelayd is not configured
MySQL is not enabled. Skip...
Syslog setting file does not exist!
Syslog-ng server start...
Client/Server is both disabled
PGSQL service is disabled. Skip...
CUPS: Starting cupsd...
CUPS: Never Start CUPS until volume exist...
GCP: cupsd not running, skip start gcpd
start S2S daemons ...
Starting Synology File Indexing Daemon ...
PGSQL service is disabled. Skip...
Starting Synology Make Thumb Daemon...
[   44.460000] scsi 6:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9910 PQ: 0 ANSI: 0
[   44.470000] sd 6:0:0:0: Attached scsi generic sg1 type 0
[   44.490000] scsi 6:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9910 PQ: 0 ANSI: 0
[   44.520000] sd 6:0:0:0: [sdq] Attached SCSI removable disk
[   44.590000] sd 6:0:0:1: Attached scsi generic sg2 type 0
[   44.610000] sd 6:0:0:1: [sdr] Attached SCSI removable disk
:: Running lunbackup garbage collection ... [  OK  ]
:: No iSCSI targets enabled, skip it.
:: No iSCSI VAAI lun in trash can, skip it.
remove temp tdbs
start nmbd ... ok
start smbd ...
check tdb: /usr/syno/etc/private/secrets.tdb ... done
check tdb: /var/run/account_policy.tdb ... done
check tdb: /var/run/share_info.tdb ... done
check tdb: /var/run/registry.tdb ... done
done
Load loop.ko ...
[   46.840000] loop: module loaded
Load isofs.ko ...
Load udf.ko ...
Load cifs.ko ...
[   47.740000] Slow work thread pool: Starting up
[   48.070000] Slow work thread pool: Ready
Starting Netatalk services (this will take a while):
 cnid_metad afpd (DiskStation:AFPServer).
NFS server is not enabled. Skip...
Starting Synology Make FLV Daemon ...
Start SSH...

 Starting Synosnmpcd
Start System Apache Server .....  -f /usr/syno/apache/conf/httpd.conf-sys
/usr/syno/etc/rc.d/S97apache-sys.sh: system httpd started
Start User Apache Server .....
/usr/syno/etc/rc.d/S97apache-user.sh: user httpd started
LoadModule synobandwidth_module modules/mod_synobandwidth.so
start findhostd
/var/spool/synoeaupgrade.list doesn't exist!
Stop upgarde
We only disalbe WD idle3 timer when DS down, please call /usr/syno/etc/rc.d/S99WDidle3Dis.sh stop
Starting Avahi mDNS/DNS-SD Daemon
SFTP is not enabled. Skip running SFTP
[   51.280000] findhostd uses obsolete (PF_INET,SOCK_PACKET)
[  118.290000] ata1: device plugged sstatus 0x123
[  118.300000] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[  118.310000] ata1: edma_err_cause=00000010 pp_flags=00000000, dev connect
[  118.310000] ata1: SError: { PHYRdyChg DevExch }
[  118.320000] ata1: hard resetting link
[  124.270000] ata1: link is slow to respond, please be patient (ready=0)
[  128.350000] ata1: SRST failed (errno=-16)
[  128.350000] ata1: SRST fail, set srst fail flag
[  128.350000] ata1: hard resetting link
[  130.780000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[  130.780000] ata1: link reset sucessfully clear error flags
[  130.810000] ata1.00: ATA-8: SAMSUNG HD203WI, 1AN10003, max UDMA/133
[  130.810000] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[  130.840000] ata1.00: configured for UDMA/133
[  130.840000] ata1: EH complete
[  130.840000] scsi 0:0:0:0: Direct-Access     SAMSUNG  HD203WI          1AN1 PQ: 0 ANSI: 5
[  130.860000] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[  130.870000] sd 0:0:0:0: Attached scsi generic sg3 type 0
[  130.900000] sd 0:0:0:0: [sda] Write Protect is off
[  130.920000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  130.940000]  sda: sda1 sda2 sda3 < sda5 >
[  130.980000] sd 0:0:0:0: [sda] Attached SCSI disk
[  137.810000] ata2.00: skip command 0xef feature 0x2
[  137.850000] ata1.00: configured for UDMA/133
[  137.850000] ata1: EH complete


Bonus tip: if you feel brave and really eager to void your warranty, you can hack U-Boot and load another operating system instead of Linux. The NetBSD folks posted a handy tutorial here. This is left as an exercise for the reader :)

If you don’t have another Linux machine and your NAS isn’t booting properly, you can use the serial console to try to recover the data within the Synology itself. Just use the cat /proc/mdstat, mdadm and vgchange as explained above to inspect the disks. There’s tons of tutorials on how to recover disks using md and lvm, so I won’t repeat here. I added a few pointers below to get you started. Naturally you’ll need a second healthy disk within the NAS, so you can copy disk-to-disk.

All in all, the Synology Diskstation is an excellent NAS server, created on top of an open platform, and very hacker friendly. Hope you never need to connect a serial console to yours, but it’s good to know that it’s there, should you need it one day.

References:

Glitch is closing. Here’s why.

Today is a sad day. Glitch, the beautiful massive multiplayer game that had the most pixel perfect design ever created, announced that they’ll be closing doors soon. I’m truly heartbroken to see so much work and love simply going to the trashcan. At least they were classy and wrote a candid and honest shutting-down post, and they’ll even refund users the amount paid. That’s a level of integrity that you don’t see everyday in the startup world.

If you’ve never played Glitch, sadly it’s now too late. While the game world is still available for registered users, they are not accepting new registrations, and everything will be turned off by Dec 9th 2012. Here’s some videos to give you an idea of what you missed. Go watch it. I’ll wait.

Yes, it’s gorgeous indeed. I was part of the very first wave of beta testers and, even though I’ve never spent much time playing, I remember being surprised by how every little thing was nicely planned, designed and implemented. In fact these videos don’t do any justice in terms of their attention to detail. Just trust me when I say that it was really pixel perfect.

Aside from the intrinsic beauty, the truth is that there was no reason for you to keep coming back.

It didn’t have the same evil addictive psychology of Zynga’s games (“Your crops are dying! Your friend Samantha just moved to a farm next door. Spam your friends - or buy some credits - so you can level up faster.”). Also didn’t have the action + social interactivity of a WoW. Neither the puzzle challenges like Limbo, or the progressive difficulty of Monkey Island (true, neither one was multiplayer). Also no massive multiplayer, fast paced action like World of Tanks/World of Warplanes…

So, what was it then?

Good question. In the end, it was just a cute massive multiplayer social game. Maybe the cutest ever. But this doesn’t seem enough to attract a loyal audience - other than a few other game geeks, artists and designers.

This reminds me of the Steve Blank’s (the original author behind the lean startup movement) stories. Do you really need to implement a full game, with that many details, with that many layers, with so many features, creative dialogues, dozens of non-playable characters, so much work on the client-server code, on building an architecture that is scalable to thousands of simultaneous users, just to realize that your users aren’t coming back in the first place?

Can’t you do a demo with 2 levels and 5 hard-coded scenarios, and put your mom/sister/son to play for a few months, and just see how many times they come back (when you’re not looking)? Can’t you probably get the same conclusions with, say, 10% of the effort? If you do this early enough, you’ll still have the other 90% of runway to make corrections and explore different options (or, hell, pivot to totally different business model if you discovered your boat isn’t going anywhere).

Of course hindsight is a bitch. (or, like someone on Hacker News said, “…hindsight is a glitch” :-).

Still, it’s clear that they repeated some of the fatal mistakes others have done in the past. Case in point: the excellent paper “Lessons from Habitat” about the experimental project created by Lucasfilm in the mid 80’s. The entire paper is a great read, but one part that strikes me as relevant to this discussion is this:

Lessons from Lucasfilm's Habitat

> While we find much of the work presently being done on elaborate interface technologies — DataGloves, head-mounted displays, special-purpose rendering engines, and so on — both exciting and promising, the almost mystical euphoria that currently seems to surround all this hardware is, in our opinion, both excessive and somewhat misplaced. > > We can’t help having a nagging sense that it’s all a bit of a distraction from the really pressing issues. > > At the core of our vision is the idea that cyberspace is necessarily a multiple-participant environment. It seems to us that the things that are important to the inhabitants of such an environment are the capabilities available to them, the characteristics of the other people they encounter there, and the ways these various participants can affect one another. Beyond a foundation set of communications capabilities, the details of the technology used to present this environment to its participants, while sexy and interesting, are of relatively peripheral concern.

Keep in mind the entire Habitat was implemented in 1986, and ran on a Commodore64. At the time a 1200bps modem was really leading edge (and just yesterday I was complaining that we can’t live with 25 Mbps anymore).

Even though gamers today have higher expectations in terms of quality than ever before, the core principles are still the same: the success of a massive multiplayer game is defined not by its level of peripheral sophistication (be it design, cuteness, or head mounted displays), but by the social experience and characteristics of how people can interact with each other.

Certainly Glitch isn’t alone in repeating these same mistakes. Almost two decades ago, Worlds Chat was the very first 3D world ever created. It achieved moderate success during 1995-96, but people got quickly bored in having to load a heavy and slow 3D environment just to chat. Eventually they lost traction, and people moved to other channels (IRCs and webchats).

The Palace came right after Worlds Chat, and tried to explore exact the interest of people to connect with each other (there was no Facebook at the time :) by creating a simplistic-but-cute 2D avatar-driven chat interface, stripping away all the technical complexities of Worlds Chat. Considerable traction for a couple of years (while it was still new), before dying for the exact same problems as Worlds Chat or Habitat.

Several years later, Philip Rosedale came up with yet-another company trying to recreate the futuristic metaverse described by Neal Stephenson in Snow Crash. (btw, 20+ years and we still don’t have head-mounted displays. No, Google Glass doesn’t count.)

Second Life clearly went much further than all others - at least it was the first one to receive a cover page on BusinessWeek and to get companies like Adidas, Reebok, Dell and IBM rushing to build storefronts in the virtual world. But while Second Life never really failed, they haven’t succeeded either.

And just to complete this short history cycle: Rosedale was one of the very first users of Worlds Chat in 1995. A few years later, with the Worlds, Inc struggling to keep users engaged, he saw an opportunity to create his own version of metaverse. Linden Labs was created a few years later, and the first Second Life launched in 2003. The rest is history.

Last but not least: channel distribution.

Another issue at play for Glitch here is channel distribution. It’s really challenging to succeed with a web-only game, especially when you’re not anchored on Facebook. And, if on top of that you’re using Flash, you’ll be missing out all those millions of 2-3 minutes slots of free time that people have waiting for the train, on the bus, bathroom, elevator, etc. And Glitch almost never sent any emails, so I guess they were expecting people to bookmark the site and keep coming back organically. Yeah, right…

Anyway, in the end of the day, the Glitch team deserves a lot of praise for accomplishing what they did. It’s a gorgeous project, flawless design, and I can just hope that their work will inspire future designers and game developers around the world. And, maybe, parts of the code will be open sourced someday.

You can continue the conversation on Hacker News.

$('a').filter(function() { return this.hostname && this.hostname !== location.hostname; }).addClass("external");