comet424 Posted June 2, 2020 Author Share Posted June 2, 2020 ya you mentioned that and I deleted the corrupted file though.. so I did what you said delete it or replace it..then it should be working perfectly fine and I mentioned I ran the scrub repair after I deleted the file... so I rebooted the unraid and it showed 0 errors I re ran the scrub and I got errors again so does this mean the SSD is no good or do I need to format it? to fix the corrupted SSD or will it come back.. im also finding bin-krusader cant delete files or takes like 10 min or more to delete 1 file where windows can delete the same file instantly.. not sure... but I deleted the file it said in krusader but it didn't delete... so I deleted with windows re emptied recycling bin and now re rerunning scrub to see no errors on SSD hopefully Jun 2 00:05:20 Tower kernel: BTRFS warning (device sde1): checksum error at logical 876900556800 on dev /dev/sde1, physical 874753073152, root 5, inode 3703059, offset 3952824320, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:05:20 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9325, gen 0 Jun 2 00:05:48 Tower kernel: BTRFS warning (device sde1): checksum error at logical 884792160256 on dev /dev/sde1, physical 882644676608, root 5, inode 3703059, offset 3952857088, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:05:48 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9326, gen 0 Jun 2 00:05:48 Tower kernel: BTRFS warning (device sde1): checksum error at logical 884792164352 on dev /dev/sde1, physical 882644680704, root 5, inode 3703059, offset 3952861184, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:05:48 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9327, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261186048 on dev /dev/sde1, physical 889113702400, root 5, inode 3703059, offset 3952914432, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9328, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261190144 on dev /dev/sde1, physical 889113706496, root 5, inode 3703059, offset 3952918528, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9329, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261194240 on dev /dev/sde1, physical 889113710592, root 5, inode 3703059, offset 3952922624, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9330, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261198336 on dev /dev/sde1, physical 889113714688, root 5, inode 3703059, offset 3952926720, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9331, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261202432 on dev /dev/sde1, physical 889113718784, root 5, inode 3703059, offset 3952930816, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9332, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261206528 on dev /dev/sde1, physical 889113722880, root 5, inode 3703059, offset 3952934912, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9333, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261210624 on dev /dev/sde1, physical 889113726976, root 5, inode 3703059, offset 3952939008, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9334, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261214720 on dev /dev/sde1, physical 889113731072, root 5, inode 3703059, offset 3952943104, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9335, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261218816 on dev /dev/sde1, physical 889113735168, root 5, inode 3703059, offset 3952947200, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9336, gen 0 Jun 2 00:06:11 Tower kernel: BTRFS warning (device sde1): checksum error at logical 891261222912 on dev /dev/sde1, physical 889113739264, root 5, inode 3703059, offset 3952951296, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1del.img) Jun 2 00:06:11 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 9337, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10837, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10838, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10839, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10840, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10841, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10843, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10843, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10844, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10845, gen 0 Jun 2 00:06:32 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 10846, gen 0 Quote Link to comment
JorgeB Posted June 2, 2020 Share Posted June 2, 2020 You need to find out what's corrupting the data, or else you fix one file and you get more errors an a new one. Quote Link to comment
comet424 Posted June 2, 2020 Author Share Posted June 2, 2020 im guessing it has to be the SSD... as orginally the errors when I started was SSD to Hotswap module to SATA connector on the motherboard. when I did the testing and the scrubbing and deleting files... that was then SSD to cable to LSI Raid card... and I only get 6 csum errors not like the 500 before.. and it still corupted the file I copied to it …. and if I get 2 SSDS for cache does it do Parity or mirror? and if mirror doesn't it corrupt the mirror? these were the errors.. but I thinking I need to RMA the SSD Jun 2 06:08:01 Tower root: error: /webGui/include/ProcessStatus.php: wrong csrf_token Jun 2 06:57:47 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 11656, gen 0 Jun 2 07:59:03 Tower kernel: BTRFS warning (device sde1): checksum error at logical 13115813888 on dev /dev/sde1, physical 13115813888, root 5, inode 2946948, offset 4377702400, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) Jun 2 07:59:03 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 11657, gen 0 Jun 2 08:31:26 Tower kernel: BTRFS warning (device sde1): checksum error at logical 837234552832 on dev /dev/sde1, physical 837234552832, root 5, inode 2946948, offset 23971860480, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) Jun 2 08:31:26 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 11658, gen 0 Jun 2 08:32:04 Tower kernel: BTRFS warning (device sde1): checksum error at logical 853885153280 on dev /dev/sde1, physical 851737669632, root 5, inode 2946948, offset 1903353856, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) Jun 2 08:32:04 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 11659, gen 0 Jun 2 08:32:28 Tower kernel: BTRFS warning (device sde1): checksum error at logical 865848225792 on dev /dev/sde1, physical 863700742144, root 5, inode 2946948, offset 3021479936, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) Jun 2 08:32:28 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 11660, gen 0 Jun 2 08:32:35 Tower kernel: BTRFS warning (device sde1): checksum error at logical 868864192512 on dev /dev/sde1, physical 866716708864, root 5, inode 2946948, offset 23607009280, length 4096, links 1 (path: domains/Windows Server 2016 (Web Server)/vdisk1.img) Jun 2 08:32:35 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 11661, gen 0 Jun 2 08:32:37 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 11662, gen 0 Quote Link to comment
JorgeB Posted June 2, 2020 Share Posted June 2, 2020 Very unlikely the SSD is the problem for this, also don't forget you have corruption on the array disks, first candidate would be RAM, followed by the board or controller. Quote Link to comment
comet424 Posted June 2, 2020 Author Share Posted June 2, 2020 I RMAing it.. but if I format the Cache drive and re copy the files off the array back to the cache drive... have you seen it fix itself? or its a SSD issue and since I guess after doing a scrub of all the hard drives unraid goes into parity check so its parity checking again.. so I cant try the cache drive on another cable on the LSI Raid card Quote Link to comment
JorgeB Posted June 2, 2020 Share Posted June 2, 2020 Sorry, don't understand the question. Quote Link to comment
comet424 Posted June 2, 2020 Author Share Posted June 2, 2020 ah ok.. well I deleted the corrupted file on the Array.. and then did Empty Recycling bin.. and Its currently doing a Parity check, and I doin a scrub on the disk3 that had the csum errors ram I did 2 Pass's and it passed I used memtest386 before SSD --->Hotswap module ----> SATA Cable to mobo now SSD ---> Cable ----> LSI Raid card also power adapter now directly to the SSD not through the hot swap module.. what else can I test? Quote Link to comment
comet424 Posted June 2, 2020 Author Share Posted June 2, 2020 oh the question is what I mean is.. sorry dislexia have you done it before... Format the SSD to wipe it then.. copy the backup files back to the cache drive appdata domins etc... and did it correct the csum errors or does a Format not cure it.. its just a step I haven't tried yet.. Format Cache.. copy all back,.. hope for the best Quote Link to comment
JorgeB Posted June 2, 2020 Share Posted June 2, 2020 Memtest isn't 100% reliable finding errors, only when if does find some you can be sure there are problems, not finding doesn't mean you can rule out bad RAM. Quote Link to comment
comet424 Posted June 2, 2020 Author Share Posted June 2, 2020 oh well that bites lol... hmmm if I buy ECC ram is that better since the board supports it to get 32gb ram Quote Link to comment
comet424 Posted June 2, 2020 Author Share Posted June 2, 2020 just trying to narrow this down and be affordable now with money being tight too Quote Link to comment
comet424 Posted June 2, 2020 Author Share Posted June 2, 2020 I still cant find out or how do you find out... Unraid is being unresponsive to go into shares so say I have Install Programs or the Videos on the array.. it wont go into those yet the disks are spun up... I know its doing parity check but its worked before... but is there a test or a check to see why its being unresponsive Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.