User Controls
Problem with lap if sophie, lanny or panny are free to help
-
2018-08-05 at 6:32 PM UTC
Originally posted by Sophie If it works after you get the DVD out then problem solved. If you're still getting dropped into a recovery shell see if you can boot properly via USB. It's what i do before i start reading 1000 lines of dmesg output.
its working fine now, i've even put a different dvd in and that's playing fine right now. it was a bit slow booting tho and it did start to run those error codes for about 10 lines or so then it just started up.
. -
2018-08-05 at 6:36 PM UTC^ Bad sectors do exactly that. It will work fine one moment and then won't the next. This is because the bad sectors are not marked off in the system.
-
2018-08-05 at 6:36 PM UTCDope.
-
2018-08-05 at 6:38 PM UTC
Originally posted by NARCassist its working fine now, i've even put a different dvd in and that's playing fine right now. it was a bit slow booting tho and it did start to run those error codes for about 10 lines or so then it just started up.
.
You need to run a file system check to ensure integrity since it was having problems with your encrypted volume. fsck will do this, but you need to know what volume to run it on, hence the reason I was asking for the output of parted /dev/sda 'print'
Typically speaking, you can use: fsck /dev/sda(number for your volume here) to check. -
2018-08-05 at 6:38 PM UTC
Originally posted by -SpectraL ^ Bad sectors do exactly that. It will work fine one moment and then won't the next. This is because the bad sectors are not marked off in the system.
Let it go, Speccy. I already exposed you as a Google copy/paster. Just let it go. Stick to Windows XP. Let Linux boys handle this. -
2018-08-05 at 6:40 PM UTCChecking the file system won't do anything. It has to be a full surface scan.
-
2018-08-05 at 6:46 PM UTC
Originally posted by Grimace You need to run a file system check to ensure integrity since it was having problems with your encrypted volume. fsck will do this, but you need to know what volume to run it on, hence the reason I was asking for the output of parted /dev/sda 'print'
Typically speaking, you can use: fsck /dev/sda(number for your volume here) to check.
i posted the results from parted /dev/sda 'print just now, here they are.
user1@user1-Aspire-5050:~$ sudo parted /dev/sda 'print'
[sudo] password for user1:
Model: ATA FUJITSU MHV2080A (scsi)
Disk /dev/sda: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 768MB 767MB primary ext4 boot
2 769MB 80.0GB 79.3GB extended
5 769MB 80.0GB 79.3GB logical
user1@user1-Aspire-5050:~$
. -
2018-08-05 at 6:50 PM UTC
-
2018-08-05 at 6:51 PM UTCnobody is impressed.
. -
2018-08-05 at 6:58 PM UTC
Originally posted by NARCassist i posted the results from parted /dev/sda 'print just now, here they are.
user1@user1-Aspire-5050:~$ sudo parted /dev/sda 'print'
[sudo] password for user1:
Model: ATA FUJITSU MHV2080A (scsi)
Disk /dev/sda: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 768MB 767MB primary ext4 boot
2 769MB 80.0GB 79.3GB extended
5 769MB 80.0GB 79.3GB logical
user1@user1-Aspire-5050:~$
.
Please run: fsck /dev/sda5 and post the output. -
2018-08-05 at 8:20 PM UTC
-
2018-08-05 at 9:07 PM UTC
Originally posted by NARCassist all i got was that
user1@user1-Aspire-5050:~$ sudo fsck /dev/sda5
[sudo] password for user1:
fsck from util-linux 2.31.1
user1@user1-Aspire-5050:~$
.
It means that no error in the filesystem was found. You can go further with using the Ultimate Boot CD like I mentioned earlier if you wanted to do a manufacturer test on the drive, but you've probably already found your problem - The DVD that was stuck in the drive. -
2018-08-05 at 9:33 PM UTC
-
2018-08-05 at 9:45 PM UTCIf it was the CD drive causing the issues, it wouldn't have given the "unrecoverable read" error.
-
2018-08-05 at 9:59 PM UTC
-
2018-08-05 at 10:03 PM UTC
-
2018-08-05 at 10:06 PM UTC
-
2018-08-05 at 10:10 PM UTCi actually know the exact answer to that but i'm not going to answer since you didn't ask me specifically
-
2018-08-05 at 10:12 PM UTC
-
2018-08-05 at 11:12 PM UTC