Jump to content

Cache drive went read only when working on Docker Config


bmfrosty

Recommended Posts

unRAID OS Version:

6.0-beta10a

Description:

Drive went read-only.  Could not write to filesystem.  Resolved by stopping and restarting the array.

How to reproduce:

Unknown

Expected results:

N/A

Actual results:

N/A

Other information:

Filesystem of cache drive is ReiserFS

See below for relevant log and dmesg segments:

 

Nov  5 19:59:48 maxi rpc.mountd[1955]: authenticated mount request from 10.10.10.101:51735 for /mnt/user/Movies (/mnt/user/Movies)
Nov  5 19:59:49 maxi shfs/user: shfs_truncate: truncate: /mnt/cache/nzbget/inter/Utopia.S02E04.DVDRip.x264-HAGGiS.#9/373.out.tmp (5) Input/output erro                                                                                       r
Nov  5 19:59:49 maxi shfs/user: shfs_open: open: /mnt/cache/nzbget/inter/Utopia.S02E04.DVDRip.x264-HAGGiS.#9/373.out.tmp (30) Read-only file system
Nov  5 19:59:49 maxi shfs/user: shfs_open: open: /mnt/cache/appdata/nzbget/log/nzbget.logs (30) Read-only file system
Nov  5 19:59:49 maxi shfs/user: shfs_open: open: /mnt/cache/appdata/nzbget/log/nzbget.logs (30) Read-only file system
Nov  5 19:59:49 maxi kernel: REISERFS error (device sdh1): vs-4080 _reiserfs_free_block: block 230757836: bit already cleared
Nov  5 19:59:49 maxi kernel: REISERFS (device sdh1): Remounting filesystem read-only
Nov  5 19:59:49 maxi shfs/user: shfs_write: write: (12) Cannot allocate memory
Nov  5 19:59:49 maxi shfs/user: shfs_open: open: /mnt/cache/appdata/nzbget/log/nzbget.logs (30) Read-only file system
Nov  5 19:59:49 maxi shfs/user: shfs_create: open: /mnt/cache/nzbget/tmp/372.020 (30) Read-only file system
Nov  5 19:59:49 maxi shfs/user: shfs_open: open: /mnt/cache/appdata/nzbget/log/nzbget.logs (30) Read-only file system
Nov  5 19:59:49 maxi kernel: nzbget[6685]: segfault at 0 ip 00002ad0edf867d4 sp 00002ad0fd43a980 error 4 in libc-2.19.so[2ad0edf18000+1bc000]
Nov  5 19:59:49 maxi shfs/user: shfs_open: open: /mnt/cache/nzbget/nzbget.lock (30) Read-only file system
Nov  5 19:59:51 maxi shfs/user: shfs_open: open: /mnt/cache/nzbget/nzbget.lock (30) Read-only file system
Nov  5 19:59:52 maxi shfs/user: shfs_open: open: /mnt/cache/nzbget/nzbget.lock (30) Read-only file system
Nov  5 19:59:53 maxi shfs/user: shfs_open: open: /mnt/cache/nzbget/nzbget.lock (30) Read-only file system
Nov  5 19:59:54 maxi shfs/user: shfs_open: open: /mnt/cache/nzbget/nzbget.lock (30) Read-only file system
Nov  5 19:59:55 maxi shfs/user: shfs_open: open: /mnt/cache/nzbget/nzbget.lock (30) Read-only file system
Nov  5 19:59:55 maxi kernel: BTRFS: bdev /dev/loop8 errs: wr 0, rd 0, flush 1, corrupt 0, gen 0
Nov  5 19:59:55 maxi kernel: BTRFS: error (device loop8) in write_all_supers:3442: errno=-5 IO failure (errors while submitting device barriers.)
Nov  5 19:59:55 maxi kernel: BTRFS info (device loop8): forced readonly
Nov  5 19:59:55 maxi kernel: BTRFS warning (device loop8): Skipping commit of aborted transaction.
Nov  5 19:59:55 maxi kernel: ------------[ cut here ]------------
Nov  5 19:59:55 maxi kernel: WARNING: CPU: 0 PID: 25882 at fs/btrfs/super.c:259 __btrfs_abort_transaction+0x4b/0xfb()
Nov  5 19:59:55 maxi kernel: BTRFS: Transaction aborted (error -5)
Nov  5 19:59:55 maxi kernel: Modules linked in: veth xt_nat ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 nf_nat iptable_filter ip_tables m                                                                                       d_mod k10temp i2c_piix4 ahci libahci r8169 mii [last unloaded: md_mod]
Nov  5 19:59:55 maxi kernel: CPU: 0 PID: 25882 Comm: btrfs-transacti Not tainted 3.16.3-unRAID #3
Nov  5 19:59:55 maxi kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A85X-D3H, BIOS F2 02/01/2013
Nov  5 19:59:55 maxi kernel: 0000000000000000 ffff88021474bcc8 ffffffff815d9532 ffff88021474bd10
Nov  5 19:59:55 maxi kernel: ffff88021474bd00 ffffffff81040687 ffffffff81294a12 00000000fffffffb
Nov  5 19:59:55 maxi kernel: ffff8801023a1800 ffff88012318e8c0 ffffffff8161f270 ffff88021474bd60
Nov  5 19:59:55 maxi kernel: Call Trace:
Nov  5 19:59:55 maxi kernel: [<ffffffff815d9532>] dump_stack+0x45/0x56
Nov  5 19:59:55 maxi kernel: [<ffffffff81040687>] warn_slowpath_common+0x75/0x8e
Nov  5 19:59:55 maxi kernel: [<ffffffff81294a12>] ? __btrfs_abort_transaction+0x4b/0xfb
Nov  5 19:59:55 maxi kernel: [<ffffffff810406e7>] warn_slowpath_fmt+0x47/0x49
Nov  5 19:59:55 maxi kernel: [<ffffffff81294a12>] __btrfs_abort_transaction+0x4b/0xfb
Nov  5 19:59:55 maxi kernel: [<ffffffff812b854a>] cleanup_transaction+0x80/0x21d
Nov  5 19:59:55 maxi kernel: [<ffffffff8106efff>] ? __wake_up_sync+0xd/0xd
Nov  5 19:59:55 maxi kernel: [<ffffffff812b9458>] btrfs_commit_transaction+0x857/0x86c
Nov  5 19:59:55 maxi kernel: [<ffffffff812b54d4>] transaction_kthread+0xf7/0x1c8
Nov  5 19:59:55 maxi kernel: [<ffffffff812b53dd>] ? btrfs_cleanup_transaction+0x45b/0x45b
Nov  5 19:59:55 maxi kernel: [<ffffffff810588ba>] kthread+0xd6/0xde
Nov  5 19:59:55 maxi kernel: [<ffffffff810587e4>] ? kthread_create_on_node+0x168/0x168
Nov  5 19:59:55 maxi kernel: [<ffffffff815df3bc>] ret_from_fork+0x7c/0xb0
Nov  5 19:59:55 maxi kernel: [<ffffffff810587e4>] ? kthread_create_on_node+0x168/0x168
Nov  5 19:59:55 maxi kernel: ---[ end trace 84ef036ef3a5e360 ]---
Nov  5 19:59:55 maxi kernel: BTRFS: error (device loop8) in cleanup_transaction:1571: errno=-5 IO failure
Nov  5 19:59:55 maxi kernel: BTRFS info (device loop8): delayed_refs has NO entry
Nov  5 19:59:56 maxi shfs/user: shfs_open: open: /mnt/cache/nzbget/nzbget.lock (30) Read-only file system


REISERFS error (device sdh1): vs-4080 _reiserfs_free_block: block 230757836: bit already cleared
REISERFS (device sdh1): Remounting filesystem read-only
nzbget[6685]: segfault at 0 ip 00002ad0edf867d4 sp 00002ad0fd43a980 error 4 in libc-2.19.so[2ad0edf18000+1bc000]
BTRFS: bdev /dev/loop8 errs: wr 0, rd 0, flush 1, corrupt 0, gen 0
BTRFS: error (device loop8) in write_all_supers:3442: errno=-5 IO failure (errors while submitting device barriers.)
BTRFS info (device loop8): forced readonly
BTRFS warning (device loop8): Skipping commit of aborted transaction.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 25882 at fs/btrfs/super.c:259 __btrfs_abort_transaction+0x4b/0xfb()
BTRFS: Transaction aborted (error -5)
Modules linked in: veth xt_nat ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 nf_nat iptable_filter ip_tables md_mod k10temp i2c_piix4 ahci libahci r8169 mii [last unloaded: md_mod]
CPU: 0 PID: 25882 Comm: btrfs-transacti Not tainted 3.16.3-unRAID #3
Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A85X-D3H, BIOS F2 02/01/2013
0000000000000000 ffff88021474bcc8 ffffffff815d9532 ffff88021474bd10
ffff88021474bd00 ffffffff81040687 ffffffff81294a12 00000000fffffffb
ffff8801023a1800 ffff88012318e8c0 ffffffff8161f270 ffff88021474bd60
Call Trace:
[<ffffffff815d9532>] dump_stack+0x45/0x56
[<ffffffff81040687>] warn_slowpath_common+0x75/0x8e
[<ffffffff81294a12>] ? __btrfs_abort_transaction+0x4b/0xfb
[<ffffffff810406e7>] warn_slowpath_fmt+0x47/0x49
[<ffffffff81294a12>] __btrfs_abort_transaction+0x4b/0xfb
[<ffffffff812b854a>] cleanup_transaction+0x80/0x21d
[<ffffffff8106efff>] ? __wake_up_sync+0xd/0xd
[<ffffffff812b9458>] btrfs_commit_transaction+0x857/0x86c
[<ffffffff812b54d4>] transaction_kthread+0xf7/0x1c8
[<ffffffff812b53dd>] ? btrfs_cleanup_transaction+0x45b/0x45b
[<ffffffff810588ba>] kthread+0xd6/0xde
[<ffffffff810587e4>] ? kthread_create_on_node+0x168/0x168
[<ffffffff815df3bc>] ret_from_fork+0x7c/0xb0
[<ffffffff810587e4>] ? kthread_create_on_node+0x168/0x168
---[ end trace 84ef036ef3a5e360 ]---
BTRFS: error (device loop8) in cleanup_transaction:1571: errno=-5 IO failure
BTRFS info (device loop8): delayed_refs has NO entry
docker0: port 2(veth25c1) entered disabled state
device veth25c1 left promiscuous mode
docker0: port 2(veth25c1) entered disabled state
docker0: port 5(veth34d7) entered disabled state
device veth34d7 left promiscuous mode
docker0: port 5(veth34d7) entered disabled state
docker0: port 3(veth5f5c) entered disabled state
device veth5f5c left promiscuous mode
docker0: port 3(veth5f5c) entered disabled state
docker0: port 1(veth13a4) entered disabled state
device veth13a4 left promiscuous mode
docker0: port 1(veth13a4) entered disabled state
docker0: port 4(veth9d64) entered disabled state
device veth9d64 left promiscuous mode
docker0: port 4(veth9d64) entered disabled state
br0: port 2(vif1.0) entered disabled state
br0: port 2(vif1.0) entered disabled state
device vif1.0 left promiscuous mode
br0: port 2(vif1.0) entered disabled state
mdcmd (237): nocheck

 

Link to comment
  • 3 weeks later...

I just recently started seeing this exact issue although it is my target data drive that is locking files...sometimes that actual downloaded files and sometimes the nzbget lock file.  It happens specifically with NZBGet in a Docker container.  I may set up a test VM with NZBGet to see if it happens there or not.

Link to comment

A Reiser file system is remounted as read-only when corruption is detected in the file system.  And as you can see below, an error was found in the Reiser file system on sdh1, probably your Cache drive.

 

Nov  5 19:59:49 maxi kernel: REISERFS error (device sdh1): vs-4080 _reiserfs_free_block: block 230757836: bit already cleared

Nov  5 19:59:49 maxi kernel: REISERFS (device sdh1): Remounting filesystem read-only

 

Please see Check Disk File systems to fix it.  This thread should probably be moved to a Support board for V6.

Link to comment

Rob...if this is happening consistently does it indicate an imminent drive failure?  Two days in a row now I have seen this on disk4 and both times it has been when NZBGet was doing it's thing...

 

Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (5) Input/output error
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID kernel: REISERFS error (device md4): vs-4080 _reiserfs_free_block: block 446052105: bit already cleared
Dec  4 07:42:21 unRAID kernel: REISERFS (device md4): Remounting filesystem read-only
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/nzbget.lock (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:21 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:22 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:22 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:22 unRAID shfs/user: shfs_truncate: truncate: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:22 unRAID shfs/user: shfs_open: open: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system
Dec  4 07:42:22 unRAID shfs/user: shfs_unlink: unlink: /mnt/disk4/Downloads/usenet/inter/Phineas.and.Ferb.S01E40-41.720p.HDTV.x264-DVSKY.#308/3606.out.tmp (30) Read-only file system

 

Last night I ran reiserfsck --fix-fixable and it came back and said no corruption was found.  i was then able to write to disk4 again but as you can see it is the same thing all over again this morning.

 

I will say this though...I did not run a reiserfsck --check first.  Is this needed prior to running --fix-fixable?

 

BTW...I have been hitting my system pretty hard over that last few months.  I have not seen ANY corruption until I upgraded to b10a and b12.  Maybe just a coincidence but figured I would mention it.

 

John

Link to comment

Look at the smart report, post the attributes.

I would suggest doing a smart long test.

(Disable any spin down timers on the drive first).

 

 

Post the smart attributes before and after the test.

 

Make sure the drives are healthy first, then look at the wiring and controllers.

 

It certainly can be the OS/Filesystem/driver, but you need to eliminate that it could be the hard drive as well.

There was an earlier beta that had known silent corruptions of reiserfs and metadata. (beta 7 or 8 I think).

Link to comment
  • 1 year later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...