May somebody can give me a hint. I am still using my old squeeze and it works the way I want. But my recent post about changing the owners rights, e.g. 777 or 755 anyway, it could be 644 as well. While configuring a new pc, just by chance I discovered how to enter the BIOS. And here it comes. I want to install from an usb-stick the debian-7.8.0-amd64-netinst.iso.
Allright, there should be no obstacle so far. But this usb-stick was formatted in ext4 on another debian 7.8 machine and this very usb-stick now is refusing me as root on squeeze to unpack even in the terminal the package. No matter if I try chmod, chown 644 -d name-of-the-file. I don't have permission to do so. That would mean for my humble understanding that this device has won a hardlink to the other machine, I truly don't have a clue. Is there someone out there who could give me a hint. Thanks a lot in advance, I keep gouging my way through this. Maybe I am wrong, and there is no hardlink, but only root can act as rwx, the rest is set to r.
this is what I get, after typing as root.
but it is such a package to be unpacked, I did it before, earlier version of wheezy, and where I am doing wrong?
maybe something like this:
yep, luky strike...it worked.
but after solving this, on rebooting after the changes of the BIOS, there comes up, the real grewsome two aspects.
changes to the American Megatrends Bios version 2.15.1236 in the boot sequence are not saved, even clicking so. I switches back to EFI or UEFI and furhtermore it tells me that there is no BIOS fils in this usb key. Where the hack do I slam in to that usb key any bios file. After rebooting the screen tells me about grub rescue. So the BIOS itself saves the BIOS to the storage device with a strange name, that means...never use a large usb-device for that, unless you have to much of them. But grub rescue> after rebooting continues. So any hints to that. Thanks in advance!!!
Last edited by 1in10; 03-24-2015 at 11:56 PM..
Reason: solved and new problem on the horizon, grub rescue
I've never attempted to 'read' an iso file using RAR.....
Instead i've always used mount, to then copy the files out of the mounted path, as you did for your own surprise.
I do not even understanding why you are surprised that an ISO file is not a RAR-archive?
Or how you associate this with with a hardlink issue, thats quite something different.
In regards how you attempt to read an iso file i must ask, how did you write that iso file onto your usb stick?
No, the BIOS doesnt store 'itself' on the stick.
But there must be files readable by the bios on the stick in order to boot, those are required, however they are not 'bios' (nor (u)efi either)
Simple said, (probably) technicly incorrect:
Your computer looks according to its config/setting for either an (U)EFI or a BIOS file on the device selected to load (hdd, cd/dvd, usb), if none required file was found, it reports that no OS could be detected and the booting fails.
An ISO is not an archive, it is a raw disk image -- a raw cdrom/dvd/bluray disk image. This is why it works with mount, not archiver tools. It has to be something which understands cdrom format.
As an answer to sea, the BIOS of the version mentioned up above requires such a written line on the usb-media, though unpacked. It is an msi-board, the menu itself got some 12 entries for the boot sequence. So it may wasn't correct to put it like this, but until UEFI or something like this, I really never had to make such a fuss writing or connecting the boot media with on single bit of the BIOS. Or even a command-line for such a media. Who may is into this trouble with UEFI may knows about this. Nonetheless I am repairing my GRUB.
And yes he may looks to a former partition with an MBR, because there has been a pre-installed version of UBUNTU. As my attempt was to get unetbootin to install another OS (Debian). My problem startet. In this very case it is not the OS, whether UBUNTU or anything else, it is UEFI that stubbornly blocks any attempt to get access.
I must be a fool to think there still is a MBR. This has been ages ago, nowadays it is called "shiny new Globally Unique Identifiers partition table (GPT)".
Last edited by 1in10; 03-25-2015 at 05:36 PM..
Reason: new information for GRUB2
Getting a bit upset about GRUB RESCUE> that requires some commands like
ls, set. set prefix=(hd0.1) I put on another usb-stick the so called rescue-kit as mentioned here Rescue your Windows & GNU/Linux systems - Rescatux & Super Grub2 Disk , I took the
super_grub2_disk_i386_efi_2.00s2.iso and after plugging it into the usb-port asking the commands mentioned above.
ls is telling me, there are as follows:
while setting the following command at
there occurs the message:
Before that the error message was:
throwing me back to
After changing several times the boot sequence in the UEFI-Bios, saving it and exit, to try to reboot, the same procedure.
So I tried :
always coming back to grub rescue> the same procedure as every time,
then
and looping back to
grub rescue>
even trying
gives me no reply at all. The first repair-kit is on an usb-drive formatted in FAT32 to repair grub. Entering the BIOS it is flashing from the usb-drive.
Before all that I tried without success to execute the commands above with
sda for SATA-hdd.
And not even
seems to work. Think I am done with uefi. :-(
---------- Post updated at 11:42 PM ---------- Previous update was at 09:54 PM ----------
Starting now in efi mode the mobo tells me startup.nsh, wow, backslashes all over the place. This shell must be nuts.
This link gets me some help https://packages.debian.org/wheezy/grub-efi-amd64
allthough I am at the very beginning of this.
...great.
while trying to unpack the rescue-kit on my usb-device, at the laptop there it says after typing
where the directory named /save is containing the debian-file. So there is a conflict at the basic, where the usb-drive with this very specific debian-packet is on an usb-drive that is formatted in FAT32 to fullfill the requirements of UEFI but working in the wrong place.
Any hints for this nutshell of microsoft? Setting the SATA to another plug? Thanks in advance.
quote:
"This represents only the beginning of the uses and benefits of EFI shell commands and scripts. Not only can EFI be used similarly to a MS-DOS device driver, its capabilities also remove the hassle of modifying the OS. Disk utility vendors can use EFI to craft powerful tools like platform-independent disk partitioning. Another of EFI's benefits is that the same device drivers can be used by many EFI-compliant platforms, thus providing a good return on investment. EFI allows users to create device drivers to access hardware directly without having to go through the OS, making the process both simpler and faster."
I would probably set all my rubber points here to get some real help for creating a boot device on a usb-stick. There is no CD-drive on this machine, thats why I need to use a usb-stick. And scrumming in a CD-drive to fuddle around in the fstab or something like that is out of reach.
My wisdom so... (9 Replies)
I am trying to use a USB (Pen?) drive on Unixware 7.1.4.
The USB stick is in the machine and the machine recognises it when I enter usbprobe as follows:
Path - Address Description
-----------------------------
+++++++ BUS #2
0 - 1 - HUB "UHCI Root Hub"
1 - 2 - HID "Chicony Wireless Device"... (1 Reply)
hi
Howto mount an USB stick under SCO 5.0.7?
BTW ist it possible to mount USB stick in the command line using 'tools' at the Boot: prompt from OpenServer Release 5.0.7 installation CD? (1 Reply)
Hey Guys
I have an Ubuntu CD and I was thinking of creating like a bootable hard drive with various OS so that I can just boot OSs with t drive and not require the CDs. I was just wondering is there a way I can do this, like have Ubuntu boot from a USB stick? If yes how is that possible(even if I... (3 Replies)
Hello,
i am using a solaris thinclient that tries to connecting to a terminalserver. (RDP) Everything works fine, but the usb redirection. If i put in a usb stick i always get 2 usb-drives mounted. If i look in /tmp/SUNWut/mnt/<name of the host> i see 2 devices. One with the name of the... (2 Replies)
When mounting a USB stick or pen drive on a FreeBSD machine I always issue the following command:
mount -t msdosfs /dev/da0s1 /mnt
Something I have always wondered is what the option msdosfs stands for and more importantly, why it is necessary. (7 Replies)
Dummies questions, perfect for this. I cannot mount my idiotic usb stick on Slackware, I input the following on non-graphic mode as root:
Mount -t vfat /dev/sdc1/usbstick
usbstick is the folder i created for mounting my USB, the file system is FAT, and everytime I input that I get some kind... (2 Replies)
I have a P-Series Machine running AIX 5.3, it has a USB Port on the front of the server, can I use a USB Stick on AIX platforms?? if so how..:rolleyes: (2 Replies)
Hello Everybody
I am planning to install Fedora core 8 on an extra PC I have; what I wanna do is to boot from a USB stick then install Fedora from an ISO image I already have via FTP. Could any one tell me how to create bootable USB Stick for Fedora as I already found how to install from FTP... (0 Replies)
I got Puppy linux and installed it on a usb stick.
In the BIOS i selected to boot from USB-FDD but it goes to my HD and ignores the USB stick,
What going on ?? (2 Replies)