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

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

#1 2008-07-13 17:57:57

luusac
Member
Registered: 2008-04-29
Posts: 360

using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

Hi,
I have installed cleanboot:

    # wget -O cleanboot-2.0.4-ffp05.tgz http://dns323.kood.org/forum/attachment.php?item=269
    # funpkg -i cleanboot-2.0.4-ffp05.tgz
    # chmod a+x /ffp/start/cleanboot.sh
    # /ffp/start/cleanboot.sh start


Am running ffp 0.5 and f/w 1.04, raid1, ntp, ssh, telnet, cleanboot 2.0.4 via ffp, and tun/tap driver added to the kernel for OpenVPN.

#./cleanboot.sh status
cleanboot running

on 1st boot dmesg is saying:

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

So from console I entered:

    hd_verify
    e2fsck -y -c -v /dev/md0    (actually I can't remember whether it was -y -c -v or -y -f -v)

errors fixed then:

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

unit shuts down, I turn it back on and EXT2-fs warning is still in dmesg, but this time it is there 3 times (see bottom of post for full dmesg).

Adding 530104k swap on /dev/sda1.  Priority:-1 extents:1
Adding 530104k swap on /dev/sdb1.  Priority:-2 extents:1
ext3: No journal on filesystem on sda2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
ext3: No journal on filesystem on sdb2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
md: md0 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md0 active with 2 out of 2 mirrors
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
Link Layer Topology Discovery Protocol, version 1.05.1223.2005
dev is  <NULL>
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>


What am I doing wrong?  Now that cleanboot is working, I am not supposed to get this because all services have been shutdown correctly, right ?

thanks

lu

Linux version 2.6.12.6-arm1 (jack@SWTEST2) (gcc version 3.3.3) #29 Thu Dec 27 09:59:48 CST 2007
CPU: ARM926EJ-Sid(wb) [41069260] revision 0 (ARMv5TEJ)
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
CPU0: D cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
Machine: MV-88fxx81
Using UBoot passing parameters structure
Sys Clk = 166000000, Tclk = 166000000


- Warning - This LSP release was tested only with U-Boot release 1.7.3

Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 16384
  DMA zone: 16384 pages, LIFO batch:7
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: root=/dev/ram console=ttyS0,115200 :::DB88FXX81:egiga0:none
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB 0MB 0MB 0MB = 64MB total
Memory: 55680KB available (2466K code, 454K data, 112K init)
Calibrating delay loop... 331.77 BogoMIPS (lpj=1658880)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 6064K
NET: Registered protocol family 16

  Marvell Development Board (LSP Version 1.7.6_NAS)-- RD-88F5181-88SX7042-2xSATA

Detected Tclk 166000000 and SysClk 166000000
Marvell USB EHCI Host controller #0: c03a7bc0
pexBarOverlapDetect: winNum 2 overlap current 0
mvPexInit:Warning :Bar 2 size is illigal
it will be disabled
please check Pex and CPU windows configuration
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
cesadev_init(c0012498)
Fast Floating Point Emulator V0.9 (c) Peter Teichmann.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 4 ports, IRQ sharing disabled
ttyS0 at MMIO 0x0 (irq = 3) is a 16550A
io scheduler noop registered
io scheduler deadline registered
RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize
loop: loaded (max 8 devices)
Marvell Gigabit Ethernet Driver 'egiga':
  o Ethernet descriptors in DRAM
  o DRAM SW cache-coherency
  o Checksum offload enabled
  o Loading network interface 'egiga0'
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi2 : Marvell SCSI to SATA adapter
scsi3 : Marvell SCSI to SATA adapter
  Vendor: Seagate   Model: ST3250410AS       Rev: 3.AA
  Type:   Direct-Access                      ANSI SCSI revision: 03
  Vendor: Seagate   Model: ST3250410AS       Rev: 3.AA
  Type:   Direct-Access                      ANSI SCSI revision: 03
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0,  type 0
physmap flash device: 800000 at ff800000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition definition
Creating 5 MTD partitions on "phys_mapped_flash":
0x00000000-0x00010000 : "MTD1"
0x00010000-0x00020000 : "MTD2"
0x00020000-0x001a0000 : "Linux Kernel"
0x001a0000-0x007d0000 : "File System"
0x007d0000-0x00800000 : "u-boot"
ehci_platform ehci_platform.20865: EHCI Host Controller
ehci_platform ehci_platform.20865: new USB bus registered, assigned bus number 1
ehci_platform ehci_platform.20865: irq 17, io mem 0x00000000
ehci_platform ehci_platform.20865: park 0
ehci_platform ehci_platform.20865: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
usb 1-1: new full speed USB device using ehci_platform and address 2
usb 1-1: device descriptor read/64, error -71
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
mice: PS/2 mouse device common for all mice
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 112K
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
egiga0: mac address changed
egiga0: link down
egiga0: link up<5>, full duplex<5>, speed 100 Mbps<5>
Adding 530104k swap on /dev/sda1.  Priority:-1 extents:1
Adding 530104k swap on /dev/sdb1.  Priority:-2 extents:1
ext3: No journal on filesystem on sda2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
ext3: No journal on filesystem on sdb2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
md: md0 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md0 active with 2 out of 2 mirrors
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
Link Layer Topology Discovery Protocol, version 1.05.1223.2005
dev is  <NULL>
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

Offline

 

#2 2008-07-13 22:14:09

EnricoM
Member
From: Netherlands
Registered: 2008-06-03
Posts: 77

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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?


Hardware: Conceptronic CH3SNAS, FW1.03 - 2x Samsung Spinpoint F1 750 MB, no RAID  - Imation Whizz 4GB USB Flash Drive
Software:  Fun_plug 0.5 beta, SSH, Samba recycle bin, Firefly, hellanzb, nzbget, cleanboot, chrooted etch, optware, midnight commander, rsnapshot

Offline

 

#3 2008-07-13 23:47:00

luusac
Member
Registered: 2008-04-29
Posts: 360

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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

Offline

 

#4 2008-07-14 09:25:10

EnricoM
Member
From: Netherlands
Registered: 2008-06-03
Posts: 77

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

Am I right if I see that e2fsck ends with 'ERROR'?


Hardware: Conceptronic CH3SNAS, FW1.03 - 2x Samsung Spinpoint F1 750 MB, no RAID  - Imation Whizz 4GB USB Flash Drive
Software:  Fun_plug 0.5 beta, SSH, Samba recycle bin, Firefly, hellanzb, nzbget, cleanboot, chrooted etch, optware, midnight commander, rsnapshot

Offline

 

#5 2008-07-14 14:17:28

luusac
Member
Registered: 2008-04-29
Posts: 360

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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)

Offline

 

#6 2008-07-14 19:54:08

EnricoM
Member
From: Netherlands
Registered: 2008-06-03
Posts: 77

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

I don't think the ERROR message is normal. Below an example of my box:

Code:

root@MEDIASERVER:/# umount /dev/sdb4
root@MEDIASERVER:/# e2fsck -f /dev/sdb4
e2fsck 1.40.6 (09-Feb-2008)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create<y>? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sdb4: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb4: 26/128520 files (0.0% non-contiguous), 16232/514080 blocks
root@MEDIASERVER:/#

So no ERROR indication...
What happens if you run e2fsck 2 times directly after eachother without rebooting? Is the problem fixed then?
In my case I get this result:

Code:

root@MEDIASERVER:~# e2fsck -f /dev/sdb4
e2fsck 1.40.6 (09-Feb-2008)
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/sdb4: 26/128520 files (0.0% non-contiguous), 16232/514080 blocks
root@MEDIASERVER:~#

When the errors have been solved and they are present again after reboot, it might be that the raid-1 doesn't shutdown properly. Because I use raid-0, I can not test this.

Last edited by EnricoM (2008-07-14 20:01:44)


Hardware: Conceptronic CH3SNAS, FW1.03 - 2x Samsung Spinpoint F1 750 MB, no RAID  - Imation Whizz 4GB USB Flash Drive
Software:  Fun_plug 0.5 beta, SSH, Samba recycle bin, Firefly, hellanzb, nzbget, cleanboot, chrooted etch, optware, midnight commander, rsnapshot

Offline

 

#7 2008-07-15 00:06:04

luusac
Member
Registered: 2008-04-29
Posts: 360

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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)

Offline

 

#8 2008-07-15 15:34:02

EnricoM
Member
From: Netherlands
Registered: 2008-06-03
Posts: 77

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

Strange that your e2fsck version is different, it should point to the ffp folder from fonz fun_plug 0.5:

Code:

root@MEDIASERVER:/# which e2fsck
/ffp/sbin/e2fsck
root@MEDIASERVER:/# ls /ffp/sbin/e2fsck -l
-rwxr-xr-x    1 root     root       149068 Apr 15 12:11 /ffp/sbin/e2fsck

Because you installed the same fun_plug version as I have, I am wondering why you have a different e2fsck version. Are you sure that the PATH settings are correct (PATH='/ffp/sbin:/ffp/bin:/usr/sbin:/sbin:/usr/bin:/bin')? In case of wrong path settings you might initiate the wrong shutdown command instead of the cleanboot version.

You might verify the actual file started when you issue the shutdown command, it should point to do_reboot.

Code:

root@MEDIASERVER:/# which shutdown
/sbin/shutdown
root@MEDIASERVER:/# ls /sbin/shutdown -l
lrwxrwxrwx    1 root     root           19 Jul 11 15:54 /sbin/shutdown -> /usr/sbin/do_reboot
root@MEDIASERVER:/# ls /usr/sbin/do_reboot -l
-rwxr-xr-x    1 root     root         3632 Jul 11 15:54 /usr/sbin/do_reboot
root@MEDIASERVER:/#

Hardware: Conceptronic CH3SNAS, FW1.03 - 2x Samsung Spinpoint F1 750 MB, no RAID  - Imation Whizz 4GB USB Flash Drive
Software:  Fun_plug 0.5 beta, SSH, Samba recycle bin, Firefly, hellanzb, nzbget, cleanboot, chrooted etch, optware, midnight commander, rsnapshot

Offline

 

#9 2008-07-15 20:19:59

marinalink
Member
Registered: 2008-04-13
Posts: 56

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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

This fixed my file system issues.

Offline

 

#10 2008-07-15 20:35:32

EnricoM
Member
From: Netherlands
Registered: 2008-06-03
Posts: 77

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

marinalink wrote:

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

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.


Hardware: Conceptronic CH3SNAS, FW1.03 - 2x Samsung Spinpoint F1 750 MB, no RAID  - Imation Whizz 4GB USB Flash Drive
Software:  Fun_plug 0.5 beta, SSH, Samba recycle bin, Firefly, hellanzb, nzbget, cleanboot, chrooted etch, optware, midnight commander, rsnapshot

Offline

 

#11 2008-07-15 21:09:11

luusac
Member
Registered: 2008-04-29
Posts: 360

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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

Offline

 

#12 2008-07-15 23:53:03

marinalink
Member
Registered: 2008-04-13
Posts: 56

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

Yes you are right, you have to setup the RAID at that point... hm, I'm just using a standard configuration (two single disks). Sorry, I can't help you in this respect.

Offline

 

#13 2008-07-16 05:48:31

bq041
Member
From: USA
Registered: 2008-03-19
Posts: 709

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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?


DNS-323     F/W: 1.04b84  H/W: A1  ffp: 0.5  Drives: 2X 400 GB Seagate SATA-300
DNS-323     F/W: 1.05b28  H/W: B1  ffp: 0.5  Drives: 2X 1 TB  WD SATA-300
DSM-G600   F/W: 1.02       H/W: B                Drive:  500 GB WD ATA

Offline

 

#14 2008-07-16 12:58:02

luusac
Member
Registered: 2008-04-29
Posts: 360

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

bq041 wrote:

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?

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

Offline

 

#15 2008-07-16 13:23:11

luusac
Member
Registered: 2008-04-29
Posts: 360

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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)

Offline

 

#16 2008-07-16 14:35:29

EnricoM
Member
From: Netherlands
Registered: 2008-06-03
Posts: 77

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

You could try to put the funplug on a usb flash drive. In that case you can umount the hard disks and still have access to all the funplug commands and in my case even a chrooted debian environment. This works fine for me . . .


Hardware: Conceptronic CH3SNAS, FW1.03 - 2x Samsung Spinpoint F1 750 MB, no RAID  - Imation Whizz 4GB USB Flash Drive
Software:  Fun_plug 0.5 beta, SSH, Samba recycle bin, Firefly, hellanzb, nzbget, cleanboot, chrooted etch, optware, midnight commander, rsnapshot

Offline

 

#17 2008-07-16 14:37:19

luusac
Member
Registered: 2008-04-29
Posts: 360

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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

Offline

 

#18 2008-07-16 14:40:59

EnricoM
Member
From: Netherlands
Registered: 2008-06-03
Posts: 77

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

Or try to remount the disks after e2fsck, in that case you should have access again to the funplug commands


Hardware: Conceptronic CH3SNAS, FW1.03 - 2x Samsung Spinpoint F1 750 MB, no RAID  - Imation Whizz 4GB USB Flash Drive
Software:  Fun_plug 0.5 beta, SSH, Samba recycle bin, Firefly, hellanzb, nzbget, cleanboot, chrooted etch, optware, midnight commander, rsnapshot

Offline

 

#19 2008-07-16 17:50:44

bq041
Member
From: USA
Registered: 2008-03-19
Posts: 709

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

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

Code:

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

DNS-323     F/W: 1.04b84  H/W: A1  ffp: 0.5  Drives: 2X 400 GB Seagate SATA-300
DNS-323     F/W: 1.05b28  H/W: B1  ffp: 0.5  Drives: 2X 1 TB  WD SATA-300
DSM-G600   F/W: 1.02       H/W: B                Drive:  500 GB WD ATA

Offline

 

#20 2008-09-27 14:29:44

Nuri
Member
Registered: 2008-09-27
Posts: 12

Re: using cleanboot & still getting EXT2-fs warning: mounting unchecked fs

I have the same problem. I use cleanboot and after reboot dmesg reported
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
for both hard drives (i don't use RAID). What's wrong? And i don't undestand why lost+found directory disappeared from both drives after reboot?
e2fsck always wants to create it smile
Sorry for bad English smile

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB