DNS-325 A1, RC5
The idea is not dead, to place the minidlna database and cache to an external ssd on the usb port, so content can be browsed while the harddrives are sleeping on. But found a curious problem.
Alt-F mounts the ssd automated and reported it's ext2 as dirty. I choose ext2 to get of journaling that has destroyed an usb key before. But alt-f reports the filesystem as dirty. I can check and check-force it but there after it is dirty. I formatted it again with alt-f and right after that it is reported in red as dirty. Minidlna dislike to start on a dirty filesystem.
Do we have a bug in the ext2 handling?
Plugged a new Transcend usb ssd into the device, formatted it from vfat to ext2. Result:
Unable to automatically fix sdc1, mounting Read Only: fsck 1.41.14 (22-Dec-2010)
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc1
/dev/sdc1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
The filesystem ext2 is dirty and trashed when formatting has ended.
Eric