Re: error on sid laptop: ALERT! /dev/disk/by-uuid/493.....085 does not exist.
Nick Lidakis: [ 2468.452915] sd 2:0:0:0: [sdc] Unhandled error code [ 2468.452919] sd 2:0:0:0: [sdc] [ 2468.452922] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [ 2468.452926] sd 2:0:0:0: [sdc] CDB: [ 2468.452928] Read(10): 28 00 03 7e 20 00 00 00 08 00 [ 2468.452940] end_request: I/O error, dev sdc, sector 58597376 [ 2468.452948] Buffer I/O error on device sdc6, logical block 0 I am not an expert with the exact meaning of these messages, but to me this looks like a hardware error. Since you tested this in a different machine we can probably rule out issues with the controller, cable or PSU. That doesn't leave very much but the disk itself. One other option might be to ensure that AHCI is enabled in your system's BIOS. Some people suggest these messages can be fixed this way. One example: https://bugzilla.redhat.com/show_bug.cgi?id=450848. Do you have port is slow to respond or soft resetting link messages as well? I don't know if this is just corrupted data or a dead/dying SSD. I'll look at the man pages for the S.M.A.R.T tools. A good start is smartctl -a /dev/sdc. If you post the output here, please make sure not to introduce additional linebreaks. Attaching it as a plain text file would be fine. If you have spare space you can try ddrescue. It creates a bit-by-bit copy of your disk (or what's left of it). You can then use photorec or similar tools on that disk image without risking to destroy even more data. J. -- I use a Playstation to block out the existence of my partner. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: error on sid laptop: ALERT! /dev/disk/by-uuid/493.....085 does not exist.
On Thu, Jul 10, 2014 at 02:42:14AM +0200, Jochen Spieker wrote: Nick Lidakis: I've recently been unable to boot into my thinkpad x200s because of this error: ALERT! /dev/disk/by-uuid/493085b does not exist. Dropping to a shell! Most of the Google results are of users changin out disks or partitions and the UUID get messed up. I haven't switched any disks or messed with any partitions. Maybe your disk is corrupt. When you have inserted this disk into another system (or if you boot from a rescue CD) you can take a look whether the /dev/disk/by-uuid/493… path exists. You should also see a new device /dev/sdX and the device nodes for your partitions. I Connected the SSD laptop drive on my desktop via SATA and mounted the root partition. Output of /dev: phobos:/dev/disk/by-uuid# ls 1f9bb8e8-9df8-4216-9386-baf7ccebcc59 88d3b128-1ba4-4511-8428-79b4f0fbbf35 ceea9138-fcca-4342-b4b1-abba566e947b 48f73142-3355-4f5d-98a3-360e6ec03296 ab09f8df-6703-4483-a162-26647bd8884d 493046dc-a036-499a-8e17-33f19a65085b b1946e5e-e4ee-4113-82b4-7a40aecf7935 phobos:/dev/disk/by-uuid# So it's there. But I also tried mounting the /home partition and copying some files. I was able to cd to most directories but ons some I would get: ls: reading directory .: Input/output error And dmesg: [ 2460.794520] Read(10): 28 00 00 00 08 00 00 00 20 00 [ 2460.794539] blk_update_request: 151 callbacks suppressed [ 2460.794543] end_request: I/O error, dev sdc, sector 2048 [ 2460.794549] quiet_error: 152 callbacks suppressed [ 2460.794553] Buffer I/O error on device sdc1, logical block 0 [ 2460.794558] Buffer I/O error on device sdc1, logical block 1 [ 2460.794562] Buffer I/O error on device sdc1, logical block 2 [ 2460.794565] Buffer I/O error on device sdc1, logical block 3 [ 2460.794601] sd 2:0:0:0: [sdc] Unhandled error code [ 2460.794605] sd 2:0:0:0: [sdc] [ 2460.794608] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [ 2460.794611] sd 2:0:0:0: [sdc] CDB: [ 2460.794613] Read(10): 28 00 00 00 08 00 00 00 08 00 [ 2460.794624] end_request: I/O error, dev sdc, sector 2048 [ 2460.794628] Buffer I/O error on device sdc1, logical block 0 [ 2468.452821] sd 2:0:0:0: [sdc] Unhandled error code [ 2468.452831] sd 2:0:0:0: [sdc] [ 2468.452835] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [ 2468.452840] sd 2:0:0:0: [sdc] CDB: [ 2468.452843] Read(10): 28 00 03 7e 20 00 00 00 20 00 [ 2468.452860] end_request: I/O error, dev sdc, sector 58597376 [ 2468.452868] Buffer I/O error on device sdc6, logical block 0 [ 2468.452873] Buffer I/O error on device sdc6, logical block 1 [ 2468.452877] Buffer I/O error on device sdc6, logical block 2 [ 2468.452880] Buffer I/O error on device sdc6, logical block 3 [ 2468.452915] sd 2:0:0:0: [sdc] Unhandled error code [ 2468.452919] sd 2:0:0:0: [sdc] [ 2468.452922] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [ 2468.452926] sd 2:0:0:0: [sdc] CDB: [ 2468.452928] Read(10): 28 00 03 7e 20 00 00 00 08 00 [ 2468.452940] end_request: I/O error, dev sdc, sector 58597376 [ 2468.452948] Buffer I/O error on device sdc6, logical block 0 I don't know if this is just corrupted data or a dead/dying SSD. I'll look at the man pages for the S.M.A.R.T tools. Nick -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140716142812.GA4167@phobos
Re: error on sid laptop: ALERT! /dev/disk/by-uuid/493.....085 does not exist.
Nick Lidakis: I've recently been unable to boot into my thinkpad x200s because of this error: ALERT! /dev/disk/by-uuid/493085b does not exist. Dropping to a shell! Most of the Google results are of users changin out disks or partitions and the UUID get messed up. I haven't switched any disks or messed with any partitions. Maybe your disk is corrupt. When you have inserted this disk into another system (or if you boot from a rescue CD) you can take a look whether the /dev/disk/by-uuid/493… path exists. You should also see a new device /dev/sdX and the device nodes for your partitions. J. -- I want to keep my skin looking good but I believe all computers do the same job. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
error on sid laptop: ALERT! /dev/disk/by-uuid/493.....085 does not exist.
I've recently been unable to boot into my thinkpad x200s because of this error: ALERT! /dev/disk/by-uuid/493085b does not exist. Dropping to a shell! Most of the Google results are of users changin out disks or partitions and the UUID get messed up. I haven't switched any disks or messed with any partitions. Mounted the disk on desktop to grab the grub.cfg and fstab: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc/proc procdefaults0 0 # / was on /dev/sda1 during installation UUID=493046dc-a036-499a-8e17-33f19a65085b / ext3 errors=remount-ro 0 1 # /home was on /dev/sda6 during installation UUID=ceea9138-fcca-4342-b4b1-abba566e947b /home ext3defaults 0 2 # swap was on /dev/sda5 during installation UUID=b1946e5e-e4ee-4113-82b4-7a40aecf7935 noneswapsw 0 0 /dev/sdb1 /media/usb0 autorw,user,noauto 0 0 I'd figure I'd ask the list first before I royally screw something up. Any suggestions? Nick -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140708213326.GA5939@phobos
