Recent Posts

71

Boot Managers / Re: Zu doof für Plop Boot Manager ?

« Last post by GrafZahl2 on February 22, 2021, 09:34:24 AM »

Hallo und Danke für dne Hinweis.
 
Hat sich erledigt. Einen anderen, alten Laptop konnte ich mit USB Stick auf Linux Mint umstellen. Eine Knoppix und eine Linux Mint 14 23-Bit version startete dann auf dem Rechner. Der ist jetzt auf Linux Mint 14 (will aber versuchen, ihn noch auf eine aktuellere Version zu bekommen ... mal sehen, ob die Hardware das noch schafft)

 Dank und Gruß

72

Boot Managers / Re: Zu doof für Plop Boot Manager ?

« Last post by Elmar on February 20, 2021, 19:40:50 PM »

Hallo,

anstelle vom Plop Boot Manager 5 solltest du PlopKexec oder PBM6 probieren. In deinem Fall kannst du die beiden Bootmanager nur von CD starten. Dann kannst du ein System von CD oder USB booten.

LG
Elmar

73

Boot Managers / Zu doof für Plop Boot Manager ?

« Last post by GrafZahl2 on February 20, 2021, 14:28:07 PM »

Hallo zusammen,

ich habe hier einen alten 32-Bit Rechner
Pentium 4
Windows XP SP3
HD 200 GB
Memory 1,5 GB
PIONEER DVD RW  DVR-107D und
SONY DVD-ROM DDU1612
etliche USB slots

Der startet von Festplatte einwandfrei und läuft auch (bis auf einige Blue-Screens ) eigentlich noch tadellos.
Eine (Windows) Installations-CD vom CD oder DVD Laufwerk startet auch problemlos

Ich will den Rechner auf Linux umstellen (am liebsten Linux Mint Cinnamon 32 bit Version).
Einig Linux-ISO Files schon ausprobiert (Bodhi /Linux Mint 17)

Starten nie - weder vom USB Stick noch von CD. 

Nun den Plop boot manager installiert.
Der bringt mir die Bott Auswahl (HD/CD/USB)
Aber bei CD (Bodhi Live) bekomme ich die Meldung "CD not bootable"
Bei USB (1.1) hängt er sich beim Boot load auf.

Damit geht nur HD ... und das ging ja schon immer  

Irgendwelche Tips, was ich noch versuchen könnte ??

   Dank und Gruß
     
 

 

74

Plop Linux / Re: Plop Linux PXE -> NFS does not mount, Error "mount.nfs: Protocol not supported"

« Last post by Elmar on February 11, 2021, 14:05:11 PM »

Booting from NFS3 server is fixed.

Fix: I added the missing files netconfig, protocols and services to the initrd etc.

Please try the 21.1 test version.
https://www.plop.at/en/ploplinux/upcoming/index.html

75

HFS+ Rescue / Re: Struggling to figure out where restored files should show up.

« Last post by Elmar on February 04, 2021, 19:27:22 PM »

It seems that important parts of the old file system are missing and the old structure can't be restored by hfsprescue.

The "x_directory_problem" directory should have valid files. hfsprescue is not able to do more in that case.

76

HFS+ Rescue / Re: Struggling to figure out where restored files should show up.

« Last post by duncanmarshall on February 04, 2021, 19:03:59 PM »

Huh.  I had tried that, but it didn't work.  Seems to be working now.  Perhaps I typed something differently the first time.

Okay, thanks, that's great.  I can now get individual files out.

I still don't know how to recapture my directory architecture though. The restored directory contains newroot, and that contains x_directory_problem and x_unknown, the former of which contains various directory architectures which I don't recognize, and which contain hardly any files.

My one file which I've now successfully found, for example.  How do I find out where that belongs?

77

HFS+ Rescue / Re: Struggling to figure out where restored files should show up.

« Last post by Elmar on February 04, 2021, 15:55:39 PM »

Did you read the paragraph at the end of the output you posted?

At the end you find

Code: [Select]

Use '--ignore-eof' to restore without ExtentsOverFlowFile.


78

HFS+ Rescue / Re: Struggling to figure out where restored files should show up.

« Last post by duncanmarshall on February 04, 2021, 15:50:46 PM »

I assumed so, but it isn't.

79

HFS+ Rescue / Re: Struggling to figure out where restored files should show up.

« Last post by Elmar on February 04, 2021, 15:34:28 PM »

The file will be stored in the directory where you are.

80

HFS+ Rescue / Struggling to figure out where restored files should show up.

« Last post by duncanmarshall on February 04, 2021, 12:42:01 PM »

I've never used this program before.  I have an HFS+ volume from a MacBook that I suspect has bad sectors.  I have no Apple devices to test with.  Instead I have Win7 and Linux.  My Linux install does not mount the HFS+ volume, unlike other working HFS+ volumes.  The MacBook that it came from showed the folder/question mark thing.

I went through the six steps that the hfsprecue documentaion outlines here: https://www.plop.at/en/hfsprescue/recover_files.html

I'm now trying to get just one file for test purposes, like so:

Code: [Select]

https://www.plop.at/en/hfsprescue/recover_files.html
Giving this output:

Code: [Select]

hfsprescue 3.5 2020/09/25 by Elmar Hanlhofer https://www.plop.at

Start: 2021/02/04 11:34:10

*** Force block size: 4096
Signature:                      0x00,  (Unknown)
LastMountedVersion:             , last mount was not done by Mac OS X.
CreateDate:                     1904-01-01 00:00:00  [UID: 0x0]
ModifyDate:                     1904-01-01 00:00:00+0000
BackupDate:                     1904-01-01 00:00:00+0000
CheckedDate:                    1904-01-01 00:00:00+0000
FileCount:                      0
DirCount:                       0
BlockSize:                      4096
TotalBlocks:                    0
AllocationFile StartBlock:      0
ExtentsOverflowFile StartBlock: 0
CatalogFile StartBlock:         16778240
Total size:                     698 GB

Extracting the ExtentsOverflowFile to 'restored/ExtentsOverflowFile'.

You are forcing the block size. I assume, the Volume Header is not correct.
Automatic extracting of the ExtentsOverflowFile has been disabled! This means
strong fragmented files will not be restored! When you want to use the
ExtentsOverflowFile, then you have to restore it manually with '--extract-eof'.
Use '--ignore-eof' to restore without ExtentsOverFlowFile.

I don't see where the file is, or even where it should be.  I'm not really sure where to go from here with the process.