bakslaash Posted February 24, 2020 Share Posted February 24, 2020 Hello - I was hoping someone might be able to point me in the right direction. I've tried upgrading the OS to 6.8.2 multiple times and have the same issue each time. When I login post reboot following the upgrade, the system cannot see my western digital drives. All the others are seen. When I revert back to version 6.6.6 the drives are visible and everything is back in order. Did something change in 6.8.2 that I need to update in my config? I'm the first to admit that I am a novice when it comes to this, but please see attached for the diagnostic file. Any tips or pointers would be greatly appreciated! tower-diagnostics-20200224-1441.zip Quote Link to comment
JorgeB Posted February 25, 2020 Share Posted February 25, 2020 The problem isn't the WD disks, it's the Marvell controller they are connected to, this can sometimes help. P.S. Your flash drive is showing some read errors: Feb 24 14:02:33 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 24 14:02:33 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Feb 24 14:02:33 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Feb 24 14:02:33 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 2b 82 00 00 91 00 Feb 24 14:02:33 Tower kernel: print_req_error: critical medium error, dev sda, sector 11138 Feb 24 14:02:33 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 24 14:02:33 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Feb 24 14:02:33 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Feb 24 14:02:33 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 2b 82 00 00 01 00 Feb 24 14:02:33 Tower kernel: print_req_error: critical medium error, dev sda, sector 11138 Feb 24 14:02:33 Tower kernel: FAT-fs (sda1): FAT read failed (blocknr 11136) Try chkdsk first, but it might be failing. Quote Link to comment
bakslaash Posted February 26, 2020 Author Share Posted February 26, 2020 Thanks, johnnie.black! That did the trick. I inserted the "iommu=pt perimeter (see code below) to the /syslinux/syslinux.cfg file and things seem to be working. Really appreciate the response! append initrd=/bzroot iommu=pt 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.