DSM-G600, DNS-3xx and NSA-220 Hack Forum

EnricoM wrote:

Only the standard NAS processes and those started via /ffp/start will be stopped. It seems that there is another process that prevents the fs from umounting.  Do you start other processes manually and/or did you create/modify a new startscript in /ffp/start?

What process though?

I have
#shutdown
turned back on
#hd_verify
# e2fsck -v -f -y /dev/md0
e2fsck 1.32 (09-Nov-2002)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/md0: ***** FILE SYSTEM WAS MODIFIED *****

   90697 inodes used (0%)
    3810 non-contiguous inodes (4.2%)
         # of inodes with ind/dind/tind blocks: 32000/4882/1
59755373 blocks used (27%)
       0 bad blocks
       2 large files

   80761 regular files
    6941 directories
       0 character device files
       0 block device files
       0 fifos
       7 links
    2985 symbolic links (2985 fast symbolic links)
       0 sockets
--------
   90694 files
ERROR

#shutdown

Refresh Shared Name Table version v1.04
/etc/shared_name failed to open.!!!

turned back on and dmesg still shows:

RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).

Here are my processes:
#ps

PID   USER     COMMAND
    1 root     init
    2 root     [ksoftirqd/0]
    3 root     [events/0]
    4 root     [khelper]
    5 root     [kthread]
   11 root     [kblockd/0]
   14 root     [khubd]
   50 root     [pdflush]
   51 root     [pdflush]
   53 root     [aio/0]
   52 root     [kswapd0]
  190 root     [scsi_eh_0]
  191 root     [scsi_eh_1]
  192 root     [scsi_eh_2]
  193 root     [scsi_eh_3]
  204 root     [mtdblockd]
  221 root     [kcryptd/0]
  222 root     [kmirrord/0]
  233 root     [loop0]
1053 root     atd
1058 root     smbd -D
1060 root     nmbd -D
1068 root     smbd -D
1134 root     [md0_raid1]
1203 root     chkbutton
1224 root     /web/webs
1229 root     fancontrol
1256 root     op_server 3 3 3
1263 root     -sh
1287 root     lpd Waiting
1319 root     crond
1406 root     /ffp/bin/ntpd -g -f /ffp/etc/ntp.drift
1417 root     /ffp/sbin/telnetd
1432 root     /ffp/sbin/sshd
1454 root     -sh
1482 root     ps

#

It was a fresh cleanboot install, I haven't modified it and I have not modified any ffp scripts.  Here is my ffp/start dir:


/mnt/HD_a2/ffp/start# ls -al
drwxr-xr-x    2 root     root         4096 Jul 13 03:47 .
drwxr-xr-x   11 root     root         4096 Jul 13 03:47 ..
-rw-r--r--    1 root     root           52 Apr 19 13:26 LOGIN.sh
-rw-r--r--    1 root     root           36 Apr 19 13:26 SERVERS.sh
-rwxr-xr-x    1 root     root          692 Jun 20 15:02 adjtimex.sh
-rwxr-xr-x    1 root     root          164 May  7 18:35 bootcmds.sh
-rwxr-xr-x    1 root     root         1121 Mar 14 02:37 cleanboot.sh
-rw-r--r--    1 root     root          203 Apr 19 12:11 inetd.sh
-rw-r--r--    1 root     root          229 Apr 15 14:06 kickwebs.sh
-rw-r--r--    1 root     root          223 Apr 15 14:06 lighttpd.sh
-rw-r--r--    1 root     root          267 Apr 15 14:52 mediatomb.sh
-rw-r--r--    1 root     root         1468 Apr 15 21:50 nfsd.sh
-rwxr-xr-x    1 root     root          526 Apr 15 17:00 ntpd.sh
-rwxr-xr-x    1 root     root          552 Apr 19 13:26 passwd.sh
-rw-r--r--    1 root     root          160 Apr 15 22:18 portmap.sh
-rwxr-xr-x    1 root     root          861 Apr 19 13:26 rcS.sh
-rw-r--r--    1 root     root          224 Apr 16 07:37 rsyncd.sh
-rwxr-xr-x    1 root     root          534 Apr 19 13:26 shells.sh
-rwxr-xr-x    1 root     root          971 Apr 14 21:19 sshd.sh
-rw-r--r--    1 root     root          398 Apr 19 12:11 syslogd.sh
-rwxr-xr-x    1 root     root          170 May  6 14:39 telnetd.sh
-rw-r--r--    1 root     root          998 Apr 16 21:33 unfsd.sh
-rw-r--r--    1 root     root         2064 Apr 19 13:26 usbdisk.sh

/mnt/HD_a2/ffp/start#

I have insmod the tun/tap driver a while back, but I have not run OpenVPN for a while.  No other manually started processed.

any thoughts? thanks

lu

yes, but doesn't that just mean that there were errors found with the fs (or am I being dumb here).  The output does say that the filesystem was modified.  The next time I run e2fsck it finds a different problem, typically in pass 3 and 5.

I will repeat and see if it says error again.  Here is the result (I ommitted the -y switch this time).


/ffp/start# e2fsck -f -v /dev/md0
e2fsck 1.32 (09-Nov-2002)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Pass 3A: Optimizing directories
Optimizing directories:  13451281 13762563 14761993
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (801619, counted=437879).
Fix<y>? yes

Free inodes count wrong (30203319, counted=30203302).
Fix<y>? yes


/dev/md0: ***** FILE SYSTEM WAS MODIFIED *****

   90714 inodes used (0%)
    3815 non-contiguous inodes (4.2%)
         # of inodes with ind/dind/tind blocks: 32008/4891/1
60119113 blocks used (28%)
       0 bad blocks
       2 large files

   80777 regular files
    6942 directories
       0 character device files
       0 block device files
       0 fifos
       7 links
    2985 symbolic links (2985 fast symbolic links)
       0 sockets
--------
   90711 files
ERROR

/ffp/start#

lu

Last edited by luusac (2008-07-14 14:56:43)

No I hadn't tried running it twice before shutdown, but when I do, instesad of error, I get success.  BUT dmesg still shows the fs warning on restart.  You are using a different method to unmount, I will try that and report.

[just tried and it didn't work:

# umount /dev/md0
# e2fsck -y -f -v /dev/md0

e2fsck 1.40.6 (09-Feb-2008)
/dev/md0 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? no

check aborted.

]

Here is what happened when I ran e2fsck twice without rebooting between checks:
/# e2fsck -f -v -y /dev/md0

e2fsck 1.32 (09-Nov-2002)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Optimizing directories:  13762563 14761993
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (437879, counted=238040).
Fix? yes

Free inodes count wrong (30203302, counted=30203287).
Fix? yes


/dev/md0: ***** FILE SYSTEM WAS MODIFIED *****

   90729 inodes used (0%)
    3820 non-contiguous inodes (4.2%)
         # of inodes with ind/dind/tind blocks: 32014/4895/1
60318952 blocks used (28%)
       0 bad blocks
       2 large files

   80792 regular files
    6942 directories
       0 character device files
       0 block device files
       0 fifos
       7 links
    2985 symbolic links (2985 fast symbolic links)
       0 sockets
--------
   90726 files

/# e2fsck -f -v -y /dev/md0
e2fsck 1.32 (09-Nov-2002)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

   90729 inodes used (0%)
    3820 non-contiguous inodes (4.2%)
         # of inodes with ind/dind/tind blocks: 32014/4895/1
60318952 blocks used (28%)
       0 bad blocks
       2 large files

   80792 regular files
    6943 directories
       0 character device files
       0 block device files
       0 fifos
       7 links
    2985 symbolic links (2985 fast symbolic links)
       0 sockets
--------
   90727 files
SUCCESS
/#

(but note that error is still in dmesg)

Last edited by luusac (2008-07-15 00:14:29)

Try to check your file system the way fonz recommends:
http://www.inreto.de/dns323/fsck/

This fixed my file system issues.

First, thanks for the continued input.

second:

EnricoM wrote:

What about this in Fonz's recommendation (Luusac uses RAID-1) :
If you're using RAID, you need to set it up now. If you know how to do
this, please let me know.

I had seen this on Fonz's site and it is exactly because of using raid1 that I didn't go down that route.  My linux skills aren't good enough.  Though perhaps bq041's raid scripts could help in this regard?

I will post back on the e2fsck versions etc & paths later

thanks

lu

Since I see my name and have not read back through everything, what exactly do you want to acomplish?  Do you want to set up a raid 1 manually?

Path='/opt/bin:/opt/sbin:/ffp/sbin:/ffp/bin:/usr/sbin:/sbin:/usr/bin:/bin'

Where is 'which' located, because once I have run hd_verify I can't access which:

#which e2fsck
-sh: which: not found

once hd_verify is run the array is unmounted - so I can't access /ffp/......
I suppose I could copy it to the ramdisk, but what would the path be, and will e2fsck & cleanboot need anything else (like libraries etc)
lu

Last edited by luusac (2008-07-16 14:36:48)

Hi,
I am trying that too (in another thread :-)
thanks
lu

luusac wrote:

On Fonz's site (http://www.inreto.de/dns323/fsck/) he provides a versions of e2fsck where he says:

"If you're using RAID, you need to set it up now. If you know how to do this, please let me know."

So I was wondering whether one of your raid1 breaking/recreating scripts could be used/adapted to work with this method of using e2fsck.  That is what I was referring to.

cheers

lu

mdadm -A /dev/md0 /dev/sd[ab]2