Puppy Linux Discussion Forum

I have tales of strangeness when it comes to external HDD's attached to a variety of machines and operating systems.

How again is this HDD being connected? I have and am using various SATA/IDE adapter types to connect salvaged HDD's from dead desktops to my machines.

This method is pretty reliable but not always. Then there are the NAS type USB drives.......adventure abounds with these things. And of course the many different USB flash drives can all act differently. Some are seen by the systems very easly and others never seem to really work right.

Is this external HDD talked about in this topic have a FAT32 partition of any size on it anywhere?

I have entire machines operating that have dead internal drives and only use USB SATA adaptors and salvaged drives from old 2000's era machines. I have hundreds of HDD from the dumpster/roadside junk machines. Surprised on how long some drives hang on.

I have had drives that were not seen at all after many many tries and lots of tactics used....and suddenly...usually never a known reason why.....suddenly spring to life. These suddenly spool up in speed and I can feel the drive spinning and pop! there it is on the desktop......another ghost in the machine.

The way I have most luck with external HDD's is first a small 1 G FAT32 partition that has the boot flag enabled and next to that the ext3/4 parition

All of the boot loaders like Grub4Dos or Grub2config will be on the FAT32 with the menu.lst boot stanza's pointing to the Puppy Linux distro on the ext3/4 partition.

Troublesome USB connected external HDD seem to work mostly this way. I have a My-Book NAS drive that holds a half terabyte of Puppy's and Dog stuff. It can't seem to be recgonized when the boot flag is set on it. But connected, no boot flag on any partition in it and the boot system on the internal drive can use it very nicely with LABEL or UUID

rockedge wrote: ↑Tue Jun 28, 2022 3:16 pm

How again is this HDD being connected?

All my external drives are self contained accessory items, non of them are rescued from PC’s, so they’re just connected by USB cable.

greengeek wrote: ↑Tue Jun 28, 2022 11:36 am

Your frustration is understandable. The message "is not a bootable device" does offer scope for further investigation.

Are you willing to troubleshoot further?

There are many hardware/software interactions that affect booting.

You are getting closer to a solution - if you don't mind checking a couple more things?

Yes it is frustrating. I haven’t actually kept count, but for arguments sake say you have a dozen distros that you’re trying to do the same thing with, same equipment, methods, etc. 10 of them work perfectly but 2 don’t, you can’t help wondering what the hell is the matter with those 2.

I’m giving it a rest for remainder of this week, but may have another look at it next weekend, so if you want to make any further suggestions feel free, and thank you.

At one point I was going to say that Manjaro, Linux Mint, and all the rest, don’t have a magical ingredient, but in a way perhaps they do. You boot them up from USB stick, click on the “install” icon on the desktop, and away you go, just follow whatever comes up on screen.

It doesn’t matter if it’s a Windows machine that just has a single NTFS partition. Formatting it, setting boot flags and everything else is all automated. Unfortunately Puppy doesn’t have that “luxury”.

@rockedge

These suddenly spool up in speed and I can feel the drive spinning and pop! there it is on the desktop......another ghost in the machine.

Have had many old drives "fail on the shelf". This is usually due to one of three things:
1. the grease in the spindle bearings is old and gets stiff, when the drive gets warm it can loosen and spins up.
2. the read/write head arm bearings, same thing.
3. a read/write head(s) have stuck to the platters. (This one not very common on modern drives that autopark the heads)

wizard

If it is trying to boot the external hard drive and it is not getting to showing a boot loader menu.

You are doing something wrong when you use Grub4dos Config to install the boot loader.

Are you doing this?

First screen choose to install it on the external hard drive.

Select to search only within this device.

Leave all other options unchecked.

Everything else should be OK as default settings.

When asked about writing to the MBR, let it do that.

Keep selecting OK until done.

There is something you are not telling us, but we only know what you do tell us.

You say you are taking all the files from within the Bionicpup ISO and placing them into a directory on the drive partition.
That should work as basically a manual frugal install.
Best if you name this directory bionicpup.
For sure Grub4dos knows that is a Puppy Linux install.

Please post an image of what the Rox file manager shows is in that directory?
That way we know for sure you did that correctly.

Forget about doing installs using the Universal Installer.
It is in bad need of updating.

@stevie pup ,
I have just scanned through this thread.

If you just want to install to the external drive and bootup, in one easy operation, do this:

Download easy-4.2.2-amd64.img from here:

https://distro.ibiblio.org/easyos/amd64 ... 022/4.2.2/

Check the md5sum:

# md5sum easy-4.2.2-amd64.img

...which should be: 4117eaaac576962e4962c2aad0199ae8

Plugin your external drive and write to it. Let's say it is /dev/sdc. Make sure that you write to the entire drive, not a partition:

# dd if=easy-4.2.2-amd64.img of=/dev/sdc bs=1M
# sync

That's it, all done. Just choose the drive in the BIOS-Setup or UEFI-Setup.

The EasyOS image has the Limine bootloader builtin, in a 7MiB fat12 partition, and the second partition is where Easy is installed -- that is ext4, it is 816MiB and will automatically expand the fill the drive.

The Limine bootloader works on legacy-BIOS and UEFI computers.

There really is nothing else to do, you are up and running immediately.

For keeping your personal files, see /files, which is a link to /mnt/sdc/easyos/files, and most apps will default to open and save here.

Note: the easy-4.2.2-amd64.img has a msdos partition table (mbr) so can only handle drives up to 2TB.

EDIT:
Have just now rewritten this page:

https://easyos.org/install/how-to-insta ... w-ssd.html

...applies to any drives, internal or external.

bigpup wrote: ↑Tue Jun 28, 2022 11:58 pm

You are doing something wrong when you use Grub4dos Config to install the boot loader.

Screenshots attached, hopefully.

I've had another go, done everything exactly the same as I did previously, and it still won't boot. But for some mysterious reason this time I've got a different error message, which reads:

error file '/boot/grub/i386-pc/normal.mod' not found

Which means nothing to me. Perhaps someone more knowledgeable can explain and perhaps point me in the right direction for putting it right.

BarryK wrote: ↑Wed Jun 29, 2022 2:14 am

If you just want to install to the external drive and bootup, in one easy operation, do this:

Thank you Barry, if necessary I'll come back to this in a few days.

I've had another go, done everything exactly the same as I did previously

But did you do this when using the Grub4dos Config to install Grub4dos boot loader?:
First screen choose to install it on the external hard drive.

Select to search only within this device.

Leave all other options unchecked.

Everything else should be OK as default settings.

When asked about writing to the MBR, let it do that.

Keep selecting OK until done.

On that image of what is on the drive.
If all it has is one partition sdc1
Seems you have the operating system in that bionicpup directory.

But do you see any of the boot loader files just on sdc1 outside of that directory?

The Grub4dos files you should see on sdc1
.

.
.

Are you able to post screenshots of what Gparted shows for sda, sdb and sdc please?

No need to take any actions - just tell Gparted to look at a drive , take a screenshot then close Gparted. Then repeat for each drive.

Well, success at last, it boots! When I checked what was on the drive the sdc-mbr.-bak file was missing, no idea why as I hadn't told it do anything different. So I deleted the other stuff then ran Grub4Dos again. Checked and everything was there, then booted it up successfully.

So following on from this I decided to install to a different external HD. Again this was successful, but not until the fourth attempt. The previous three all failed, for some inexplicable reason. Throughout this saga I have at no point ever done anything differently in Grub4Dos, I've always done the same thing as shown in the screenshots I posted previously.

So to me a lot of it remains a bit of a mystery, and I can only think of two possible causes. Firstly, that Grub4Dos is a quirky, temperamental thing that does what it wants when it wants? Probably not impossible but equally not likely. The other option is that my external drives are nearing the end of their lifespans, and they have become quirky, temperamental things that do what they want when they want. The fact that I've never had any similar difficulties installing to an internal drive would suggest this as a most likely cause.

Thank you to everyone for the many contributions to this thread, much appreciated. I'm going to mark it as solved, but if anyone ever asks how it was solved I'm going to have a hell of a job trying to explain.

Grub4dos Config is usually rock solid 100%.

There is always a chance of downloading from the internet, software did not get 100% perfect download.

That sdc-mbr.-bak file gets created when some of the Grub4dos stuff gets installed on the drives MBR.
That file is a backup copy of what was originally on the MBR.
If for some reason you wanted to roll back to the original MBR.
This sdc-mbr.-bak file could be used to do that.
So, if that file is not there.
The step to choose to install to the MBR never got done.

I keep asking if you exactly do specific stuff when running Grub4dos Config.
All you tell me is you run it.

bigpup wrote: ↑Thu Jun 30, 2022 12:02 pm

I keep asking if you exactly do specific stuff when running Grub4dos Config.
All you tell me is you run it.

Not sure what you mean by "specific stuff". When I say I just run it I mean I simply open it, click the details as shown in the screenshots in my previous post, and click ok, ok, etc. I don't do anything else.

I specifically wanted to know if you did this:

When asked about writing to the MBR, let it do that.

You got it working.

Forget me trying to figure out what your actual problem was.

I am happy you finally got it working.

Computers and computer software seem to do this to us sometimes.
Trying to do something and it just seems to not be working.
Then it suddenly just works