Hello!
I make small file server with FreeNAS-8.0.4-RELEASE-p2-x86 (11367) with two HDD, 500Gb each.
Volumes were created via GUI using UFS ( on this machine ZFS will work too slow). After some time one of drives reported SMART error
"Offline uncorrectable sectors" for drive used for backups. Fortunately, now is just trial run and data loss is not a problem,
but for future it will be very important to know, what files are broken.
I found some advices ( http://smartmontools.sourceforge.net/badblockhowto.html , http://www.opennet.ru/tips/info/1720.shtml ) and tried to follow them, but without success.
As I understand FreeNAS use some special format for UFS, because HDD works for read/write, but I cant use BSD commands for it, as well as for second (healthy) HDD:
[root@fs] ~# bsdlabel /dev/ada0
bsdlabel: /dev/ada0: no valid label found
[root@fs] ~# debugfs
debugfs 1.41.14 (22-Dec-2010)
debugfs: open /dev/ada0
/dev/ada0: Bad magic number in super-block while opening filesystem
[root@fs] ~# fsdb /dev/ada0
** /dev/ada0
Cannot find file system superblock
ioctl (GCINFO): Inappropriate ioctl for device
fsdb: /dev/ada0: can't read disk label
So, question is what shall be done in case of partially corrupted data ?
Is there some special command to detect corrupted files or maybe I shall make somehow corrections to filesystem and it will be accessible to BSD commands?
Also, I didn't try it - will be UFS volume created by FreeNAS readable via win UFS viewer ?
I make small file server with FreeNAS-8.0.4-RELEASE-p2-x86 (11367) with two HDD, 500Gb each.
Volumes were created via GUI using UFS ( on this machine ZFS will work too slow). After some time one of drives reported SMART error
"Offline uncorrectable sectors" for drive used for backups. Fortunately, now is just trial run and data loss is not a problem,
but for future it will be very important to know, what files are broken.
I found some advices ( http://smartmontools.sourceforge.net/badblockhowto.html , http://www.opennet.ru/tips/info/1720.shtml ) and tried to follow them, but without success.
As I understand FreeNAS use some special format for UFS, because HDD works for read/write, but I cant use BSD commands for it, as well as for second (healthy) HDD:
[root@fs] ~# bsdlabel /dev/ada0
bsdlabel: /dev/ada0: no valid label found
[root@fs] ~# debugfs
debugfs 1.41.14 (22-Dec-2010)
debugfs: open /dev/ada0
/dev/ada0: Bad magic number in super-block while opening filesystem
[root@fs] ~# fsdb /dev/ada0
** /dev/ada0
Cannot find file system superblock
ioctl (GCINFO): Inappropriate ioctl for device
fsdb: /dev/ada0: can't read disk label
So, question is what shall be done in case of partially corrupted data ?
Is there some special command to detect corrupted files or maybe I shall make somehow corrections to filesystem and it will be accessible to BSD commands?
Also, I didn't try it - will be UFS volume created by FreeNAS readable via win UFS viewer ?