Reboot problem...

An update of DSM 3.0 operating system, including enhanced iPhone and Android phone support, Windows ACL integration, comprehensive iSCSI support, extended volume size capability, Surveillance Station, and a new feature of Time Backup application.

Re: Reboot problem...

Postby FakeDave » Wed Jan 12, 2011 9:28 am

OK, thanx for the information.
I wonder why this happened all of a sudden, after working properly for 2 months?
I also wonder why I have not found more people with the issue (in case I have the same, still to confirm)?
I try to do that today, I miss it very much :(
FakeDave
Trainee
Trainee
 
Posts: 14
Joined: Mon Aug 20, 2007 10:00 pm
Location: Belgium

Re: Reboot problem...

Postby FakeDave » Wed Jan 12, 2011 1:28 pm

So I tried:

    removed /etc/rc.local but not the 2 others that where 'optional' but I don't know on what it's based.
    created optware.sh & made it executable
    but when I go to /opt/etc/init.d, it's empty, I don't have any Sxx script :(

Would you please help with what's next?

Thank you :D
FakeDave
Trainee
Trainee
 
Posts: 14
Joined: Mon Aug 20, 2007 10:00 pm
Location: Belgium

Re: Reboot problem...

Postby shimh » Wed Jan 12, 2011 3:44 pm

Sxx files are used to load daemon if that optware app need to run when the system is started. So if a particular optware app, such as nano, does not have to be run in the background, it won't generate Sxx in that folder. That's probably the reason that not all people have reboot problem after optware apps are installed. In my case, it is caused by Asterisk.

Next, are you sure your reboot issue is caused by Optware apps? I am not expert of optware and linux, as you see, other people like maxxfi, Goetz, etc. helped to generate the solution. :-) If you read the whole thread, you could know the cause of the problem, and why and how of the solution. Then you could check if yours is the same of this one. I had this problem since the initial release of 3.0. To verify that, do not let optware run at all or remove optware, if the reboot problem is caused by optware, now the system should reboot successfully.
shimh
Experienced
Experienced
 
Posts: 107
Joined: Sat Aug 11, 2007 4:03 am

Re: Reboot problem...

Postby FakeDave » Wed Jan 12, 2011 8:55 pm

yes, I've read the whole thread and I thought it was the same problem.
What I understood was that the original problem was a hang up during shutdown. That's also what I experience.
But since I don't have any Sxxx file and based on your email, I now assume that my problem is different.

Can someone tell me what for is the file /etc/rc.local ?

I'll try to investigate further then ... :(
FakeDave
Trainee
Trainee
 
Posts: 14
Joined: Mon Aug 20, 2007 10:00 pm
Location: Belgium

Re: Reboot problem...

Postby goetz » Wed Jan 12, 2011 8:59 pm

Hi,
please provide
Code: Select all
mount
ls -la /


Regards Goetz
DS-209+II / DSM 3.1-1742 /2x 2TB Seagate Constellation ES
DS-107+ / DSM 3.1-1613 / Samsung HD103UI
DS-106 / DSM 3.1-1742 (from 108j) / Hitachi HDP72505
eTrayZ / Samsung HD103SI
goetz
Knowledgeable
Knowledgeable
 
Posts: 336
Joined: Wed Mar 18, 2009 10:05 pm
Location: Berlin, Germany

Re: Reboot problem...

Postby maxxfi » Wed Jan 12, 2011 9:21 pm

FakeDave wrote:Can someone tell me what for is the file /etc/rc.local ?

I'll try to investigate further then ... :(

In the /etc/rc file, after loading kernel modules, etc. etc. there are these lines:
Code: Select all
if [ -r /etc/rc.local ]; then
        echo -n 'Starting local daemons:'
        sh /etc/rc.local
        echo '.'
fi

So if you have some custom service to run at boot, rc.local is the place that Synology has reserved to use
(the file is not wiped out by a f/w upgrade)
In fact, if you e.g. have optware installed and activated, in the rc.local you can find these lines:
Code: Select all
# Optware setup
[ -x /etc/rc.optware ] && /etc/rc.optware start

Which are a call to run the specific optware startup scripts.
DS-411 (DSM 4.2-3202) w/ 2x WD10EFRX + 1x HD154UI
DS-106j (DSM 3.0-1357), PATA-to-SATA adapter, 2.5" HM250HI
User avatar
maxxfi
Architect
Architect
 
Posts: 4339
Joined: Sun Dec 27, 2009 12:13 pm
Location: Espoo, Finland

Re: Reboot problem...

Postby FakeDave » Wed Jan 12, 2011 9:22 pm

Hello goetz,

thanx for looking at my issue :D

Let me know if this is what you look for:
Code: Select all
mount
/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)
/proc/bus/usb on /proc/bus/usb type usbfs (0)
/dev/vg1/lv on /volume1 type ext4 (usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl)
/dev/md3 on /volume2 type ext4 (usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl)
/volume1/@optware on /opt type bind (bind)
/dev/sdk1 on /volumeUSB1/usbshare type fuseblk (rw,allow_other,blksize=4096,default_permissions)

Code: Select all
Rabbit> ls -la /
drwxr-xr-x   23 root     root          4096 Jan 12 09:30 .
drwxr-xr-x   23 root     root          4096 Jan 12 09:30 ..
-rw-------    1 root     root          1024 Oct 28 10:57 .rnd
drwxr-xr-x    2 root     root          4096 Jan 10 21:11 bin
drwxr-xr-x    8 root     root         36864 Jan 12 09:30 dev
drwxr-xr-x   15 root     root          4096 Jan 12 20:56 etc
drwxr-xr-x   13 root     root          4096 Jan 12 09:30 etc.defaults
drwxr-xr-x    2 root     root          4096 Nov  2 13:58 initrd
drwxr-xr-x   14 root     root         12288 Jan 10 21:11 lib
drwxr-xr-x    2 root     root          4096 Jan 10 21:11 lib64
lrwxrwxrwx    1 root     root            11 Jan 10 21:11 linuxrc -> bin/busybox
drwx------    2 root     root          4096 Nov  2 13:55 lost+found
drwxr-xr-x    2 root     root          4096 Nov  2 13:29 mnt
drwxr-xr-x   11 root     root          4096 Nov 27 15:38 opt
dr-xr-xr-x  190 root     root             0 Jan 12 09:30 proc
drwxr-xr-x    2 root     root          4096 Jan 10 21:11 root
drwxr-xr-x    2 root     root          4096 Jan 10 21:11 sbin
drwxr-xr-x   12 root     root             0 Jan 12 09:30 sys
drwxrwxrwx    9 root     root           880 Jan 12 20:57 tmp
drwxr-xr-x    7 root     root          4096 Jan 10 21:11 usr
drwxr-xr-x   12 root     root          4096 Jan 12 09:30 var
drwxr-xr-x   12 root     root          4096 Jan 10 21:11 var.defaults
drwxr-xr-x   19 root     root          4096 Jan 12 09:30 volume1
drwxr-xr-x    6 root     root          4096 Jan 12 09:30 volume2
drwxr-xr-x    3 root     root          4096 Jan 12 09:54 volumeUSB1


Is that what you requested ? Anything, please ask :)
FakeDave
Trainee
Trainee
 
Posts: 14
Joined: Mon Aug 20, 2007 10:00 pm
Location: Belgium

Re: Reboot problem...

Postby FakeDave » Wed Jan 12, 2011 9:35 pm

Hello maxxfi,

Thanx for your explanation. Little by little it'll all get together I guess (any book I could get that would walk me thru that stuff?)

here's the content of my rc.local file that I had just renamed:
Code: Select all
#!/bin/sh

# Optware setup
[ -x /etc/rc.optware ] && /etc/rc.optware start

exit 0


Here's my /etc/rc.optware
Code: Select all
#! /bin/sh

if test -z "${REAL_OPT_DIR}"; then
# next line to be replaced according to OPTWARE_TARGET
REAL_OPT_DIR=/volume1/@optware
fi

case "$1" in
    start)
        echo "Starting Optware."
        if test -n "${REAL_OPT_DIR}"; then
            if ! grep ' /opt ' /proc/mounts >/dev/null 2>&1 ; then
                mkdir -p /opt
                mount -o bind ${REAL_OPT_DIR} /opt
            fi
        fi
        [ -x /opt/etc/rc.optware ] && /opt/etc/rc.optware
    ;;
    reconfig)
        true
    ;;
    stop)
        echo "Shutting down Optware."
        true
    ;;
    *)
        echo "Usage: $0 {start|stop|reconfig}"
        exit 1
esac

exit 0


and finally /opt/etc/rc.optware
Code: Select all
#!/bin/sh

# Start all init scripts in /opt/etc/init.d
# executing them in numerical order.
#
for i in /opt/etc/init.d/S??* ;do

        # Ignore dangling symlinks (if any).
        [ ! -f "$i" ] && continue

        case "$i" in
           *.sh)
                # Source shell script for speed.
                (
                        trap - INT QUIT TSTP
                        set start
                        . $i
                )
                ;;
           *)
                # No sh extension, so fork subprocess.
                $i start
                ;;
        esac
done


I guess it's all normal, I put it just in case as I don't understand anything there ...
FakeDave
Trainee
Trainee
 
Posts: 14
Joined: Mon Aug 20, 2007 10:00 pm
Location: Belgium

Previous

Return to DiskStation Manager 3.0 - 1334/1337

Who is online

Users browsing this forum: No registered users and 1 guest