claira Posted January 20, 2016 Share Posted January 20, 2016 I wanted to remove a 2nd cache drive. Click the new config to reset the array as guided. Now I don't know which drive to assign in which order. Got the following drives. Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405XNL (sdb) 7814026584 Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405YKP (sdc) 7814026584 Jan 19 19:11:40 UNRAID emhttp: ST3000DM001-9YN166_W1F0MKEB (sdd) 2930266584 Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405Y1T (sde) 7814026584 Jan 19 19:11:40 UNRAID emhttp: WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 (sdf) 2930266584 Jan 19 19:11:40 UNRAID emhttp: SAMSUNG_SSD_830_Series_S0VVNEAC602793 (sdg) 250059096 Jan 19 19:11:40 UNRAID emhttp: INTEL_SSDSC2CT060A3_CVMP2216081G060AGN (sdh) 58615704 Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8409T0L (sdi) 7814026584 Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8409MLA (sdj) 7814026584 Is there a way to figure out what order to put them back in? One is the parity drive. Link to comment
claira Posted January 20, 2016 Author Share Posted January 20, 2016 Any chance the old drive order can be figured out form this log? Full log attached. Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405XNL (sdb) 7814026584 Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405YKP (sdc) 7814026584 Jan 19 18:57:08 UNRAID emhttp: ST3000DM001-9YN166_W1F0MKEB (sdd) 2930266584 Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405Y1T (sde) 7814026584 Jan 19 18:57:08 UNRAID emhttp: WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 (sdf) 2930266584 Jan 19 18:57:08 UNRAID emhttp: SAMSUNG_SSD_830_Series_S0VVNEAC602793 (sdg) 250059096 Jan 19 18:57:08 UNRAID emhttp: INTEL_SSDSC2CT060A3_CVMP2216081G060AGN (sdh) 58615704 Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8409T0L (sdi) 7814026584 Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8409MLA (sdj) 7814026584 Jan 19 18:57:08 UNRAID emhttp: array slots: 23 Jan 19 18:57:08 UNRAID emhttp: cache slots: 2 Jan 19 18:57:08 UNRAID kernel: mdcmd (1): import 0 8,16 7814026532 ST8000AS0002-1NA17Z_Z8405XNL Jan 19 18:57:08 UNRAID kernel: md: import disk0: [8,16] (sdb) ST8000AS0002-1NA17Z_Z8405XNL size: 7814026532 Jan 19 18:57:08 UNRAID kernel: mdcmd (2): import 1 8,64 7814026532 ST8000AS0002-1NA17Z_Z8405Y1T Jan 19 18:57:08 UNRAID kernel: md: import disk1: [8,64] (sde) ST8000AS0002-1NA17Z_Z8405Y1T size: 7814026532 Jan 19 18:57:08 UNRAID kernel: mdcmd (3): import 2 8,48 2930266532 ST3000DM001-9YN166_W1F0MKEB Jan 19 18:57:08 UNRAID kernel: md: import disk2: [8,48] (sdd) ST3000DM001-9YN166_W1F0MKEB size: 2930266532 Jan 19 18:57:08 UNRAID kernel: mdcmd (4): import 3 8,32 7814026532 ST8000AS0002-1NA17Z_Z8405YKP Jan 19 18:57:08 UNRAID kernel: md: import disk3: [8,32] (sdc) ST8000AS0002-1NA17Z_Z8405YKP size: 7814026532 Jan 19 18:57:08 UNRAID kernel: mdcmd (5): import 4 8,80 2930266532 WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 Jan 19 18:57:08 UNRAID kernel: md: import disk4: [8,80] (sdf) WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 size: 2930266532 Jan 19 18:57:08 UNRAID kernel: mdcmd (6): import 5 8,128 7814026532 ST8000AS0002-1NA17Z_Z8409T0L Jan 19 18:57:08 UNRAID kernel: md: import disk5: [8,128] (sdi) ST8000AS0002-1NA17Z_Z8409T0L size: 7814026532 log.txt Link to comment
claira Posted January 20, 2016 Author Share Posted January 20, 2016 Before: Jan 19 19:06:25 UNRAID kernel: mdcmd (1): import 0 8,16 7814026532 ST8000AS0002-1NA17Z_Z8405XNL Jan 19 19:06:25 UNRAID kernel: md: import disk0: [8,16] (sdb) ST8000AS0002-1NA17Z_Z8405XNL size: 7814026532 Jan 19 19:06:25 UNRAID kernel: mdcmd (2): import 1 8,64 7814026532 ST8000AS0002-1NA17Z_Z8405Y1T Jan 19 19:06:25 UNRAID kernel: md: import disk1: [8,64] (sde) ST8000AS0002-1NA17Z_Z8405Y1T size: 7814026532 Jan 19 19:06:25 UNRAID kernel: mdcmd (3): import 2 8,48 2930266532 ST3000DM001-9YN166_W1F0MKEB Jan 19 19:06:25 UNRAID kernel: md: import disk2: [8,48] (sdd) ST3000DM001-9YN166_W1F0MKEB size: 2930266532 Jan 19 19:06:25 UNRAID kernel: mdcmd (4): import 3 8,32 7814026532 ST8000AS0002-1NA17Z_Z8405YKP Jan 19 19:06:25 UNRAID kernel: md: import disk3: [8,32] (sdc) ST8000AS0002-1NA17Z_Z8405YKP size: 7814026532 Jan 19 19:06:25 UNRAID kernel: mdcmd (5): import 4 8,80 2930266532 WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 Jan 19 19:06:25 UNRAID kernel: md: import disk4: [8,80] (sdf) WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 size: 2930266532 Jan 19 19:06:25 UNRAID kernel: mdcmd (6): import 5 8,128 7814026532 ST8000AS0002-1NA17Z_Z8409T0L Jan 19 19:06:25 UNRAID kernel: md: import disk5: [8,128] (sdi) ST8000AS0002-1NA17Z_Z8409T0L size: 7814026532 After: Jan 19 19:28:23 UNRAID kernel: mdcmd (1): import 0 8,16 7814026532 ST8000AS0002-1NA17Z_Z8405XNL Jan 19 19:28:23 UNRAID kernel: md: import disk0: [8,16] (sdb) ST8000AS0002-1NA17Z_Z8405XNL size: 7814026532 Jan 19 19:28:23 UNRAID kernel: md: disk0 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (2): import 1 8,64 7814026532 ST8000AS0002-1NA17Z_Z8405Y1T Jan 19 19:28:23 UNRAID kernel: md: import disk1: [8,64] (sde) ST8000AS0002-1NA17Z_Z8405Y1T size: 7814026532 Jan 19 19:28:23 UNRAID kernel: md: disk1 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (3): import 2 8,48 2930266532 ST3000DM001-9YN166_W1F0MKEB Jan 19 19:28:23 UNRAID kernel: md: import disk2: [8,48] (sdd) ST3000DM001-9YN166_W1F0MKEB size: 2930266532 Jan 19 19:28:23 UNRAID kernel: md: disk2 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (4): import 3 8,32 7814026532 ST8000AS0002-1NA17Z_Z8405YKP Jan 19 19:28:23 UNRAID kernel: md: import disk3: [8,32] (sdc) ST8000AS0002-1NA17Z_Z8405YKP size: 7814026532 Jan 19 19:28:23 UNRAID kernel: md: disk3 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (5): import 4 8,80 2930266532 WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 Jan 19 19:28:23 UNRAID kernel: md: import disk4: [8,80] (sdf) WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 size: 2930266532 Jan 19 19:28:23 UNRAID kernel: md: disk4 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (6): import 5 8,128 7814026532 ST8000AS0002-1NA17Z_Z8409T0L Jan 19 19:28:23 UNRAID kernel: md: import disk5: [8,128] (sdi) ST8000AS0002-1NA17Z_Z8409T0L size: 7814026532 Jan 19 19:28:23 UNRAID kernel: md: disk5 new disk So looks like I managed to put the drives back in place. Is it safe to start? Only change is 1 cache drive instead of 2. Should I check Parity is already valid? It should be in my opinion. As I put everything back as is. Link to comment
claira Posted January 20, 2016 Author Share Posted January 20, 2016 I cant start my docker Plex Server: THe docker tab doesn't show up even though it's enabled. ErrorWarningSystemArrayLogin Jan 19 19:52:06 UNRAID kernel: blk_update_request: I/O error, dev loop1, sector 2390400 Jan 19 19:52:06 UNRAID kernel: BTRFS: bdev /dev/loop1 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Jan 19 19:52:06 UNRAID kernel: BTRFS: error (device loop1) in btrfs_commit_transaction:2071: errno=-5 IO failure (Error while writing out transaction) Jan 19 19:52:06 UNRAID kernel: BTRFS warning (device loop1): Skipping commit of aborted transaction. Jan 19 19:52:06 UNRAID kernel: ------------[ cut here ]------------ Jan 19 19:52:06 UNRAID kernel: WARNING: CPU: 2 PID: 11801 at fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4d/0x10e() Jan 19 19:52:06 UNRAID kernel: BTRFS: Transaction aborted (error -5) Jan 19 19:52:06 UNRAID kernel: Modules linked in: kvm_intel kvm vhost_net vhost macvtap macvlan md_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables iptable_filter ip_tables tun hid_logitech_hidpp i2c_i801 ahci libahci hid_logitech_dj e1000e mvsas ptp libsas scsi_transport_sas pps_core [last unloaded: md_mod] Jan 19 19:52:06 UNRAID kernel: CPU: 2 PID: 11801 Comm: mount Tainted: G W 4.1.15-unRAID #1 Jan 19 19:52:06 UNRAID kernel: Hardware name: ASUS All Series/Z97-A, BIOS 2501 04/27/2015 Jan 19 19:52:06 UNRAID kernel: 0000000000000009 ffff8800b9783978 ffffffff815f1ad0 0000000000000000 Jan 19 19:52:06 UNRAID kernel: ffff8800b97839c8 ffff8800b97839b8 ffffffff8104775b ffff8800b9783a08 Jan 19 19:52:06 UNRAID kernel: ffffffff81286ae4 00000000fffffffb ffff880429a3a800 ffff88041b029160 Jan 19 19:52:06 UNRAID kernel: Call Trace: Jan 19 19:52:06 UNRAID kernel: [<ffffffff815f1ad0>] dump_stack+0x4c/0x6e Jan 19 19:52:06 UNRAID kernel: [<ffffffff8104775b>] warn_slowpath_common+0x97/0xb1 Jan 19 19:52:06 UNRAID kernel: [<ffffffff81286ae4>] ? __btrfs_abort_transaction+0x4d/0x10e Jan 19 19:52:06 UNRAID kernel: [<ffffffff810477b6>] warn_slowpath_fmt+0x41/0x43 Jan 19 19:52:06 UNRAID kernel: [<ffffffff81286ae4>] __btrfs_abort_transaction+0x4d/0x10e Jan 19 19:52:06 UNRAID kernel: [<ffffffff812ac121>] cleanup_transaction+0x80/0x21d Jan 19 19:52:06 UNRAID kernel: [<ffffffff810724cb>] ? wait_woken+0x7d/0x7d Jan 19 19:52:06 UNRAID kernel: [<ffffffff812ad38b>] btrfs_commit_transaction+0xa6c/0xa81 Jan 19 19:52:06 UNRAID kernel: [<ffffffff812e43b1>] btrfs_recover_log_trees+0x30a/0x374 Jan 19 19:52:06 UNRAID kernel: [<ffffffff812e0ed0>] ? replay_one_dir_item+0xcc/0xcc Jan 19 19:52:06 UNRAID kernel: [<ffffffff812aaf96>] open_ctree+0x1aa2/0x1d9c Jan 19 19:52:06 UNRAID kernel: [<ffffffff81287fd2>] btrfs_mount+0x4ac/0x7ea Jan 19 19:52:06 UNRAID kernel: [<ffffffff810c8bba>] ? pcpu_alloc+0x408/0x4e7 Jan 19 19:52:06 UNRAID kernel: [<ffffffff811009a0>] mount_fs+0x12/0x8a Jan 19 19:52:06 UNRAID kernel: [<ffffffff81115957>] vfs_kern_mount+0x5f/0xf8 Jan 19 19:52:06 UNRAID kernel: [<ffffffff8111854f>] do_mount+0x985/0xa7c Jan 19 19:52:06 UNRAID kernel: [<ffffffff810c5733>] ? strndup_user+0x37/0x82 Jan 19 19:52:06 UNRAID kernel: [<ffffffff81118858>] SyS_mount+0x72/0xa1 Jan 19 19:52:06 UNRAID kernel: [<ffffffff815f71ee>] system_call_fastpath+0x12/0x71 Jan 19 19:52:06 UNRAID kernel: ---[ end trace 10222e51d5086f72 ]--- Jan 19 19:52:06 UNRAID kernel: BTRFS: error (device loop1) in cleanup_transaction:1692: errno=-5 IO failure Jan 19 19:52:06 UNRAID kernel: BTRFS info (device loop1): delayed_refs has NO entry Jan 19 19:52:06 UNRAID kernel: BTRFS: error (device loop1) in btrfs_replay_log:2334: errno=-5 IO failure (Failed to recover log tree) Jan 19 19:52:06 UNRAID logger: Not starting Docker: mount error Jan 19 19:52:06 UNRAID kernel: BTRFS: open_ctree failed Link to comment
ntrlsur Posted January 20, 2016 Share Posted January 20, 2016 I am going to guess that the docker image might have gotten corrupted.. You might have to redo the config for docker. That it just a guess though. Link to comment
trurl Posted January 20, 2016 Share Posted January 20, 2016 Looks like you got the array with parity back as it should be so parity should be valid. Have you started the array? Did you back up your cache before you tried this? Link to comment
claira Posted January 20, 2016 Author Share Posted January 20, 2016 So the array started correctly. The cache drive is readable. The VM on it starts no problem. But not the docker container. Update. I moved the docker container to disk 1 and remapped and now it works. I think i'm going to move everything off the cache disk and reformat it. SO I can go back to just 1 drive. My cache disk looks like 64GB SSD and a 256Gb SSD. I have 150GB on it. Added the 64GB disk as a second disk a while ago. Now i'm getting cache disk full errors. Link to comment
JonathanM Posted January 20, 2016 Share Posted January 20, 2016 My cache disk looks like 64GB SSD and a 256Gb SSD. I have 150GB on it. Added the 64GB disk as a second disk a while ago. Now i'm getting cache disk full errors.Adding the second cache drive to the pool activated RAID1 protection, which means your data is mirrored on both drives. The 64GB became the new upper limit to the amount of data that will fit in the cache pool, because the rest of the data would not be protected. End result, you made your cache pool smaller by adding the 64GB. I'm not sure what happens with the remainder of the 150GB above the 64GB capacity, but it's definitely not making the server happy. I assume the balance operation filled the 64GB and then failed. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.