Error in boot-uponly with win98 HDD installed

Gents:
Desire to report a bug in arch 0.5 downloaded Oct 18, 2003.
Utilized arch 0.5 for some time but after installing arch linux, slackwareeline 9.0 and slackware linux 9.1 along with windows 98 in my system I encountered inability to load arch 0.5 until win98 HDD was removed.
Initial setup of the system operated correctly, each linux OS capable of mounting partitions of the other, whether it was arch to slackware or the reverse. This capability was in addition to accessing vfat on two HDD having fat file systems(one is a USB device the other the secondary slave. However, upon reboot, an fsck fail occurred asking for: " mount -n -o remount, rw/" . This notation appears in : man fsck....
I wish to pursue a bug description since this indicates a cross OS fault with win98 file systems/HDD.
The boot is selected in bios before initiating same.
How do I submit a bug?

Sorry I must be more careful in describing the complex problem.
I utilize a pciide card to extend hdd capability,
I change boot-up HDD in bios for four mobo HDD as is standard.
I cannot boot on pciide card hdd's.
I have win98 on sec-slave, with no other OS partitioned.
I have slackware 9.0 attached to pciide slot sec-master with no partitions to other OS's.
I have slackware 9.1 attached to pri-master when used as the in-use HDD. It has access to partitions on arch, win98, and slckware 9.0.
I can install arch in pri-slave when using slackware as OS.
I can install arch as OS and slackware 9.0 as pri-slave and have access to partitions on all other HDD.
I also have a USB HDD which is accessible from the OS in all cases.
The problem in arch 0.5 is that after setting up the accessibilities in Linux and win98 HDD's, at next reboot I could not pass fsck. This condition persisted until I removed the win98HDD which cleared the problem.
In win98, the OS does not recognize any Linux HDD's.
In arch0.5, the presence of win98 HDD prevents arch 0.5 from booting.
I read ....."man fsck"... and it refers to drives as "/dev/hda...etc" and this type of ID does not apply to kernel 2.4.21 which uses /dev/discs/discX/partx and therefore I feel therein lies a bug. This seems to be true since I am booting kernel 2.4.21 in arch0.5 which ID's hdd's in a mode other than specified in fsck.
If fsck "sees" the win98HDD through the /dev/hdx search(supposedly a multiple parallel hdd check) it most certainly will fail the arch0.5 boot-up AFAICT.
Perhaps I have improved your understanding of my problem..I use lilo for booting and have ....append="hde=ide-scsi ide=reverse" to allow for pciide ID after mobo ID and to enable cdrw in pcide slot primary-pri.
If further info needed, I am ready to try.

Similar Messages

Dual Boot Selection with two SSD Installed

I have two SAMSUNG SSD's installed in the W540.
SSD #1 -- Microsoft Windows 7 Professional
SSD #2 -- Microsoft Windows 7 Ultimate
The SSD's had a complete install of each Microsoft Windows operating system without using the dual boot manager. I select teh SSD to boot from by using teh F12 key at boot time.
On my previous computer (HP EliteBook Workstation 8560w), the BIOS had a option to display a boot selection menu for me to select from without having to manually select the option to display. The boot selection menu gave me 20-30 seconds to select a alternative boot option. If I did not respond it woudl boot to the primary drive.
Can the Lenovo W540 be setup the same way? I can find no options in the latest BIOS.

I am honestly dubious that your previous HP machine had anything in the BIOS to provide this "Boot Manager" functionality you've described. Your description is exactly what Boot Manager in Windows does, which probably what was in effect on your HP machine.
Now you say you installed two separate versions of Windows on two separate drives, and without involving Windows Boot Manager. That suggests to me that you unplugged the other SSD when you did each install, so that the Windows installer didn't even know about the other bootable OS when doing its current install. If it had seen the other pre-existing bootable Windows, then the second install would have triggered the creation of a 2-OS boot menu (identical to what you say you saw on your old HP machine). You could still have two bootable Windows, on two separate drives (or, you could also have installed to two separate partitions on one drive if you wanted to), and at boot time Boot Manager would present the menu to you and you'd select one or the other. The most recent Windows to get installed would probably have made itself the "default", so that after 10-30 seconds it would auto-boot to that Windows if you didn't arrow up/down and press ENTER to select the other Windows for this particular boot.
The BIOS of the machine has a "boot sequence" setup, and one of your two SSD drives MUST be first, in front of the other. So at boot time by default (in the absence of F12 to select a boot device) the BIOS would normally go to THAT "first" drive in the boot sequence list, locate the "active" partition on that drive (where Boot Manager is assumed to live), and start the boot process. If Boot Manager sees a 1-OS boot menu, it just goes to that partition (as C, where Windows lives on that drive) and starts Windows. If a 2-OS boot menu exists, Boot Manager presents it to you and you decide which Windows you want to boot to.
When you push F12 at boot time, you simply say to the BIOS "let me pick which of my drives I want you to go to, to then find the "active" partition on that drive to kick off the boot process". Since you did two completely independent Windows installs, I would say that you probably have a "system reserved" partition (which is marked "active") on each SSD, along with a C system partition (for Windows) on each SSD. So you can actually boot to either drive, via F12, or you can just let the machine boot to whichever one you know to be first in the boot sequence list.
But... if you'd simply installed your second Windows to the second SSD while the first Windows/SSD was still cabled and visible, the second Windows install would have done everything you're now asking to be done. The existing 1-OS boot menu (on the first SSD) would have been seen and updated by the Windows installer, to add the second Windows to the menu which would thus now be a 2-OS boot menu. The second Windows would get installed wherever you wanted it to get installed (i.e. to the second SSD), and all would be well with the world.
Note that had this taken place, no second "system reserved" partition (marked "active", and housing the second copy of Boot Manager) would have been created on the second SSD with the second installed Windows. The existing "system reserved" (marked "active", and living on the first drive in the BIOS boot sequence list) would simply have had its boot menu updated from 1-OS to 2-OS, and you'd be home free right now.
This is exactly how Boot Manager works. I'm sure your old HP machine had such a setup, with your two Windows installed sequentially over time, and with the second one recognizing the first one's existence and adding itself to the boot menu to produce a 2-OS boot menu which is what you saw. That wasn't from the BIOS. It was from Windows Boot Manager handling a 2-OS boot menu.
So, what can you do now? Well, technically, you only need one "active" partition (i.e. "system reserved", where Boot Manager lives) on the first SSD in your BIOS boot sequence list. You won't need the second "system reserved" which in my opinion was probably created (unnecessarily) when you did your second Windows install with the first SSD temporarily disconnected.
But the goal here is to get the 1-OS boot menu that's on the first SSD "system reserved" partition updated, to add the second Windows on the second SSD, producing a 2-OS boot menu. And to do that you can use a wonderful 3rd-party product named EasyBCD. It is a tool to maintain your boot menu, and you can manually do things after-the-fact (like now) which you should have done before, or simply to perform maintenance or changes.
So, with both SSD's cabled and operational (your current booted Windows will appear as C, and probably your other drive's Windows partition will thus appear as D to the current booted Windows), you run EasyBCD. It really doesn't matter which Windows is on the first SSD and that is first in the BIOS boot sequence, only that it will be the boot menu in the "system reserved" partition on that drive which will be manipulated by EasyBCD to become the 2-OS menu. You can make either Windows the default (which will auto-boot in 10 seconds if you don't select the other Windows), no matter which SSD it's on.
You can view the current boot menu (from the currently booted Windows) via EDIT. You pick which entry is to be the "default".
To add a new entry to the boot menu, push the ADD button and navigate to the drive (D) the Windows to be added lives on.
If you don't already have same, I would recommend you have a "system image" backup of both of your bootable Windows drives (to an external USB 3.0 drive, ideally), so that if you're skittish about doing this you'll at least be able to quickly and easily restore what you currently have from your backups.
But believe me, EasyBCD can be trusted to do exactly what you want to do... which is to create a 2-OS boot menu on your first drive's "system reserved" partition. This 2-OS boot menu will name BOTH of your two bootable Windows, from your two SSD drives. You won't need to push F12 to select the boot device, just let the machine go to the first drive in the boot sequence and kick off Boot Manager, and the rest will behave exactly as you are now seeking.
Let me know if you have questions. And for sure, let us know how it turns out.

Can't boot computer with 10.5 install CD or Single User Mode, or Safe Mode.

Ive written a couple times about this and responded to people who have similiar queeries but i just havent gotten any answers.
I cannot log onto my computer, I boot up and get a blue screen, with a nice black arrow. Thats as far as i can get. Obviously happening to lots of people..So, ive tried rebooting holding the C key and with 10.5 install CD, ive tried Unix (command-S), Ive tried resetting PR Ram, ive tried mantra recitation and cooing to my laptop; ive tried all the shortcuts in Oreilly's book and the only thing that DOES work is holding the OPTION key while rebooting. This brings up a nice icon of a padlock and a place to type letters or words and then there is another arrow in a box. Is this Open Firmware? I dont have an open firmware password...Ive tried entering my user password but it doenst accept it. ( I did change my password last week, did that create these problems???) how do i by pass that password????? Is it open firmware? (the date reads 1904 when i do the command option-O F command, and i cant get beyond that either...HELP!!

Hello,
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Utilities from the Installer menu at the top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access the Menubar at top.
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Reset Password from the Installer menu at the top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Reset Password.
Space between mount & -uw, space between -uw & the /
rm /var/db/.applesetupdone
Space after rm, before the 1st /

Am I able to install Windows 7 in Boot Camp with this HDD partition setup?

I recently upgraded from Snow Leopard to Lion, and my Boot Camp partition was obliterated beyond recognition. Fortunately I have backups, but I'm having issues re-installing Windows 7. This is what my disk looks like:
Mac OSX - Current Lion partition
Untitled - Where Boot Camp / Windows 7 used to live...
Shared - 1TB of shared data... Media/Documents/etc
This is the error I get when trying to install Windows 7 with Boot Camp Assistant...
From what I can tell, this means I won't be able to do it without wiping the Shared partition? Or is there a workaround I can use? I'd really hate to have to move all of it over to an external hard drive, since I don't have one with 750GB of free space handy...
And would this probably happen again once Mountain Lion comes out? I'll be getting that pretty much on launch, so should I hold off on messing around with this if I'll likely have to do it all again in a few weeks?
Thanks in advance to anyone who can help!
- Mark

Why don't you invest in a 1.5TB drive and case? And add to that a TimeMachine drive (and a small 40GB or even less "Emergency OS X" partition on it... a must - could even have clone of Lion and Lion Recovery on it, AND TimeMachine partition.
If you don't have a backup, it almost always will "rain" on the parade.
If you try booting from Windows 7 DVD and aim it at the parittion, what happens? tried?
To use BCA yes it is one partition and one way only.
You could remove " - " the UNTITLED volume and then expand Mac OS volume to fill that area, or plan for and setup Lion Recovery space too.
http://support.apple.com/kb/HT4718
People have managed. Usually planning ahead up front for a setup like this.
CLONE OS X and ~ or install Lion on an external drive and create a Lion Recovery partition.
http://www.bombich.com/software/ccc.html
http://macperformanceguide.com/Mac-HowToClone-backup.html
http://macperformanceguide.com/Mac-HowToClone.html

Boot issue with External HDD since OSX 10.10

Hi
Wanted to share my experience and I hope someone can help me here. I have a 2TB USB3.0 LaCie Minimus HDD that worked just fine on OSX 10.9 and even Windows 8.1. However since Yosemite (10.10) every single Mac (MacPro, MacBookPro) that I plug the HDD to will not longer boot-up normally (cold boot) IF the HDD is turned on. Power off the HDD every Mac on 10.10 will boot normally. However reboot and wake-up from sleep work fine.
To make sure I explained my self correctly.
Power off your mac on OSX 10.9, have the 2TB USB3.0 LaCie Minimus HDD (powered on) connected to your Mac. then power it on back and no problems.
Power off your PC with Win 8.1, have the 2TB USB3.0 LaCie Minimus HDD (powered on) connected to your PC. then power it on back and no problems.
Power off your mac on OSX 10.10, have the 2TB USB3.0 LaCie Minimus HDD (powered on) connected to your Mac. then power it on back and the Mac boot will be stuck until your power off the 2TB USB3.0 LaCie Minimus HDD.
Also note that Rebbot and wake from sleep work just fine in every situation and OSs. I reseted the PRAM, SMC, and tested the HDD on a Fresh 10.10 install as well as on a 10.10 upgrade and a Old 10.9.X MacBookPro.
To make sure it was not a partition problem I formatted the drive and removed all partitions (EFI) several times on each OSs... Same result.
Finally I contacted LaCie and I am waiting for their feedback.
Message was edited by: Akiba-Seattle

Here you are!
PS Thanks for helping. In My case it was disk2
XXXs-Mac-Pro:~ XXX$ diskutil info -plist disk0
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Bootable</key>
<false/>
<key>BusProtocol</key>
<string>PCI</string>
<key>CanBeMadeBootable</key>
<false/>
<key>CanBeMadeBootableRequiresDestroy</key>
<false/>
<key>Content</key>
<string>GUID_partition_scheme</string>
<key>DeviceBlockSize</key>
<integer>512</integer>
<key>DeviceIdentifier</key>
<string>disk0</string>
<key>DeviceNode</key>
<string>/dev/disk0</string>
<key>DeviceTreePath</key>
<string>IODeviceTree:/PCI0@0/RP05@1C,4/SSD0@0/PRT0@0/PMP@0</string>
<key>Ejectable</key>
<false/>
<key>FreeSpace</key>
<integer>0</integer>
<key>GlobalPermissionsEnabled</key>
<false/>
<key>IOKitSize</key>
<integer>251000193024</integer>
<key>Internal</key>
<true/>
<key>LowLevelFormatSupported</key>
<false/>
<key>MediaName</key>
<string>APPLE SSD SM0256F Media</string>
<key>MediaType</key>
<string>Generic</string>
<key>MountPoint</key>
<string></string>
<key>OS9DriversInstalled</key>
<false/>
<key>ParentWholeDisk</key>
<string>disk0</string>
<key>RAIDMaster</key>
<false/>
<key>RAIDSlice</key>
<false/>
<key>SMARTStatus</key>
<string>Verified</string>
<key>SolidState</key>
<true/>
<key>SupportsGlobalPermissionsDisable</key>
<false/>
<key>SystemImage</key>
<false/>
<key>TotalSize</key>
<integer>251000193024</integer>
<key>VolumeName</key>
<string></string>
<key>WholeDisk</key>
<true/>
<key>Writable</key>
<true/>
<key>WritableMedia</key>
<true/>
<key>WritableVolume</key>
<false/>
</dict>
</plist>
XXXs-Mac-Pro:~ XXX$ diskutil info -plist disk2
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Bootable</key>
<false/>
<key>BusProtocol</key>
<string>USB</string>
<key>CanBeMadeBootable</key>
<false/>
<key>CanBeMadeBootableRequiresDestroy</key>
<false/>
<key>Content</key>
<string>GUID_partition_scheme</string>
<key>DeviceBlockSize</key>
<integer>512</integer>
<key>DeviceIdentifier</key>
<string>disk2</string>
<key>DeviceNode</key>
<string>/dev/disk2</string>
<key>DeviceTreePath</key>
<string>IODeviceTree:/PCI0@0/PEG0@1/BR00@0/BR13@1/XHC1@0</string>
<key>Ejectable</key>
<true/>
<key>FreeSpace</key>
<integer>0</integer>
<key>GlobalPermissionsEnabled</key>
<false/>
<key>IOKitSize</key>
<integer>2000398934016</integer>
<key>Internal</key>
<false/>
<key>LowLevelFormatSupported</key>
<false/>
<key>MediaName</key>
<string>ST2000DM 001-1ER164 Media</string>
<key>MediaType</key>
<string>Generic</string>
<key>MountPoint</key>
<string></string>
<key>OS9DriversInstalled</key>
<false/>
<key>ParentWholeDisk</key>
<string>disk2</string>
<key>RAIDMaster</key>
<false/>
<key>RAIDSlice</key>
<false/>
<key>SMARTStatus</key>
<string>Not Supported</string>
<key>SupportsGlobalPermissionsDisable</key>
<false/>
<key>SystemImage</key>
<false/>
<key>TotalSize</key>
<integer>2000398934016</integer>
<key>VolumeName</key>
<string></string>
<key>WholeDisk</key>
<true/>
<key>Writable</key>
<true/>
<key>WritableMedia</key>
<true/>
<key>WritableVolume</key>
<false/>
</dict>
</plist>
XXXs-Mac-Pro:~ XXX$ diskutil cs list
No CoreStorage logical volume groups found
XXXs-Mac-Pro:~ XXX$
XXXs-Mac-Pro:~ XXX$ sudo gpt -vv -r show /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=251000193024; sectorsize=512; blocks=490234752
gpt show: /dev/disk0: PMBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 490234751
      start       size index contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6
         40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640 488555536      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
488965176    1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
490234712          7
490234719         32         Sec GPT table
490234751          1         Sec GPT header
XXXs-Mac-Pro:~ XXX$
XXXs-Mac-Pro:~ XXX$ sudo gpt -vv -r show /dev/disk2
gpt show: /dev/disk2: mediasize=2000398934016; sectorsize=512; blocks=3907029168
gpt show: /dev/disk2: PMBR at sector 0
gpt show: /dev/disk2: Pri GPT at sector 1
gpt show: /dev/disk2: Sec GPT at sector 3907029167
       start        size index contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6
          40      409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409640 3906357344      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
3906766984      262151
3907029135          32         Sec GPT table
3907029167           1         Sec GPT header

Boot Failure with HP HDD

I have an old Vectra VL420 mini tower which I've used to install 3 different operating systems on 5 different IDE Ultra ATA hard drives from different manufacturers. The drives range in size from 40G to 200G.
I have a second, socket 370, system which I built myself using an ASUS TUV4X motherboard. I have used this system to install two different operating systems, each on its own drive.
Both systems run without issue, but here's the rub:
1) I can boot my Vectra with the drives from my home-built system, but...
2) I cannot boot the home-built system with any one of the Windows (Win 2k Pro and XP home) drives from the Vectra, nor can I slave any one of the Vectra's Windows drives to it.
3) I have one drive with an old Red Hat OS that will boot either system.
4) The home-built will not boot if I swap its optical drive with one from the Vectra.
When I try to boot the home-built with the Vectra loaded Windows drives the sequence of events is always the same:
1) Power on...
2) Fans come on and drives start to spin up. This last for about 2 or 3 seconds before...
3) The system shuts itself off (power off). It doesn't even stay up long enough for a BIOS screen to appear.
This also happens when I swap the optical drive with the Vectra's.
I get the impression that the motherboard takes one quick look at the hardware, doesn't like what it sees, and shuts down.
I've spent a lot of time with the TUV4X owner's manual trying to see if there was some parameter in the BIOS or some switch/jumper on the motherboard that would solve this issue. I'm reasonably certain this is a dead end.
I'm beginning to think that there's something peculiar about the way HP formats drives. Perhaps it even modifies the firmware on them.
Any ideas?
Thanks in advance,
Pat

Hi dragnoak,
I'm talking about the USB cable that came with my Navigon 72 Plus. I bought this GPS navigator 2 years ago, which means that I used the cable 8 times (I update the maps 4 times/year), always on my X220t.
I plugged it into the A520's USB 3 port for the first time last week. You know what happened.
I said that the cable has been "destroyed" because I don't know the right English word, but you should understand what that means: the cable stopped working during the first half hour. After that I tried to connect my GPS to the X220t, but to no avail.
Same thing happened to my "pass-through" e-cigarette (it is equipped with a micro-USB port at the bottom). After a few hours the red LED next to the port turned off and the battery stopped charging. I had to order a new cable.
Neither the GPS nor the e-cigarette were damaged, only the cables. Strange things happen sometimes...
I have no doubt that your USB 3 ports work like a charm. Mine don't, since day 1. My external USB 3 compatible HDD is plugged into a USB 2 port, otherwise I can't save anything onto it (just read). In short, I have two useless USB 3 ports. I am not complaining, just talking about a fact.
@TLC2013,
I apologize for using your topic to report my own issues...
X220t | i7 | 320GB HDD | 8GB RAM | WIN7 PRO
IdeaCenter A520 | i5 | 1 TB HDD | 6GB RAM | WIN8.1

Boot issues with Win98. Safe Mode Boot only. Not all drives detected...

Hello guys! This is a great source of information and I've learned a TON browsing this place (on company time, hehe), but I've hit a road block that I can't maneuver around.
System Config
Neo K8T Neo Fisr mobo
Athlon64 3200+ CPU
1 Gig Kingston RAM
Ti4200 64 MB video card
520 Watt Antec Power Supply (after getting schooled by Bas's great posts on the importance of PSUs, I found out my lame-o 350 watt (!!!!) PSU, errr, ain't gonna quite cut it.)
Problem:
Windows98 won't boot all the way to normal mode. It only boots to safe mode. Apparently a driver issue?
Symptoms/Clues:
- Only detects my Western Digital harddrive (and only after some finegling)
- Wierdness with my 1.44 3.5" floppy (A:) drive. At first the BIOS would tell me the A: drive was there, regardless of whether it was plugged in. Then I plugged in the A: drive and Win98 in safe mode couldn't read from it. Right now, I don't have my A: drive connected and it's not in my Boot Order sequence (hard drive only for now).
- BIOS doesn't detect my new CD-ROM (SONY) drive at all. Note, this is a brand new drive that was NOT on my old system.
- I disabled the S.ATA controller. (This was confusing because there's an option to disable some SATA thing under an "Integrated Peripherals" menu. However, there's another setting to disable s SATA thing under a PCI Controller's menu. Seemed vague to me,, but then it's been a while since I've done this sort of thing.)
- I cleared the CMOS earlier because of wierdness were the system would hang on bootup and would ask me about starting a "Flash Recovery" process, upon which it would just sit there ( I left it running overnight once).
Call for help
Unfortunately I have no boot floppies, so I was hoping this was something I could fix without one, perhaps by changing some BIOS settings. Maybe it's a RealTek Boot Agent thing?
Any help is appreciated!
BamaBoy

Im running win 98se with no real problems, and its doing so well that I still dont even feel like trying anything else..........
I'd say RE-clear your c-mos , using the jumper, and unplugging the power for 5 seconds..... then reset your bios settings.......Also, maybe just reinstall the via 4-in1 chipset drivers...... I remember fiddling with some bios setttings before, like the acpi by os or by bios etc.... that helped.....but its been awhile......The great thing about 98 is that you CAN tweak so much.......
You can reinstall over itself also, which can help redetect the hardware, yyou should always have the 98 files on the hard drive so you dont need the floppy or cd...... So many things you can try....... Resolve yourself to trying as many as possible , its fun when you get it right........... My prob. is that I never remember what I did to fix stuff heheheheh.......good luck
ps, the "flash recovery" thingy has to do with the realtek ethernet lan thingy....which you should disable in its bios.....I forgot how to get to it, I think F11 or something like that while it shows when you are booting....Then it will still ask when you boot, but wwont hang......

Boot problems with second Arch install on an IDE drive

I have two SATA II drives and two IDE drives (one HDD and one optical) in my box. I had Arch installed on first SATA II drive (/dev/sda). I changed the mkinitcpio files to load sata modules before pata, and that works okay. So, my IDE HDD is now /dev/sdc
However, I installed a second Arch onto the /dev/sdc (IDE) and it won't boot. It goes through booting process and hangs at checking the drives claiming that the /dev/sda3 has bad superblock. Now, this is really odd, because /dev/sda3 is a SWAP partition, and the init script is trying to run e2fsck on it.
How do I fix this? Should I simply (somehow) disable the filesystem check?
(Before you ask, I need the second Arch to build a LiveCD.)

It's correctly identified as Linux Swap partition. Besides, the first Arch install is still working with that swap partition reporting no problems at boot time.
Here's the output of fdisk -l:
Disk /dev/sda: 160.0 GB, 160040803840 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x4a424a41
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3824 30716248+ 7 HPFS/NTFS
/dev/sda2 3825 7654 30764475 83 Linux
/dev/sda3 7655 7903 2000092+ 82 Linux swap / Solaris
/dev/sda4 7904 13982 48829567+ 5 Extended
/dev/sda5 7904 13982 48829536 83 Linux
Disk /dev/sdb: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x4fa7b7a5
Device Boot Start End Blocks Id System
/dev/sdb1 1 48641 390708801 42 SFS
Disk /dev/sdc: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xec0c2373
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 5 40162 83 Linux
/dev/sdc2 6 136 1052257+ 82 Linux swap / Solaris
/dev/sdc3 137 1666 12289725 83 Linux
/dev/sdc4 1667 9964 66653685 83 Linux
And just in case, the menu.lst used to boot both Arches:
# (0) Arch Linux
title Arch Linux
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/sda2 ro vga=791
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/sda2 ro
initrd /boot/kernel26-fallback.img
# (1) Windows
title Windows XP
rootnoverify (hd0,0)
makeactive
chainloader +1
# (2) Arch Linux
title ArchGem
root (hd1,0)
kernel /vmlinuz26 root=/dev/sdc3 ro vga=791
initrd /kernel26.img
# (3) Arch Linux
title ArchGem Fallback
root (hd1,0)
kernel /vmlinuz26 root=/dev/sdc3 ro

I am getting the error Installation came back with 17002 when installing Office 365 ProPlus from a network share

I have gotten this error several times, but It works fine on most machines
Here is the most recent example of the log file:
Timestamp Process TID Area Category EventID Level Message Correlation
08/08/2014 11:28:29.131 SETUP (0xef8) 0x1964  Click-To-Run amaxp Medium BaseConfigure::TryGetConfiguration: EULA's have been accepted.
08/08/2014 11:28:29.134 SETUP (0xef8) 0x1964  Click-To-Run aoh85 Medium AdminConfigure::HandleStateAction: Configuring an install/crosssell scenario.
08/08/2014 11:28:29.136 SETUP (0xef8) 0x1964  Click-To-Run aqdco Monitorable TryCheckNetworkCost::HandleStateAction: Failed to initialize NetworkCostManager for http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675.
Assuming low cost and proceeding.
08/08/2014 11:28:29.136 SETUP (0xef8) 0x1964  Click-To-Run aoh9i Medium TryGetVersionDescriptor::HandleStateAction: Getting Cab: v64_15.0.4631.1002.cab
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anwv6 Medium Descriptor::Load: Reading Available value from descriptor: 15.0.4631.1002
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run amawt Medium Descriptor::Load: Prereq Node exists. Being parsing it.
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anwv7 Medium Descriptor::Load: Reading Bootstrapper value from descriptor: 15.0
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run amax8 Medium TryGetVersionDescriptor::HandleStateAction: Descriptor contains Prereqs. Run them now.
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed.
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anwwb Medium IsNativeValidator::CheckPreReq: returning: 1.
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed.
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run an8w1 Medium O15BetaValidator::CheckPreReq: Validator has version descriptor
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run an8w6 Medium O15BetaValidator::CheckPreReq: No Office 15 installation detected. Prereq check passes.
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run an8xa Medium O15BetaValidator::CheckPreReq: returning: 1.
08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed.
08/08/2014 11:28:30.146 SETUP (0xef8) 0x1964  Click-To-Run anwwn Medium SXSValidator::CheckPreReq: Cross bitness test passed.
08/08/2014 11:28:30.146 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed.
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anwwp Medium BootstrapperValidator::CheckPreReq: returning: 1.
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed.
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run an8w0 Medium ClientValidator::CheckPreReq: returning: 1.
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed.
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anwwe Medium DiskSpaceValidator::CheckPreReq: Free disk space is sufficient.
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed.
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run aoh9n Medium TryGetClient::HandleStateAction: Installation path is: C:\Program Files\Microsoft Office 15
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run amaya Medium TryGetClient::HandleStateAction: Looking for existing client.
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run amayd Medium TryGetClient::HandleStateAction: Did not find an existing client. Downloading a new one.
08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run aon8l Medium TryGetClient::HandleStateAction: Getting Cab: i641033.cab
08/08/2014 11:28:30.643 SETUP (0xef8) 0x1964  Click-To-Run Telemetry amawv Medium MonitoredScope::ExecuteUnderStopWatch: TryGetClient::HandleStateAction: Getting Cab. Approximate duration: 499 milliseconds.
08/08/2014 11:28:30.643 SETUP (0xef8) 0x1964  Click-To-Run amaye Medium TryGetClient::HandleStateAction: Found C2R Client in extracted cab.
08/08/2014 11:28:30.643 SETUP (0xef8) 0x1964  Click-To-Run aoh9t Medium TryLaunchClient::HandleStateAction: Launching OfficeClickToRun.exe with parameters: scenario=unknown acceptalleulas="True" cdnbaseurl="http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675"
productreleaseid="none" culture="en-us" baseurl="http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675" lcid="1033" platform="x64" version="15.0.4631.1002" updatebaseurl="\\server\share\Office365"
updatesenabled="True" productstoadd="O365ProPlusRetail_en-us_x-none" trackedduration=499
08/08/2014 11:41:30.450 SETUP (0xef8) 0x1964  Click-To-Run apx75 Monitorable TryLaunchClient::HandleStateAction: C2R Client returned failing error code 17002
08/08/2014 11:41:30.450 SETUP (0xef8) 0x1964  Click-To-Run aoh72 Medium ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0
08/08/2014 11:41:30.450 SETUP (0xef8) 0x1964  Click-To-Run aoh9z Medium AdminBootstrapper::Main: Installation came back with 17002.
08/08/2014 11:41:30.450 SETUP (0xef8) 0x1964  Logging Liblet aqc99 Medium Logging liblet uninitializing.
Anyone have any ideas what is causing it?
I don't think it is permissions as I have seen on some forums because the share has read/execute permissions for domain users and domain computers

Hi,
Are you deploying Office 365 with the latest Office Deployment Tool? Try to download the latest version of ODT from below link, then try again:
http://www.microsoft.com/en-us/download/details.aspx?id=36778
A similar issue was resolved here, you might want to have a look:
http://social.technet.microsoft.com/Forums/en-US/eeb7b577-7868-487a-851d-a6d8c1c6bbda/office-c2r-installation-error-17002?forum=officeitpro
BTW, Microsoft Office 365 Community > Forums > Deploy Office 365
is a better source for this kind of problem and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
Thanks,
Ethan Hua CHN
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

No sim error on my iPad with SIM card installed

My iPad has a new SIM card in it but gives a no sim error message, help!

I hope I'm not jumping the gun, but after having the same "No Sim Card" problem after installing iOS7, trying the various "fixes" ... removing and replacing Sim Card, turning Airport Mode off and on, etc., without a permanent fix, just now I removed the Sim Card and cleaned the inside of the Sim Card slot on my iPad2.
To do this I took a thin flexible piece of plastic ... it's actually one of the removable collar stiffeners from a men's dress shirt, but a sized strip of cardboard would also work. I folded a cut-to-fit strip of paper towel ( I used heavy duty Bounty paper towel so it wouldn't fall apart ... a piece of clean cotton would work as well) over the plastic strip, soaked it with isopropyl alcohol, and carefully slid it back and forth in the slot a couple of times.
Then I reinserted the sim card and turned the iPad back on. At first I got the no card message again, but after simply turning Airport mode off and on, then wi-fi off and on, it started working again. This was a few hours ago. I've gone back to the iPad several times now and when I've turned it on, it continues to work properly. Only time will tell if this will work permanently, but since I've had the no card message non-stop for 2 weeks now, it's definitely encouraging.
It makes sense, because one of the fixes was to clean the Sim Card. Why wouldn't the Sim Card's receptacle be just as likely to get dirty or have a tiny bit of dust on it, stopping the connection? Wish me luck.

HP Compaq dc5750 SFF boot problem with USB devices installed.

HP Compaq dc5750 SFF
AMD Athlon (tm) 64 X2 Dual Core Processor 3800+
2.00 GHz 1.37 GB of RAM
XP Professional SP2 with latest updates.
HP Compaq Business System BIOS (786E3 BIOS)(ver. 2.36 Rev. A)
This is a problem when a Microsoft web camera is installed prior to the boot up of the computer
The webcam works fine if it is installed after the boot up.
When any type of USB product that does not have an OS is installed in any USB port the computer freezes at the BIOS POST screen and will not finish the POST unless the USB device is removed. If there is an OS on the USB device it boots normally to that device and it also boots normally to the installed OS if the USB device is not installed.
Contacted HP Support and was told to update the BIOS, which I had already done. Then I was told that the computer was out of warranty and I could pay for the service if I wanted help. I agreed to pay if the problem was fixed. This brought a reply that they did not know if the problem could be fixed.
The next day I received an email with Critical Alerts, one showing the BIOS update I had already installed and 2 other non critical updates.
Since HP did not show any interest in fixing this problem I am posting it here to see if anyone else has had this problem.

Hi,
Boot into the bios and change the boot priority order and save the setting change. Look under the Storage TAB drop down and then Boot Order. Highlight USB and press enter and then the down arrow to move it below the hard drive. Save the changes when you exit the bios.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

HP dv4-1225dx "Hard Disk Error" 3F1 on startup with eSATA HDD attached

The whole internet is void of information on this specific error code, so here it is, lo and behold, the ONLY English-language Google result for this error message:
Hard Disk Error
Please run the Hard Disk Test in System Diagnostics.
Error code:
Hard Disk 1 (3F1)
F2 System Diagnostics
For more information, please visit: (illegible due to colored text)
Specifically, the "Hard Disk 1 (3F1)" part, that's nowhere to be found online. Tons of pages about 3F0, apparently the primary hard disk. No, this is an error regarding the secondary hard disk, attached via eSATA.
Problem is, there's NOTHING wrong with the attached drive, other than this error on startup. No SMART failures. Comes up and works fine in Windows. Scanned 100% OK. It'd be nice if there were a way to bypass this error automatically, but I always have to hit F2, then Esc to abort its forced diagnostic routine.
It's a WD My Book Studio, 750gb, attached via eSATA. Doesn't happen if I leave it unplugged during startup... but SATA is a connection that likes to be present on startup. The system, as in the title, is a dv4-1225dx laptop, running Windows Home Server (Server 2003), but previously running Windows 7 Home Premium. Vista is evil.
It's also my home server, as of about yesterday (when I set it up and started getting this message). The system seems to crash pretty routinely over the past few days and every time it reboots, it hangs at that stupid "Hard Disk Error" message. Not a pretty sight when I'm away from home and want to access something, like my email. Is there a way around this message hanging the system?
edit: Not to mention the world's most buggy fan-control algorithm, worst heatpipe design on the planet, no AHCI mode control, and terrible system management (battery went dead on you at 40%? tough... remove battery to continue using your computer). LOOOOTS of bugs in this terrible BIOS.

Thanks for the link, it helps clarify that there's a difference between "3F1" and "301" - hard disk error and SMART error. In other words, it's reporting a generic "Error", not even that the drive may be/is failing.
In this case, the drive isn't failing, at all. It's a BIOS bug.
I put the drive on an ExpressCard eSATA controller, and it works fine. Unfortunately, since I'm the only one using this sort of configuration and getting this error, I imagine there won't be any work done to fix the bug

Boot Device Not Found, Please install an operating system on your hard disk, Hard Disk (3FO)

Hey
i am having this Error Message "Boot Device Not Found, Please install an operating system on your hard disk, Hard Disk (3FO)", While UEFI mode is enabled from bois but in Raid menu Both my hard Drives 1TB and SSD are Showing and I run the F2 System Diagnostics Test and it became as passed. In UEFI mode its not even showing my USB when i attach it for Window install But when i enabled the Leglacy mode it detteced my USB and also let me install my Windows and every thing seems to work fine. Updated the bios still Error is there.
Error Message only shows up when I disable the Leglacy mode.
So where is the Problem ? hard drive seems fine because these are working on Leglacy mode enabled.
Laptop Model : HP Envy Dv6-7211tx
Hard Drive : 1Tb and 32GB SSD

Hi Saifullay, sorry to hear that you are having issue with your Envy Dv6-7211tx. I have done some research and I have found a document that will assist you with this issues. Please click the link that I have provided to get to the document. http://h10010.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&dlc=en&docname=c01443463
If this does not resolve the issue, please feel free to write back . I would like to also apologize for the delay and the inconvenience that you have had to deal with.
Thank you.
Click the “Kudos Thumbs Up" at the bottom of this post to say “Thanks” for helping!
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
W a t e r b o y 71
I work on behalf of HP

Boot device not found - Please install an operating system on your hard disk

Trying to boot up this morning gave this error message:
"Boot device not found
Please install an operating system on your hard disk
Hard Disk <3F0>
F2 System Diagnostics"
Pressing F2 brings up to the "HP PC Hardware Diagnostics UEFI" page, where its shown:
"Version 1.6.0.0 - BIOS
Fore more info please visit www. ... ...
Memory Test
Hard Drive Check
Language
Exit"
Tryied the HD check but it says:
"SMART Check : Not installed
Short DST : Not installed
More details:
No bios upgrade was made, never, only a big updating of Windows yesterday.
Could someone kindely help me out please?
Thanks, Perry G.

Hi,
The above error message shows that the Hard disk drive is failed on your unit. You have to replace the Hard disk drive and reinstall the OS.
To order parts click the below link
https://h20141.www2.hp.com/Hpparts/Default.aspx?mscssid=FA59F7C7DCAC4237B498C91D0507A761
To order Recovery disk click below link
http://h10025.www1.hp.com/ewfrf/wc/document?docname=bph07143&cc=us&dlc=en&lc=en
"I work for HP."
Please click the "White Kudos" star to say thanks for helping.
Please mark "Accept As Solution" if my help has solved your problem.

IMac grey screen with external HDD attached

I used to have unibody Macbook with externall USB HDD (containing Time Machine and some free space) attached to it.
Today I have 2011 iMac but now if HDD is connected via USB, computer will stay at gray screen (after DVD drive noises).
If I disconnect the HDD, it succesfully boots. And ALT key Boot Menu with plugged HDD can be opened no problems too.
Formatted and partitioned HDD - no change.

1. Potential solution: Apple wants your forum feedback
Please see a post in the following thread and reply to it as you wish. Apple has now reportedly requested that we provide evidence in support of our desire to have the "open lid with screen off" option reinstated (eg significance of operating temperature differences, reduction in wifi reception, etc). They may then address our concerns with a Lion update.
https://discussions.apple.com/thread/3190417?start=60&tstart=0
2. The madness of magnets
This is getting very worrying. It's madness that Apple owners feel obliged to experiment with passing magnets over the top of their premium-priced computers and sticking them on here, there and everywhere in the hope of finding short-term workarounds. The sooner this problem is fixed at source (ie within Lion), the better.

Error in boot-uponly with win98 HDD installed

Similar Messages

Maybe you are looking for