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

shipiboconibo · 2009-02-24 15:10:39

Hi all,

I am out of ideas on how to get my DNS-323 to stop giving me the 'mounting unchecked fs' warning. I am using 'reboot' to restart, which I read should work with cleanboot. I am running 1.06FW, FFP .05, RAID-0 w/ 2x1TB WD Green drives. I have Firefly, Lightppd/PHP/SQLite, SSH, and Fan Control. And of course CleanBoot 2.0.4.

I kept getting the error: "EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended"

Here is my dmesg output (from the point it mentions RAID on...):

Code:

md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 112K
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 1953525168 512-byte hdwr sectors (1000205 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 1953525168 512-byte hdwr sectors (1000205 MB)
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 sdb4
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
egiga0: mac address changed
egiga0: link down
Adding 530104k swap on /dev/sda1.  Priority:-1 extents:1
Adding 530104k swap on /dev/sdb1.  Priority:-2 extents:1
egiga0: link up<5>, full duplex<5>, speed 1 Gbps<5>
ext3: No journal on filesystem on sda4
ext3: No journal on filesystem on sdb4
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
md: md0 stopped.
md: bind<sdb2>
md: bind<sda2>
md0: setting max_sectors to 128, segment boundary to 32767
raid0: looking at sda2
raid0:   comparing sda2(974133312) with sda2(974133312)
raid0:   END
raid0:   ==> UNIQUE
raid0: 1 zones
raid0: looking at sdb2
raid0:   comparing sdb2(974133312) with sda2(974133312)
raid0:   EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 1948266624 blocks.
raid0 : conf->hash_spacing is 1948266624 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 4 bytes for hash.
md: md0 stopped.
md: unbind<sda2>
md: export_rdev(sda2)
md: unbind<sdb2>
md: export_rdev(sdb2)
md: md1 stopped.
md: md0 stopped.
md: bind<sdb2>
md: bind<sda2>
md0: setting max_sectors to 128, segment boundary to 32767
raid0: looking at sda2
raid0:   comparing sda2(974133312) with sda2(974133312)
raid0:   END
raid0:   ==> UNIQUE
raid0: 1 zones
raid0: looking at sdb2
raid0:   comparing sdb2(974133312) with sda2(974133312)
raid0:   EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 1948266624 blocks.
raid0 : conf->hash_spacing is 1948266624 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 4 bytes for hash.
ext3: No journal on filesystem on sda4
ext3: No journal on filesystem on sdb4
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
md: mdadm(pid 1554) used obsolete MD ioctl, upgrade your software to use new ictls.

I have ran e2fsck on the entire partition and it was fine (just had to correct a date in the future issue). Fwiw I used the FFP fsck package to boot to a ram disk and then perform the scan.

Any ideas? I feel like I have scoured this forum for help, but I'm sorry if the answer is obvious. Please tell me if there is any other information I could provide. I would so greatly appreciate any help I could get on this! Thanks!
-Adam

atx32 · 2009-02-24 19:30:09

Use Cleanboot 2.0.5. That worked for me where 2.0.4 didn't.

shipiboconibo · 2009-02-24 23:37:43

Thanks atx32. I upgraded and still have the same issue. I follow the instructions at http://www.inreto.de/dns323/fsck/ to a tee, and it always gives me a message about my super blocks having a timestamp that is in the future, and I let it fix things, then it says the discs are clean. I then type 'reboot' and I have a dmesg output just like the one above again (I clear my dmesg buffer each time).

I am rebooting using the 'reboot' command. Is this right? I know I read somewhere that cleanboot supports rebooting like this.

Do I understand correctly that without cleanboot my drives are at risk (greater risk) of becoming corrupt? How can I know for sure that clean boot is working right? I see it shutting services down as I reboot in SSH before I get booted.

Thanks.
-Adam

Last edited by shipiboconibo (2009-02-24 23:38:32)

atx32 · 2009-02-25 18:26:03

First of all, you don't have to worry about the superblock timestamp. I think it happens because the timezone when you boot into that fsck environment is different. Just fix it, but it is not an indication of a volume being improperly unmounted. If there was a file system problem, you wouldn't get the "clean" indication, and it would instead go through all the various check passes.

I think your problem is that you haven't checked all the volumes with e2fsck. You need to check /dev/md0, /dev/sda4, and /dev/sdb4. I think it is one of the last 2 that is generating the errors in dmesg (from before you had Cleanboot installed.) Once you check those, all the file systems should be clean and along with Cleanboot 2.0.5 you shouldn't see any more problems.

MosaicPaul · 2009-02-26 06:05:20

Like shipiboconibo I also get the
"EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended"
error even using cleanboot 2.0.5. I have carefully tested several methods of shutting down or rebooting, find the error after some but not others. When I do get the error I then run e2fsck to remove the errors, using the special kernel for that purpose (http://www.inreto.de/dns323/fsck/).

The conditions under which I always get the error:
1. Shutting down from the web interface choosing Tools->System->Shutdown
2. Shutting down by pressing the front panel button
3. Shutting down through telnet by issuing "touch /tmp/shutdown"

The conditions under which I never get the error:
4. Restarting the box through the web interface by choosing Tools->System->Restart
5. Restarting the box through telnet by issuing "reboot"
6. Shutting down through telnet issuing "shutdown -a"

If in addition to installing cleanboot I also install the RAID shutdown file trick (http://dns323.kood.org/forum/t3233-DNS- … rever.html), the results stay the same.

The bottom line for me is that there are two ways to reboot, items 4 and 5 above, but only one way to shutdown the box, item 6 above. It would be nice to be able to power it down some way other than through telnet, but that doesn't seem to be possible for me.

dino · 2009-02-26 06:18:41

MosaicPaul wrote:
6. Shutting down through telnet issuing "shutdown -a"

Did you install a special package to be able to do this from the command-line?

I'm running ffp 0.5 (downloaded as of three days ago).

dino

MosaicPaul · 2009-02-26 06:55:18

dino,

I'm also running fonz's wonderful ffp 0.5, and I am using bash as my default shell. But that's now where shutdow is, instead I find it's a firmware function, at /sbin/shutdown

I just run it from the command line.

-- MosaicPaul

atx32 · 2009-02-26 15:46:34

MosaicPaul,

In the Cleanboot wiki it states that it doesn't support shutdowns via the front panel or web interface. The only way to shutdown and have Cleanboot work is to issue "halt" or "shutdown" from telnet. So what you see is expected based on the way Cleanboot works.

Personally I could never get the raidstop patch method to work, so I just stick with Cleanboot and on those rare ocassions I need to shutdown I just do it from telnet.

Last edited by atx32 (2009-02-26 16:07:05)

shipiboconibo · 2009-03-03 02:43:52

atx32 wrote:
I think your problem is that you haven't checked all the volumes with e2fsck. You need to check /dev/md0, /dev/sda4, and /dev/sdb4. I think it is one of the last 2 that is generating the errors in dmesg (from before you had Cleanboot installed.)

You hit the nail on the head! Thanks a lot atx32! :-)

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

Announcement

#1 2009-02-24 15:10:39

Cleanboot not working or maybe PEBKAC

Code:

#2 2009-02-24 19:30:09

Re: Cleanboot not working or maybe PEBKAC

#3 2009-02-24 23:37:43

Re: Cleanboot not working or maybe PEBKAC

#4 2009-02-25 18:26:03

Re: Cleanboot not working or maybe PEBKAC

#5 2009-02-26 06:05:20

Re: Cleanboot not working or maybe PEBKAC

#6 2009-02-26 06:18:41

Re: Cleanboot not working or maybe PEBKAC

MosaicPaul wrote:

#7 2009-02-26 06:55:18

Re: Cleanboot not working or maybe PEBKAC

#8 2009-02-26 15:46:34

Re: Cleanboot not working or maybe PEBKAC

#9 2009-03-03 02:43:52

Re: Cleanboot not working or maybe PEBKAC

atx32 wrote:

Board footer