NASLite Network Attached Storage

Through the HTML interface (part of) the drive (array) information looks like this:

Disk-1
tune2fs 1.27 (8-Mar-2002)
Filesystem volume name: NASLite-SE000150
Last mounted on:
Filesystem UUID: 2ad4f4ac-9eae-43de-924d-4d82c1f4bd81
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: filetype sparse_super large_file
Filesystem state: not clean

Disk-2
tune2fs 1.27 (8-Mar-2002)
Filesystem volume name: NASLite-SE000150
Last mounted on:
Filesystem UUID: 6bf97d82-99e1-4628-8c24-66da3b2838e5
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super
Filesystem state: clean

Interesting is the fact that the local information after boot says:
Checking storage file system [Disk-1][Clean]
Checking storage file system [Disk-2][Clean]

Which report should I believe?

Also - as you can see - 'the last mounted on' is empty.

Maybe Tony or Ralph find time to explain what is happening.

I *think* that the "not clean" basically means that if you perform a disorderly shutdown (power cut, reset, etc) then the drive will be checked next boot - the flag should be reset at shutdown.

It's a permanent issue. Did quite a few orderly shutdowns and reboots, ran e2fchk, logs remain the same, and local output says 'clean'.

Is Disk-2 RW or RO?

Both arrays are RW.....

I think it's the difference between ext2 and ext3; one drive does not have journal and the "unclean" flag gets reset during proper shutdown. If shutdown is NOT normal, then it needs checking on startup (and the flag is properly set to so indicate). The journaled drive kind of works in reverse. It is always assumed in a "clean" state, until something is written to it; when the write operation completes it goes back to clean. So on shutdown and start up nothing needs to be done with the "clean" flag.

"Last mounted on:" is empty for me too, but I don't think it is intended to refer to a time/date, but a machine name or O/S name. And a little further down in my list there's a "Last mount time:", which seems reasonably correct.

Thank you! That logical drive is new, and I had to apply a journal to that drive. Everything is clean.

Still another syslog line is bothering me:
Oct 6 18:12:35 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended

Do you, or anyone else have a clue? I ran e2fsck a few days ago (before adding the new controller), but that didn't change the log.

Which drive does it apply to ? (Look a couple of lines above that entry.) It may be your USB boot drive (that's what it is in my case). But if it's one of the data drives, report back with the "Filesystem Details" section (only "tune2fs" section, about the size of one webpage; not the entire log).

I think - again - you gave the clue! Both data arrays are ext3 logical drives now. Probably NASLite is referring to the 32 MB solid state IDE drive where the OS is booting from. But nothing can be done there because that drive is not mounted. The only thing which can be done is reformat, which doesn't seem to be such a good idea.

# Oct 6 18:12:35 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
# Oct 6 18:12:35 user.warn kernel: VFS: Mounted root (ext2 filesystem).
# Oct 6 18:12:35 user.info kernel: Mounted devfs on /dev
# Oct 6 18:12:35 user.info kernel: Freeing unused kernel memory: 540k freed
# Oct 6 18:12:35 user.err kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
# Oct 6 18:12:35 user.info kernel: kjournald starting. Commit interval 5 seconds
# Oct 6 18:12:35 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
# Oct 6 18:12:35 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
# Oct 6 18:12:35 user.info kernel: kjournald starting. Commit interval 5 seconds
# Oct 6 18:12:35 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,17), internal journal
# Oct 6 18:12:35 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.