Re: [Dorset] Having repository troubles
-- Next meeting at *new* venue: Bournemouth, Tuesday, 2018-12-04 20:00 Check if you're replying to the list or the author Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Having repository troubles
-- Next meeting at *new* venue: Bournemouth, Tuesday, 2018-12-04 20:00 Check if you're replying to the list or the author Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] UEFI help
Does the problem still exist? Can I be confident that if I disable the secure boot that both Win 10 and Linux will run? In my experience, you might have to disable quickboot as well, as Windows likes to leave stuff in RAM on shutdown. Are there any particular makes of laptop that should be avoided in the context. Not sure what to avoid, but I know Dell likes supporting Linux in their products toba certain extent, so customer support might be better there. Greetings: Rafi -- Next meeting: Bournemouth, Tuesday, 2017-09-05 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
Re: [Dorset] Data recovery
> > > Had the computer been booted recently before your attempt that failed? > Sometimes, the boot can be broken by an upgrade but then lie there > unused for weeks until something else triggers a reboot and the failure > is associated with the recent event. > Yes, I had used Windows and then booted Ubuntu twice before the incident. To change from Windows to Ubuntu and vice-versa I would go into the BIOS settings and change the system from UEFI to LEGACY (or vice-versa). I also noticed it saying something about too many primary partitions? Could it be that it had somehow "forgotten" about the extended partition and interpreted it all as primaries (meaning 8 instead of 4)? Rafi -- Next meeting: Bournemouth, Tuesday, 2017-08-01 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
Re: [Dorset] Data recovery
I've got it all fixed! Was being really quite stupid about it, sorry for spamming you all. In the end I just mounted the internal partition on Rescatux and an external one and used cp. Couldn't have been simpler. Thanks for all help. Rafi -- Next meeting: Bournemouth, Tuesday, 2017-08-01 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
Re: [Dorset] Data recovery
sda5 is the Windows-data partition, sda6 is the Linux-data partition -- Next meeting: Bournemouth, Tuesday, 2017-08-01 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
Re: [Dorset] Data recovery
I've managed to boot Rescatux without anz problems and ran the Boot Repair tool, these are the results (Windows was installed in German, so I've translated the hexdump messages underneath each partition): Boot Info Script e7fc706 + Boot-Repair extra info [Boot-Info 9Feb2015] = Boot Info Summary: === => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1913536512 of the same hard drive for core.img. core.img is at this location and looks for (,gpt7)/boot/grub. sda1: __ File system: ntfs Boot sector type: Windows 8/2012: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: sda2: __ File system: vfat Boot sector type: Windows 8/2012: FAT32 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files:/EFI/Boot/bootx64.efi /EFI/Microsoft/Boot/bootmgfw.efi /EFI/Microsoft/Boot/bootmgr.efi /EFI/Microsoft/Boot/memtest.efi sda3: __ File system: Boot sector type: - Boot sector info: Mounting failed: mount: unknown filesystem type '' sda4: __ File system: ntfs Boot sector type: Windows 8/2012: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: sda5: __ File system: ntfs Boot sector type: Windows 8/2012: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: sda6: __ File system: ext4 Boot sector type: - Boot sector info: Operating System: Boot files: sda7: __ File system: ext4 Boot sector type: - Boot sector info: Operating System: Boot files:/boot/grub/i386-pc/core.img sda8: __ File system: BIOS Boot partition Boot sector type: Grub2's core.img Boot sector info: Drive/Partition Info: = Drive: sda _ Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Partition Boot Start SectorEnd Sector # of Sectors Id System /dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT GUID Partition Table detected. PartitionStart SectorEnd Sector # of Sectors System /dev/sda1 2,048 616,447 614,400 Windows Recovery Environment (Windows) /dev/sda2 616,448 821,247 204,800 EFI System partition /dev/sda3 821,248 1,083,391 262,144 Microsoft Reserved Partition (Windows) /dev/sda4 1,083,392 1,092,442,111 1,091,358,720 Data partition (Windows/Linux) /dev/sda5 1,952,602,112 1,953,523,711 921,600 Windows Recovery Environment (Windows) /dev/sda6 1,092,442,112 1,913,536,511 821,094,400 Data partition (Linux) /dev/sda7 1,913,540,608 1,952,602,11139,061,504 Data partition (Linux) /dev/sda8 1,913,536,512 1,913,540,607 4,096 BIOS Boot partition "blkid" output: Device UUID TYPE LABEL /dev/loop0 2016-01-18-14-17-40-00 iso9660 Rescatux0.40b5 /dev/loop1 squashfs /dev/sda120744F25744EFCD2 ntfs Wiederherstellung /dev/sda22850-67CA vfat /dev/sda3 /dev/sda4009656839656795C ntfs /dev/sda55ABC86E9BC86BECF ntfs /dev/sda6366879c2-d9bd-490e-9c8e-33600481c26b ext4 /dev/sda763a80713-588d-49c1-9bc4-7fdcafdd422e ext4 /dev/sda8 /dev/sr0 2016-02-16-11-39-33-00 iso9660LXFDVD209 = "ls -l /dev/disk/by-id" output: == total 0 lrwxrwxrwx. 1 root root 9 Jul 30 16:26 ata-HGST_HTS721010A9E630_JR10006P11PNZF -> ../../sda lrwxrwxrwx. 1 root root 10 Jul 30 16:27 ata-HGST_HTS721010A9E630_JR10006P11PNZF-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Jul 30 16:26
Re: [Dorset] Data recovery
I just tried to boot SystemRescueCD multiple times and it either reboots or freezes or goes blank, any clue what might be going on? -- Next meeting: Bournemouth, Tuesday, 2017-08-01 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
Re: [Dorset] Data recovery
> I believed I was done and wanted to copy the contents of the > Linux-data partition onto an external (internal with adapters) HDD > from Clive. Is this drive much used normally, or could there be hardware/connection problems that your use has just happened to show up? Apparently Clive has used it multiple times without any problems. > I unmounted the other two partitions I didn't need, added a folder in > the desired partition using root and wanted to copy my data across. It > wouldn't copy Any idea what the error was? Was it from cp(1) or something else? I didn't see any error messages. > The desired partition appeared twice now As icons somewhere, or when listing the partition table? On the desktop and in the file manager, gparted only showed one. > with the newly-connected partitions being unable to mount Do you recall the error? "Mount" was grayed-out on right-click and in gparted > I had a feeling something had gone terribly wrong and rebooted. Grub > rescue appeared, stating I was missing a normal.mod file. Does this external (internal) drive normally have anything to do with booting? I'm trying to tell whether problems are limited to this one drive. If booting doesn't use it there's oddness elsewhere too? Nope, the hard drive is for storing purposes only. > Clive then got a SystemRescueCD Livedisk out and I tried to use > TestDisk to recover my data. Recover it from where? There was the original NTFS, where you deleted files and copied the rest to ext4. That ext4's content was then copied to the problematic NTFS on the external (internal) drive. This still leaves ext4, on a different disk, with the files? And perhaps the original NTFS too. The Windows-data partition may or may not contain the data, the Linux-data partition contains the data, all other HDDs faild to copy from the Linux-data partition and contain none of my data. My guess is that the final destination drive had problems; perhaps the destination ext4 partition on that drive got re-mounted read-only when the kernel saw those problems and that stopped the copy continuing. I think that could be, but I couldn't understand why I'd have difficulties booting thereafter, as the only files I changed were either in the Windows partitions or in the /home directory, which shouldn't influence booting. When things started playing up you may have found dmesg(1) output, or journalctl(1), or /var/log files, had some kernel complaint from the filesystem, or `re-mounting' message. I didn't get any terminal outputs during the process but haven't looked at any log files, will do. > Any advice would be greatly appreciated. Stick to the command line where possible so what's happening under the covers is more understood, and errors are passed up with less "translation" by a GUI. Will do. Boot again into a separate live system, like SystemRescueCD, and examine the partition tables of the disks for starters to get a good idea of what's left standing. I use `parted /dev/sda unit B print' as root, e.g. sudo. I shall do that and report, thank you. -- Next meeting: Bournemouth, Tuesday, 2017-08-01 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
