We have a synology media server at home. I wanted to change the root's default shell to bash. I modified the /etc/passwd file and changed the shell from ash to bash. After that I could not log in as root anymore, so I decided to fix it by taking out the harddisk and hooking it up to my laptop. I changed the shell back to ash and removed the drive, but forgot to unmount. I put back the drive in the mediaserver and it won't boot anymore.


I took the drive back out, hooked it back up to my laptop and this time I properly unmounted it. Then I put it back in the media server and it still would not boot.

I suspect there is some kind of weird proprietary raid setup dealio going on here. fsck could not fix the problem. It just gave me the error that it could not run fsck.linux_raid_member

Please help me. This is my dad's machine, not mine, and if I screw this up he will never let me use his server again.

That's a problem cause there are no tools for it installed on the diskstation and I cannot install packages. It is very much a proprietary system.

After rebooting it 5 times it works again.

It just gave me the error that it could not run fsck.linux_raid_member

That was your problem. Linux MD RAID 1 I assume. And you just wrote on 1 member of the RAID1, but not the other.
What does the poor thing do if it finds one disk, which has older data on it and another one which has newer data on it, but wasn't umounted cleanly?
That's right, it craps itself and tries to resync.
If you can get shell access again, run "cat /proc/mdstat"
But maybe I'm just guessing wildly..