Jump to content

mwoods98

Members
 View Profile  See their activity

  • Posts

    124

  • Joined

  • Last visited

 Content Type 

Posts posted by mwoods98

    Disk vanishes after about 33% on pre-clear?

    in General Support

    Posted

    I'm in the process of adding a new drive and I started the pre-clear process by adding it into my disk shelf. I started the preclear process last night and when I got up this morning I noticed pre-clear had stopped. 

     

    I took the drive out, of the shelf, placed it back and started he process again. Then just about 10 mins ago, I noticed the process stopped again?!? 

     

    I have included the diags - When going back the drive is not mounted and even on the disk shelf, the light is off. I'm going to try a new slot just in case there is something wrong with that specific slot

    tower-diagnostics-20210128-1302.zip

    Moved drives to Disk Shelf and some of them are complaining (showing wrong identification) (SOLVED)

    in General Support

    Posted

    2 minutes ago, trurl said:

    Stop array 

    Reassign that disk

    Start array to begin rebuilding 

    Got it and rebuild has started. I'll repeat the process for all of the other disks. 

    One final question, I turned off the dockers for this process but it does bring the array back online. Should they be turned off or it doesn't matter?

     

    Thanks  @trurl and everyone else who chimed in!

    Moved drives to Disk Shelf and some of them are complaining (showing wrong identification) (SOLVED)

    in General Support

    Posted

    17 minutes ago, trurl said:

    no.

     

    Do not physically remove. 

     

    Stop array. 

    Unassign one of the problem disks.

    Start array with disk unassigned. 

    Verify the emulated disk is mounted. 

     

    Then post a screenshot since there seems to be some confusion. 

    Hi @trurl thanks for pitching in.

     

    I have:

    Stopped the array

    unassigned the problem disk

    started the array

    verified the emulation

    image.thumb.png.bdda8863cbfcf52c145de4d7730c96b7.png

    Disk 5 is the disk. I have clicked on it to view the emulated contents.

     

    Now, here's the part I'm fuzzy with - I can copy the contents ( I have used unbalance to do this before) but I am not sure how to kick off the re-build process to 

    put that disk back into place and have it rebuild.

     

     

     

    Moved drives to Disk Shelf and some of them are complaining (showing wrong identification) (SOLVED)

    in General Support

    Posted

    1 minute ago, JorgeB said:

    I think it's your best bet, it worked many times before for similar situations, and you don't have much to lose, just don't rebuild on top if the emulated disk doesn't mount correctly.

    Ok @JorgeB,

     

    Just asking can the parity rebuild from 5 drives that have been "lost" ? I'm also just going to double check, stop the array, remvoe the device, start the array, it should emulate the drive then reassign and rebuild. Just wanted to make sure I am understanding correctly. 

     

    Thans just trying to be extra cautious @Squid can you verify?

    Moved drives to Disk Shelf and some of them are complaining (showing wrong identification) (SOLVED)

    in General Support

    Posted

    6 hours ago, Vr2Io said:

    Pls wait a moment, in first, I want to check you change controller from which to which .... But seems not a change

     

    82:00.0 SCSI storage controller [0100]: Broadcom / LSI SAS1068E PCI-Express Fusion-MPT SAS [1000:0058] (rev 08)
        Subsystem: Broadcom / LSI SAS1068E PCI-Express Fusion-MPT SAS [1000:30a0]
        Kernel driver in use: mptsas

     

    It seems just add expander ( NETAPP   DS424IOM6 ) in between, pls confirm this, I never think add a expander will cause disks unmontable. BTW, SAS1068E really not recommand and how come it support more then 2TB disks. Pls provide more detail what hardware have change.

     

    Suggest don't start array, it could corrupt whole array. 

     

    According below info. seems 1068E work with any size SAS disk ( still no BIOS support ), but not SATA.

    https://xpenology.com/forum/topic/9908-lsi-1068e-disk-support-2tb-bios-disabled/

     

    @Vr2Io to give more details: The disk shelf is a Netapp DS4246 - When I had it in the older (dying) server I was using this card - LSI SAS3801E // L3-01123-04E PCI-E 3GB/s Dual Port - to build a new machine while the old one was up I bought another card - LSI Logic SAS3801E PCIe 3GB/s miniSAS 8-Port Host Bus Adapter with 2x SFF-8088 That's the listing of the card currently in the new server - I can swap the older card into the new machine if you think this will help fix some of the issues. I thought the cards we identical.  I have the old card and can swap it out to see if that will help things. 

     

    If I do this, would I need to do the new configuration and assign the drives again? 

    Note: I did start the array to try to figure out what's wrong. It has been up for about 14 hours. 

    The cards that I have can see the larger drives without issue so far.

     

    Thanks for all the help and suggestions in helping to work to get this fixed. 

    Moved drives to Disk Shelf and some of them are complaining (showing wrong identification) (SOLVED)

    in General Support

    Posted · Edited by mwoods98

    Today was the big moving day to move the drives to the disk shelf. I removed all of the drives from the old machine and put them all in the disk array. When I started unraid, I got a stale configuration as some of the drives had been marked missing. Note: not every drive that was moved came up with this error. Looks like 5 have trouble. I looked up the error which said stale configuration and wrong disk: https://forums.unraid.net/topic/66673-drive-identification-wrong-on-some-disks-after-634-to-64-upgrade/ - The recommendation was creating a new config with leaving the parity as correct.

    After doing that I still have those 5 disks wanting to be formatted! Yikes!

    image.thumb.png.762d5f1b11abc220782982bf87258824.png

     

    I did have a snapshot of the orignal config and the disks are in the right slots:

    ORG config before moving

     

    image.thumb.png.db4f20a2bed4683b92f59e169cee961f.png

     

    This is when I had that trouble with the disk that had been resolved.

    I'm not sure what to do next. I don't know if the parity drive can re-build from this?

    Thanks for the help!

     

    Diags and smart info for the drives included:

     

     

     

    tower-smart-20210118-2317.zip tower-smart-20210118-2316 (2).zip tower-smart-20210118-2316 (1).zip tower-smart-20210118-2316.zip tower-diagnostics-20210118-2300.zip

    Kinda upgrading to a new server..

    in General Support

    Posted

    So.. I'll try to have as much detail in this as possible:

     

    I have a unraid happily installed on a server for over 2 years. Everything was fine: Last year in march I added a disk shelf and added more drives. Still fine, I noticed about 2 weeks ago my server would not boot up from a reboot. The MOBO was complaining it had no memory. I managed to get it up and working but have to take the memory back to the DIMM's I used when I bought it (roughly 1/2 the memory is gone the machine would not post with it in there) 

     

    So now with the sever limping along, I decided to order a new one and switch things over. Here is where it gets tricky. I have about 6 drives installed in the 4U (OLD) server.

     

    What I would like to do is: Move most of the drives to the disk shelf but I'm hoping its only complicated as removing all of the drives from the 4U server, putting them in the drive shelf and booting into unraid. 

     

    To further complicate things, I looked at the sever today and I see this:

    image.png.8ca6b80a8c779ba58f951ac1d9393281.png

     

    I can't pull smart info from it so I'm guessing the drive is bad.

    I have enough space to have I think have unraid rebuild or move the emulated contents to other drives but not sure whats the best way to handle moving over all

    of the other drives with this apparent dead drive. 

     

    Open to any and all suggestions.

     

    Thanks

     

     

    Cache drive full?

    in General Support

    Posted

    So this happened the other day. I was organizing some Plex Media into folders like A-M and N-Z. After doing that, I noticed that almost half of my cache drive was used up. I'm guessing this is in relation to the move. Can I recoup that space? 

    [Support] Djoss - FileZilla

    in Docker Containers

    Posted

    image.thumb.png.f9969cddf9c8d9cc11cd3a06d935b67b.png

    I just fired up Filezilla after using it a lot. Nothing has changed but I see this when starting the docker. 

    When I hover over the x it says server disconnected code 1006

    The logs on the server have this:

      

    ** (filezilla:926): WARNING **: 13:02:02.643: invalid source position for vertical gradient


** (filezilla:926): WARNING **: 13:02:02.671: invalid source position for vertical gradient


** (filezilla:926): WARNING **: 13:02:02.671: invalid source position for vertical gradient


** (filezilla:926): WARNING **: 13:02:02.682: invalid source position for vertical gradient


** (filezilla:926): WARNING **: 13:02:02.682: invalid source position for vertical gradient


** (filezilla:926): WARNING **: 13:02:02.747: invalid source position for vertical gradient


** (filezilla:926): WARNING **: 13:02:02.747: invalid source position for vertical gradient


** (filezilla:926): WARNING **: 13:02:02.755: invalid source position for vertical gradient


** (filezilla:926): WARNING **: 13:02:02.755: invalid source position for vertical gradient

29/08/2020 13:17:52 Got connection from client 127.0.0.1
29/08/2020 13:17:52 other clients:
29/08/2020 13:17:52 Got 'ws' WebSockets handshake
29/08/2020 13:17:52 - webSocketsHandshake: using base64 encoding
29/08/2020 13:17:52 - WebSockets client version hybi-13

29/08/2020 13:17:52 Disabled X server key autorepeat.
29/08/2020 13:17:52 to force back on run: 'xset r on' (3 times)
29/08/2020 13:17:52 incr accepted_client=1 for 127.0.0.1:59822 sock=10
29/08/2020 13:17:52 webSocketsDecodeHybi: got frame without mask
29/08/2020 13:17:52 rfbProcessClientProtocolVersion: read: I/O error

29/08/2020 13:17:52 client_count: 0
29/08/2020 13:17:52 Restored X server key autorepeat to: 1
29/08/2020 13:17:52 Client 127.0.0.1 gone
29/08/2020 13:17:52 Statistics events Transmit/ RawEquiv ( saved)
29/08/2020 13:17:52 TOTALS : 0 | 0/ 0 ( 0.0%)
29/08/2020 13:17:52 Statistics events Received/ RawEquiv ( saved)
29/08/2020 13:17:52 TOTALS : 0 | 0/ 0 ( 0.0%)

     

    Preclear plugin

    in Plugin Support

    Posted

    Hi have been getting some errors when trying to run preclear.

     

    So, with my new shiny Easystore 14TB drive freshly shucked. I put it in my Disk Array (NetApp DS4246 Disk Array Shelf) to get precleared and working to add to the array.

     

    Well, that didn't go to well. Here is a snip from the log when trying to preclear. 

    Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112883, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112884, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112885, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112886, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112887, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112888, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112889, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112890, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112891, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112892, lost async page write
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576904088
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576905112
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576906136
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576907160
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576908184
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576909208
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576910232
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576911256
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576912280
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865984, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865985, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865986, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865987, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865988, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865989, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865990, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865991, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865992, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865993, lost async page write
Jul 30 01:58:00 Tower preclear_disk_9RJ8E21C[6825]: Zeroing: dd if=/dev/zero of=/dev/sdai bs=2097152 seek=820609286144 count=13179910356992 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Jul 30 01:58:26 Tower preclear_disk_9RJ8E21C[6825]: Zeroing: dd output: dd: error writing '/dev/sdai': No space left on device
Jul 30 10:34:24 Tower kernel: sd 6:0:25:0: [sdai] Spinning up disk...
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] Write Protect is off
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] Mode Sense: 8b 00 00 08
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] Attached SCSI disk
Jul 30 13:19:24 Tower kernel: sd 6:0:28:0: [sdai] Spinning up disk...
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] Write Protect is off
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] Mode Sense: 8b 00 00 08
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] Attached SCSI disk

     

    Now Preclear does see the device but when I click on it to start it just pauses. I have tried this with the tape trick and without, the result is still the same. I'm very curious about the no space left on the drive line.

    Any suggestions and I have attached diags to this for review.

     

    Update:

     

    I swapped the shelf just to see if by any chance if it was a specific tray that was in error and preclear started

     

    Then it failed at 6%

    image.png.0ad0778b78837d24dd0762404a6f9b67.png

     

    Logs for this attempt: 

    Jul 30 01:58:27 preclear_disk_9RJ8E21C_6825: error encountered, exiting...
Thu Jul 30 15:17:02 EDT 2020: PHP Warning: unlink(/tmp/preclear_stat_sdab): No such file or directory in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 430
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 1 --frequency 4 --cycles 1 --skip-preread --skip-postread --no-prompt /dev/sdab
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Preclear Disk Version: 1.0.16
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: S.M.A.R.T. info type: default
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Disk size: 14000519643136
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Disk blocks: 27344764928
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Blocks (512 bytes): 27344764928
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Block size: 512
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Start sector: 0
Jul 30 15:17:15 preclear_disk_9RJ8E21C_28163: Zeroing: emptying the MBR.
Jul 30 15:17:16 preclear_disk_9RJ8E21C_28163: Zeroing: dd if=/dev/zero of=/dev/sdab bs=2097152 seek=2097152 count=14000517545984 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Jul 30 15:17:16 preclear_disk_9RJ8E21C_28163: Zeroing: dd pid [29334]
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409167+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858085392384 bytes (858 GB, 799 GiB) copied, 5695.68 s, 151 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409168+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409168+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858087489536 bytes (858 GB, 799 GiB) copied, 5802.18 s, 148 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409169+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409169+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858089586688 bytes (858 GB, 799 GiB) copied, 5908.68 s, 145 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409170+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409170+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858091683840 bytes (858 GB, 799 GiB) copied, 6015.17 s, 143 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409171+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409171+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858093780992 bytes (858 GB, 799 GiB) copied, 6123.96 s, 140 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409172+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409172+0 records out
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858095878144 bytes (858 GB, 799 GiB) copied, 6230.45 s, 138 MB/s
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409173+0 records in
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409173+0 records out
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858097975296 bytes (858 GB, 799 GiB) copied, 6336.95 s, 135 MB/s
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: dd process hung at 858100072448, killing....
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Continuing disk write on byte 858097975296
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd if=/dev/zero of=/dev/sdab bs=2097152 seek=858097975296 count=13142421667840 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd pid [16519]
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd - wrote 858097975296 of 14000519643136.
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: elapsed time - 1:48:17
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd command failed, exit code [1].
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: dd: error writing '/dev/sdab': No space left on device
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 1+0 records in
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 0+0 records out
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 0 bytes copied, 0.00130157 s, 0.0 kB/s
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: error encountered, exiting...

    I'm not sure if it's the drive or something else. I'm going to see if I can just connect to a PC to see if it mounts and reads

     

     

     

     

     

     

     

     

     

    tower-diagnostics-20200730-1417.zip

    Errors on Preclear #yikes

    in General Support

    Posted

    Update: So checking back this drive failed at about 6%

    image.png.630abceedc995d5a4262c36aa28cc409.png

     

    Logs from Preclear:

      

    Jul 30 01:58:27 preclear_disk_9RJ8E21C_6825: error encountered, exiting...
Thu Jul 30 15:17:02 EDT 2020: PHP Warning: unlink(/tmp/preclear_stat_sdab): No such file or directory in /usr/local/emhttp/plugins/preclear.disk/Preclear.php on line 430
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 1 --frequency 4 --cycles 1 --skip-preread --skip-postread --no-prompt /dev/sdab
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Preclear Disk Version: 1.0.16
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: S.M.A.R.T. info type: default
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Disk size: 14000519643136
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Disk blocks: 27344764928
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Blocks (512 bytes): 27344764928
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Block size: 512
Jul 30 15:17:14 preclear_disk_9RJ8E21C_28163: Start sector: 0
Jul 30 15:17:15 preclear_disk_9RJ8E21C_28163: Zeroing: emptying the MBR.
Jul 30 15:17:16 preclear_disk_9RJ8E21C_28163: Zeroing: dd if=/dev/zero of=/dev/sdab bs=2097152 seek=2097152 count=14000517545984 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Jul 30 15:17:16 preclear_disk_9RJ8E21C_28163: Zeroing: dd pid [29334]
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409167+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858085392384 bytes (858 GB, 799 GiB) copied, 5695.68 s, 151 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409168+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409168+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858087489536 bytes (858 GB, 799 GiB) copied, 5802.18 s, 148 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409169+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409169+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858089586688 bytes (858 GB, 799 GiB) copied, 5908.68 s, 145 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409170+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409170+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858091683840 bytes (858 GB, 799 GiB) copied, 6015.17 s, 143 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409171+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409171+0 records out
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858093780992 bytes (858 GB, 799 GiB) copied, 6123.96 s, 140 MB/s
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409172+0 records in
Jul 30 17:05:45 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409172+0 records out
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858095878144 bytes (858 GB, 799 GiB) copied, 6230.45 s, 138 MB/s
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409173+0 records in
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 409173+0 records out
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 858097975296 bytes (858 GB, 799 GiB) copied, 6336.95 s, 135 MB/s
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: dd process hung at 858100072448, killing....
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Continuing disk write on byte 858097975296
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd if=/dev/zero of=/dev/sdab bs=2097152 seek=858097975296 count=13142421667840 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Jul 30 17:05:46 preclear_disk_9RJ8E21C_28163: Zeroing: dd pid [16519]
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd - wrote 858097975296 of 14000519643136.
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: elapsed time - 1:48:17
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd command failed, exit code [1].
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: dd: error writing '/dev/sdab': No space left on device
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 1+0 records in
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 0+0 records out
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: Zeroing: dd output: 0 bytes copied, 0.00130157 s, 0.0 kB/s
Jul 30 17:05:49 preclear_disk_9RJ8E21C_28163: error encountered, exiting...

     

    Errors on Preclear #yikes

    in General Support

    Posted · Edited by mwoods98

    So, with my new shiny Easystore 14TB drive freshly shucked. I put it in my Disk Array (NetApp DS4246 Disk Array Shelf) to get precleared and working to add to the array.

     

    Well, that didn't go to well. Here is a snip from the log when trying to preclear. 

    Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112883, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112884, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112885, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112886, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112887, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112888, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112889, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112890, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112891, lost async page write
Jul 29 19:21:17 Tower kernel: Buffer I/O error on dev sdai, logical block 197112892, lost async page write
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576904088
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576905112
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576906136
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576907160
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576908184
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576909208
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576910232
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576911256
Jul 29 19:21:17 Tower kernel: print_req_error: I/O error, dev sdai, sector 1576912280
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865984, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865985, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865986, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865987, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865988, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865989, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865990, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865991, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865992, lost async page write
Jul 30 01:58:00 Tower kernel: Buffer I/O error on dev sdai, logical block 197865993, lost async page write
Jul 30 01:58:00 Tower preclear_disk_9RJ8E21C[6825]: Zeroing: dd if=/dev/zero of=/dev/sdai bs=2097152 seek=820609286144 count=13179910356992 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Jul 30 01:58:26 Tower preclear_disk_9RJ8E21C[6825]: Zeroing: dd output: dd: error writing '/dev/sdai': No space left on device
Jul 30 10:34:24 Tower kernel: sd 6:0:25:0: [sdai] Spinning up disk...
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] Write Protect is off
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] Mode Sense: 8b 00 00 08
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 30 10:34:40 Tower kernel: sd 6:0:25:0: [sdai] Attached SCSI disk
Jul 30 13:19:24 Tower kernel: sd 6:0:28:0: [sdai] Spinning up disk...
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] Write Protect is off
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] Mode Sense: 8b 00 00 08
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 30 13:19:39 Tower kernel: sd 6:0:28:0: [sdai] Attached SCSI disk

     

    Now Preclear does see the device but when I click on it to start it just pauses. I have tried this with the tape trick and without, the result is still the same. I'm very curious about the no space left on the drive line.

    Any suggestions and I have attached diags to this for review.

     

    tower-diagnostics-20200730-1417.zip

×
×
  • Create New...