Start up problem due to full hard disk

HI , hope to get help with my MAC book Pro 13 '' my hard disk is full and lukey me i did a back up for my files but unfortunetly after the back up i turned off my mac book then when i tried to start it up it turnsd on and stops after the apple appeares on a blue screen and not proceeding further more, and a msg appeares that the disk is full and no space to start up.
is there any sloution for this problem.
thanks

Try a Safe Boot OS X: What is Safe Boot, Safe Mode? - Apple Support if it starts that way you can unload some files to free up space. Music, pictures and video files are often moved off in cases like yours.

Similar Messages

HT201412 Have a problem with iPad2, apple logo appears but iPad won't boot up, then logo disappears & iPad dies - probably caused due to insufficient hard disk space (too many apps) - any help greatly appreciated

I have a problem with iPad2, apple logo appears but iPad won't boot up, then logo disappears & iPad dies - probably caused due to insufficient hard disk space (foolishly loaded up too many apps) - any help/advice greatly appreciated

What to Do When Your iPad Won't Turn On
http://ipad.about.com/od/iPad_Troubleshooting/ss/What-To-Do-When-Your-Ipad-Wo-No t-Turn-On.htm
iOS: Not responding or does not turn on
http://support.apple.com/kb/TS3281
iPad Frozen? How to Force Quit an App, Reset or Restart Your iPad
http://ipadacademy.com/2010/11/ipad-frozen-how-to-force-quit-an-app-reset-or-res tart-your-ipad
iPad: Basic troubleshooting
http://support.apple.com/kb/TS3274
Update and restore alert messages on iPhone, iPad, and iPod touch
http://www.buybuyla.com/tech/view/012953a0d412000e.shtml
iOS: Resolving update and restore alert messages
http://support.apple.com/kb/TS1275
iPad: Unable to update or restore
http://support.apple.com/kb/ht4097
 Cheers, Tom

HT1338 My mac Mini shows full hard disk when it is not really full. Shows some free space upon start up that gradually disappears without doing anything with the Mac.

My Mac shows a full hard disk even though the disk is not full. There are several GB of unused space if I add the sizes of all the folders in the disk. Under the disk info window the free space shrinks to zero after a short period of time. It shows more space upon restart, but then it shrinks eventually to zero space available. is there a way to solve this?

OmniDisksweeper can help you find what's hogging your disk space.

Full hard disk test Error

Hello.
my notebook has recently some startup problems, either during bios startup (led blinks twice) or while loading Windows. The problem seems to happen especially the first time I switch it on during the day, when I have to try 6-10 times before it starts correctly.
I have reinstalled the operating system and nothing changed. I have performed System diagnostic and I had an error on the Full Hard Disk Test:
9AM66W-53S7G3-XD0021-61EC03
all other tests have passed.
Thanks
This question was solved.
View Solution.

means the drive is failing and should be replaced....
I am a Volunteer to help others on here-not a HP employee.
Replies aren't online 24/7 because of Time Zone differences.
Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

Problem with a new hard disk

I have an old Imac 333, but unfortunately the original hard disk is died, so I munt a normal ide hard disk (segate 20G), but my mac don't see it, WhY? please help me!!

First, you have to make sure the drive is set to Master, not Cable Select or other setting. The "tray-loader" iMac actually has two IDE buses and the CDROM drive is on the other IDE bus. Some drives distinguish between settings for Master with no Slave present and Master with Slave. You want Master with no Slave present. These settings are made using the sets of pins on the drive, with little jumpers. There should be a label the drive with the settings. If not, the manufacturers web site should have it settings.
If that's been done, the second problem may be that the drive is not formatted, or it is formatted for Windows. I can't tell if you are using Mac OS X or Mac OS 9. If X, start up from the Mac OS X Installation Disk and run Disk Utility from the Installer menu. If Mac OS 9, start up from the Mac OS 9 Installation CD and run Drive Setup, with should be in the Utilities folder. In both cases, use the utility to format the drive for Mac OS Extended (HFS+).
Finally, these iMacs (233 MHz to 333 MHz) have a hardware limitation that requires the start up drive or volume fit within the first 8GB of drive space. So if the drive is 20GB, you must partition it so that the first partition is about 7.7GB and the second partition is the remaining space. This limitation exists only during the startup process. Once booted, you have full access to the second partition (up to a total of 128GB for all partitions).

Problem with USB External Hard Disk Drive

I have similar problem with hard disk MK6025GAS in Sweex casing connected via USB as Raistlfiren in this post but I am not sure if it has something to do with kernel. The problem is that when I plug the hard disk via USB it is not even shown with in /dev/ or by fdisk -l. I had similar problems with the drive before but it was always shown in /dev.
I got same output from dmesg as Raistlfiren in the post before
# dmesg | tail
sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
Info fld=0x0
I was browsing net for a lot of time to find a solution but nothing helped a lot. The problem is closes to the one described on Gentoo Forum
I can see that it is recognized by computer since it is shown with lsusb
# lsusb
Bus 001 Device 005: ID 13fd:0540 Initio Corporation
# lsusb -d 13fd:0540 -v
Bus 001 Device 005: ID 13fd:0540 Initio Corporation
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x13fd Initio Corporation
idProduct 0x0540
bcdDevice 0.00
iManufacturer 1 Initio
iProduct 2 MK6025GAS
iSerial 3 0010100500000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
From the beginning I though and I still think that the partition table is screwed up but the programs like TestDisk and fixdisktable work only with disks shown in /dev/
Additionally, I have checked the content of /var/log/kernel.log
Sep 16 22:03:58 hramat kernel: usb 1-2: new high speed USB device using ehci_hcd and address 5
Sep 16 22:03:58 hramat kernel: usb 1-2: configuration #1 chosen from 1 choice
Sep 16 22:03:58 hramat kernel: scsi4 : SCSI emulation for USB Mass Storage devices
Sep 16 22:03:58 hramat kernel: usb-storage: device found at 5
Sep 16 22:03:58 hramat kernel: usb-storage: waiting for device to settle before scanning
Sep 16 22:04:03 hramat kernel: scsi 4:0:0:0: Direct-Access Initio MK6025GAS 2.23 PQ: 0 ANSI: 0
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
Sep 16 22:04:03 hramat kernel: usb-storage: device scan complete
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] 117210240 512-byte hardware sectors: (60.0 GB/55.8 GiB)
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Write Protect is off
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Mode Sense: 86 0b 00 02
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:04:03 hramat kernel: sdd:<6>sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
Sep 16 22:04:03 hramat kernel: Info fld=0x0
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
and /var/log/errors.log
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
Sep 16 22:07:35 hramat kernel: INFO: task async/0:3957 blocked for more than 120 seconds.
Sep 16 22:07:35 hramat kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
The only thing I understand from these logs is that the disk is blocked, therefore not listed in /dev.
Assuming the newer kernel problems I could try to use some older live linux CD to see if that would work. I am also thinking of connecting this hard drive directly to my laptop, using live linux CD and maybe check the output of hdparm. Is there anything else I could check or try?
Thank you for any help or suggestions
Matej

Thank you nTia89 for response. Sorry for not providing enough information.
I believe the problem is not system dependent. I have dual boot with windows and there the disk has also problems. However, I do have Arch32 with Kernel 2.6.30, using Gnome. hal and dbus are also running.
I did not tried to connect the disk to the computer directly, I will try it today.
Yesterday I have used SystemRescueCD 0.4.1 with Kernel 2.6.22. I wanted to see if it will be recognized by the system and placed in /dev/. Yes it was. This means that the problem highlighted in Gentoo forum can be true, but it doesn't solve my problem. I have tried to connect the drive several times to Arch and it was not shown in /dev/sd*, in SystemRescueCD it was placed as /dev/sdb. Now I am sure that the partition table is screwed up.
So I have started to play with the drive in SystemRescueCD with TestDisk and FixDiskTable but without success.
% fdisk -l
Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1530 12289693+ 7 HPFS/NTFS
/dev/sda2 1531 6672 41303115 7 HPFS/NTFS
/dev/sda3 6673 12161 44090392+ f W95 Ext'd (LBA)
/dev/sda5 * 6673 11908 42058138+ 83 Linux
/dev/sda6 11909 12161 2032191 82 Linux swap / Solaris
Disk /dev/sdb: 60.0 GB, 60011642880 bytes
64 heads, 32 sectors/track, 57231 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk /dev/sdb doesn't contain a valid partition table
Manufacturer disk geometry: Heads: 16; Cylinders: 16383; Sectors: 63; Logical Blocks (LBA): 117210240
TestDisk found only Linux partitions with 43Gb while disk had only one 60Gb partitioned with FAT32/NTFS.
Also recognized 64 heads, 57231 cylinders and 32 sectors (same as from fdisk -l), which obviously differs from manufacturer disk geometry.
testdisk.log:
Thu Sep 17 19:09:26 2009
Command line: TestDisk
TestDisk 6.8, Data Recovery Utility, August 2007
Christophe GRENIER
Linux version (ext2fs lib: 1.40.2, ntfs lib: 9:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: none)
Using locale 'C'.
Hard disk list
Disk /dev/sda - 100 GB / 93 GiB - CHS 12161 255 63, sector size=512
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32, sector size=512
Disk /dev/sdb - 60 GB / 55 GiB
Partition table type: Intel
Interface Advanced
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : No
Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32
Current partition structure:
Partition sector doesn't have the endmark 0xAA55
Ask the user for vista mode
Computes LBA from CHS for Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Allow partial last cylinder : Yes
search_vista_part: 1
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Search for partition aborted
Results
interface_write()
No partition found or selected for recovery
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Search for partition aborted
Results
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Current partition structure:
Partition sector doesn't have the endmark 0xAA55
Ask the user for vista mode
Allow partial last cylinder : Yes
search_vista_part: 1
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Results
interface_write()
No partition found or selected for recovery
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
NTFS at 8956/63/32
heads/cylinder 255 (NTFS) != 64 (HD)
sect/track 63 (NTFS) != 32 (HD)
filesystem size 24579387
sectors_per_cluster 8
mft_lcn 1024141
mftmirr_lcn 1650676
clusters_per_mft_record -10
clusters_per_index_record 1
NTFS part_offset=9392094720, part_size=12584646144, sector_size=512
NTFS partition cannot be added (part_offset<part_size).
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34129 1 1 75201 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=69896224, size=84116272, end=154012495, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34632 2 1 75704 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=70926400, size=84116272, end=155042671, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34668 0 1 75740 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71000064, size=84116272, end=155116335, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34673 1 1 75745 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71010336, size=84116272, end=155126607, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34699 2 1 75771 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71063616, size=84116272, end=155179887, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 34708 2 1 75780 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=71082048, size=84116272, end=155198319, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36338 0 1 77410 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74420224, size=84116272, end=158536495, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36367 0 1 77439 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74479616, size=84116272, end=158595887, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36401 2 1 77473 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74549312, size=84116272, end=158665583, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 36414 2 1 77486 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=74575936, size=84116272, end=158692207, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 37949 1 1 79021 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=77719584, size=84116272, end=161835855, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 37955 1 1 79027 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=77731872, size=84116272, end=161848143, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 37989 1 1 79061 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=77801504, size=84116272, end=161917775, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 38404 0 1 79476 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=78651392, size=84116272, end=162767663, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 39636 2 1 80708 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=81174592, size=84116272, end=165290863, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 41263 1 1 82335 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=84506656, size=84116272, end=168622927, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 41266 1 1 82338 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=84512800, size=84116272, end=168629071, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 41660 0 1 82732 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=85319680, size=84116272, end=169435951, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 42898 0 1 83970 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=87855104, size=84116272, end=171971375, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 43244 1 1 84316 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=88563744, size=84116272, end=172680015, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 44870 2 1 85942 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=91893824, size=84116272, end=176010095, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 44930 2 1 86002 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=92016704, size=84116272, end=176132975, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 46961 0 1 88033 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=96176128, size=84116272, end=180292399, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 47312 0 1 88384 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=96894976, size=84116272, end=181011247, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 48393 2 1 89465 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=99108928, size=84116272, end=183225199, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 49633 2 1 90705 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=101648448, size=84116272, end=185764719, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 50767 1 1 91839 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=103970848, size=84116272, end=188087119, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 51150 1 1 92222 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=104755232, size=84116272, end=188871503, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 51941 1 1 93013 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=106375200, size=84116272, end=190491471, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 52759 0 1 93831 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=108050432, size=84116272, end=192166703, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 53069 1 1 94141 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=108685344, size=84116272, end=192801615, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 53768 0 1 94840 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=110116864, size=84116272, end=194233135, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54287 0 1 95359 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=111179776, size=84116272, end=195296047, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54493 2 1 95565 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=111601728, size=84116272, end=195717999, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54861 1 1 95933 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=112355360, size=84116272, end=196471631, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54890 2 1 95962 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=112414784, size=84116272, end=196531055, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 54953 2 1 96025 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=112543808, size=84116272, end=196660079, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 56330 1 1 97402 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=115363872, size=84116272, end=199480143, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 56334 0 1 97406 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=115372032, size=84116272, end=199488303, disk end=117211136)
recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
recover_EXT2: boot_sector=0, s_blocksize=4096
recover_EXT2: s_blocks_count 10514534
recover_EXT2: part_size 84116272
D Linux 57203 0 1 98275 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
This partition ends after the disk limits. (start=117151744, size=84116272, end=201268015, disk end=117211136)
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (60 GB / 55 GiB) seems too small! (< 103 GB / 95 GiB)
The following partitions can't be recovered:
D Linux 34129 1 1 75201 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34632 2 1 75704 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34668 0 1 75740 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34673 1 1 75745 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34699 2 1 75771 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 34708 2 1 75780 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36338 0 1 77410 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36367 0 1 77439 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36401 2 1 77473 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 36414 2 1 77486 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 37949 1 1 79021 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 37955 1 1 79027 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 37989 1 1 79061 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 38404 0 1 79476 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 39636 2 1 80708 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 41263 1 1 82335 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 41266 1 1 82338 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 41660 0 1 82732 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 42898 0 1 83970 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 43244 1 1 84316 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 44870 2 1 85942 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 44930 2 1 86002 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 46961 0 1 88033 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 47312 0 1 88384 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 48393 2 1 89465 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 49633 2 1 90705 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 50767 1 1 91839 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 51150 1 1 92222 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 51941 1 1 93013 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 52759 0 1 93831 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 53069 1 1 94141 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 53768 0 1 94840 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54287 0 1 95359 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54493 2 1 95565 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54861 1 1 95933 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54890 2 1 95962 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 54953 2 1 96025 27 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 56330 1 1 97402 26 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 56334 0 1 97406 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
D Linux 57203 0 1 98275 25 16 84116272
EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
Results
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
Interface Advanced
Disk /dev/sdb - 60 GB / 55 GiB
Partition table type: Intel
Disk /dev/sdb - 60 GB / 55 GiB
Partition table type: Intel
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : No
New options :
Dump : No
Cylinder boundary : Yes
Allow partial last cylinder : No
Expert mode : No
Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Current partition structure:
Partition sector doesn't have the endmark 0xAA55
Ask the user for vista mode
Allow partial last cylinder : No
search_vista_part: 0
search_part()
Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
Search for partition aborted
Results
Can't open backup.log file: No such file or directory
interface_load
interface_write()
No partition found or selected for recovery
simulate write!
write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
TestDisk exited normally.
fixdisktable first output:
% ./fixdisktable -d /dev/sdb
Getting hard disk geometry
cylinders=57231, heads=64, sectors=32
end_offset: 2147482624
FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
EXT2 partition at offset 56832, length=(41072.398 MB) 43067531264
Sectors: start= 111, end= 84116382, length= 84116272
Hd,Sec,Cyl: start(3,16,0) end(28,31,41072)
Done searching for partitions.
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 3 16 0 63 32 1023 111 84116273 83 (Interpretted)
1 80 3 16 0 63 224 255 111 84116273 83 (RAW)
1: 8003 1000 833f e0ff 6f00 0000 3183 0305
2: 0000 0000 0000 0000 0000 0000 0000 0000
3: 0000 0000 0000 0000 0000 0000 0000 0000
4: 0000 0000 0000 0000 0000 0000 0000 0000
Do you wish to write this partition table to disk (yes/no)? no
fixdisktable second output:
% ./fixdisktable -d -r -v /dev/sdb
Getting hard disk geometry
cylinders=57231, heads=64, sectors=32
end_offset: 2147482624
FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
NTFS partition at offset 17483776, length=(17592186043512.582 MB) 184467440727622 49216
Sectors: start= 34148, end=36028797017147916, length=36028797017113768
Hd,Sec,Cyl: start(43,5,16) end(16,12,2096265)
Done searching for partitions.
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 43 5 16 63 32 1023 34148 -1850199 07 (Interpretted)
1 80 43 5 16 63 224 255 34148 -1850199 07 (RAW)
1: 802b 0510 073f e0ff 6485 0000 a9c4 e3ff
2: 0000 0000 0000 0000 0000 0000 0000 0000
3: 0000 0000 0000 0000 0000 0000 0000 0000
4: 0000 0000 0000 0000 0000 0000 0000 0000
Do you wish to write this partition table to disk (yes/no)? no
This string "FfEeSsNnBbUu" was repeating there for longer time and it was most probably related to debugging or a verbose mode of fixdisktable
As I have mentioned I will try to connect the disk directly to the computer and see what will happen.
Shall I try to correct the disk geometry to the one specified by manufacturer? Is it possible?
Any suggestions?

Start-up problems due to firewire/usb devices?

Hi
recently, my imac G5 has been having some strange start-up problems. It had been working fine for the previous 11 months I have used the machine.
The start-up problems occur mainly after the computer has been shut down for some time (eg in the morning). When I press the start-up button, the computer will make the start up noise and then get stuck on the blue screen. Sometimes (but not always) the fan will start making a loud noise. Sometimes it is possible to turn the computer off and try to restart with the button at the back of the computer, at other times I have to turn the computer off at the power point and start again. I have tried to start up in "safe mode", but that also does not always work. This morning I was only able to start up the computer after unplugging all external devices, after which the imac started fine. I then replugged everything - no problem. However, I would like to be able to start-up without having to unplug and replug my various devices!
I am using several firewire devices (LaCie 250gb external hard-drive, Cd and DVD burner) and USB devices (scanner, printer, external USB drive (which I use for back-ups and which is mostly removed from the computer).
I have run disk utility to check the hard drives - they all appear to be ok.
I have a feeling the problems may have started when I tried out some back-up software to set up a regular back-up scheme. I have now removed all scheduling from my back-up software (silverkeeper, synk) but the problem remains.
Is it possible there is some problem with the drivers for the external devices? Any ideas?
Thanks a lot
Barbara
iMac G5 Mac OS X (10.3.9)

Hi Barbara,
Yes, USB devices particularly (including some hubs, most USB adsl modems, some printers and scanners and the like) can most certainly be the cause of this sort of problem (By far the most common cause, in fact)
First step is to simply remove them all, and see if the problem goes away. If so, then try adding them one at a time directly connected to the computer, testing them for a while, and see whether you can pin down which one it is.
Once you have tracked it down, if the device has its own drivers then look for any updates on the manufacturers web site, of course.
If the device doesn't have its own drivers then you can try simply disconnecting before shutting down and reconnecting after starting up, but the best solution is usually to replace the device.
(For what its worth, my bet, in the absence of more information about the actual devices attached, and as long as you don't have a USB adsl modem, is that its going to be a USB hub causing the problems )
Cheers
Rod

Problem of 1.5TB hard disk with msi p7n sli platinum

I have just bought a new 1.5TB hard disk (Western Digital). Bios can detect the disk but when i boot into Windows (XP sp3) its does not show?? can anyone tell me how to fix the problem. I have updated my mobo bios to 1.3 which is the latest available from the MSI site.
Thanks in advanced

Did you initialize the disk yet? Go to Control Panel, Administrative Tools, Computer Management, and then click on Disk Management. You should now see the disk listed there. Right-click the disk and initialize it. You can get to disk management directly by hitting the WindowsKey+R, type diskmgmt.msc, hit okay or enter, and the disk management box below will show.

I need to transfer all photos to an external hard drive. Many photos have been moved around or deleted from computer hard drive, but still have a very full hard disk. Are the photos with questionmarks in Lightroom still taking up hard disk space? I'm so l

Hi folks,
My hard disk is full. I already moved lots of photos from other folders on the hard disk to other external hard drives, so there are a lot of question marks in Lightroom. So, are those photos still taking up room on the computer hard disk? I want to move everything I have in Lightroom off of the computer to another external hard drive, in hopes that will free up space. I watched a tutorial, and read some things about it, but I need simple instructions please.

I cannot find this 300GB "Backup" in the Finder, only in the Storage info when I check "About This Mac".
You are probably using Time Machine to backup your MacBook Pro, right? Then the additional 300 GB could be local Time Machine snapshots. Time Machine will write the hourly backups to the free space on your hard disk, if the backup drive is temporarily not connected. You do not see these local backups in the Finder, and MacOS will delete them, when you make a regular backup to Time Machine, or when you need the space for other data.
See Pondini's page for more explanation: What are Local Snapshots? http://pondini.org/TM/FAQ.html
I have restarted my computer, but the information remains the same. How do I reclaim the use of the 300GB? Why is it showing up as "Backups" when it used to indicate "Photos"? Are my photos safe on the external drive?
You have tested the library on the external drive, and so your photos are save there.
The local TimeMachine snapshot probably now contains a backup of the moved library. Try, if connecting your Time Machine drive will reduce the size of your local Time Machine snapshots.

Operations Manager log flooded with 11903 errors due to "Virtual Hard Disk free disk space" monitor

Management Pack: Microsoft Windows Hyper-V 2012 R2 Monitoring (7.1.10104.0)
Monitor: Virtual Hard Disk free disk space
There appears to be an issue with this monitor. Every hour, each of my Hyper-V servers is reporting dozens of errors similar to the following. It seems like there is a disconnect between the expected return type (integer) and the actual type (decimal) when
checking the free space on VHDX files.
Log Name:      Operations Manager
Source:        Health Service Modules
Date:          2/5/2014 7:59:47 AM
Event ID:      11903
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      BEAST.corp.technologytoolbox.com
Description:
The Microsoft Operations Manager Expression Filter Module could not convert the received value to the requested type.
Property Expression: Property[@Name='Microsoft:9AC8FCAB-800D-424F-ABCB-747063E5FCF1\559D22F4-A565-4AD4-9B71-44FC5D815C0C\0\0\L.FreeSpace']
Property Value: 488033.99609375
Conversion Type: DataItemElementTypeInteger(5)
Original Error: 0x80FF005A
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.HyperV.2012.R2.VirtualDrive.FreeSpaceMonitor
Instance name: Hard Disk
Instance ID: {0C0E0759-D846-963C-21E6-3C1A1C096D5F}
Management group: HQ
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Health Service Modules" />
    <EventID Qualifiers="49152">11903</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-05T14:59:47.000000000Z" />
    <EventRecordID>32395</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>BEAST.corp.technologytoolbox.com</Computer>
    <Security />
</System>
<EventData>
    <Data>HQ</Data>
    <Data>Microsoft.Windows.HyperV.2012.R2.VirtualDrive.FreeSpaceMonitor</Data>
    <Data>Hard Disk</Data>
    <Data>{0C0E0759-D846-963C-21E6-3C1A1C096D5F}</Data>
    <Data>Property[@Name='Microsoft:9AC8FCAB-800D-424F-ABCB-747063E5FCF1\559D22F4-A565-4AD4-9B71-44FC5D815C0C\0\0\L.FreeSpace']</Data>
    <Data>488033.99609375</Data>
    <Data>DataItemElementTypeInteger(5)</Data>
    <Data>0x80FF005A</Data>
</EventData>
</Event>

SCOM agent is running as SYSTEM. (I used to run SCOM agents as a low-privilege domain account but eventually surrendered to "The Dark Side" due to the number of issues encountered with that approach.)
PS HKU:\.DEFAULT\Control Panel\International> dir
Hive: HKEY_USERS\.DEFAULT\Control Panel\International
Name Property
Geo Nation : 244
User Profile Languages : {en-US}
ShowAutoCorrection : 1
ShowTextPrediction : 1
ShowCasing : 1
ShowShiftLock : 1
User Profile System Backup Languages : {en-US}
ShowAutoCorrection : 1
ShowTextPrediction : 1
ShowCasing : 1
ShowShiftLock : 1

Problem with Startup; Macintosh Hard Disk (internal) won't mount

Hi. I hope you can help me.
I was getting ready to install Leopard on my computer but was stupid enough not to make a backup first. During the installation process, Leopard warned me that for it to upgrade to Leopard from Tiger, it will have to completely erase my hard disk and reformat it. I don't know why that is. Perhaps because at that time, I only had 6GB left in my drive. So, I cancelled out of the installation process. Something happened however and now my PowerPC G5 won't restart. It completely blanks out and shuts down in the middle of the restart. So I restarted using my Tiger install DVD. I then started Disk Utility. From there, I can see that while it can see my Macintosh hard disk, it is greyed out and shown as not mounted. I clicked on the Mount button, but that didn't work. I repaired disk, and that encountered errors and didn't go all the way through. I realize my only option might be to competely erase the drive and install Leopard or Tiger again. Before doing that though, I'd really like to rescue some of the files in the hard disk. What can I do? I have the use of a macbook and an iomega external drive at my discretion.
Thanks so much!

Diskwarrior has been known to find disks. Or try Techtool Pro.

Can't boot into bios due to SMART Hard Disk Error

My hard drive failed and now im getting constant pop ups to replace it
I'm thinking about transfering windows to an external drive until I can replace the internal one but I need access to the bios to set the boot priorty options anytime I use f10 to boot into the bios it's like it's skipped over and gives me the smart hard disk error screen where my only options are to boot into windows or run diagnostics.
I tried running diagnostics but each test resulted in an instant failure.

Yes take out hard drive and connect it to another PC. Get help from your service manual for procedure for taking it out:
http://h10032.www1.hp.com/ctg/Manual/c02659236
Adapter, something like this: http://www.amazon.com/Anker®-Converter-Adapter-Cable-included/dp/B005B3VO24
For configuring boot order, try this:
http://support.hp.com/in-en/document/c00364979
Tap f9 key soon after powering on notebook, if the above don't work.
Regards
Visruth
++Please click KUDOS / White thumb to say thanks
++Please click ACCEPT AS SOLUTION to help others, find this solution faster
**I'm a Volunteer, I do not work for HP**

Start up problem due to insufficient disk space

can not start my macbook pro due to above error, how can I reboot and resolve the problem

If you are lucky Ogelthorpe's Safe Boot suggestion will allow you to get to the desktop - this works because during the Safe Boot process cache and log files are deleted/trimmed. Assuming you do get to the desktop, unless something was really awry with your system, your drive is still over full, its just that you now have the chance to remove some files to free up space. (1) if you use iPhoto launch it and delete iPhoto's trash can. This was something I hadn't thought of until one of the Level 6 or Level 7 folk mentioned it a while ago. Doing it freed up a significant amount of space on my MBA. (2) if you have a lot of music, videos, and digital photos those are good candidates for removing from your internal hard drive. Deleting one movie or a few CDs will probably free up more space than deleting all your documents and a couple programs.
I purchased a low profile SD card for my MBA and moved all my media to it which freed up a tremendous amount of space.

Sometimes cannot start PC: problem with Hitachi SATA Hard drive and K7N2G-ILSR

I have major problem with my 160Gb SATA Hitachi hard drive and my MSI K7N2G-ILSR motherboard. Sometimes the PC can be started, sometimes it cannot.
After I installed a clean build of Windows XP Pro SP1 onto my new hard drive (as the only hard drive in my PC) and install all the necessary drivers, the system runs smoothly. However, after about 2 to 3 weeks, sometimes when I start the PC, it cannot detect the hard drive and hence it claimes that it cannot find any VMI Pool Data (i.e. no OS detected). What makes it really horrible is that, it is like the lottery everytime when I start the PC. Sometimes it works, sometimes it doesn't. The highest record was 8 consecutive failures (by resetting or by turning the power off and on again) before I can start the machine properly. Also, the system sometimes just crashes in the middle of operating.
I have already sent the hard drive back to Hitachi. Got the same model of hard drive back as replacement, but the replacement has the same problem, except with the replacement drive the PC can be started eventually after many tries, while with the previous drive it is possible that the PC cannot be started until after a few days later.
Also, it seems that my drive can detect either SATA hard drive or PATA hard drive, but not both. (If I leave my old PATA drive connect in the primary IDE channel, Windows cannot detect the new SATA drive.)
Is my motherboard faulty? Can it only use PATA drive?
My PC's spec is as follows:
AMD Athlon XP 2500+
512Mb PC3200 SDRAM (set to run at 166MHz)
Hitachi 160Gb SATA Hard drive on 1st SATA channel (Model #HDS722516VLSA80)
Sony DVD+-RW drive and Panasonic DVD-ROM drive on secondary IDE channel
Use onboard video (GeForce MX)
US Robotech V92 internal PCI modem
SoundBlaster Audigy 2 Player soundcard
Onboard audio disabled
300W PSU
OS is Windows XP Pro SP1 (with all latest security patches up to date)

Quote
Originally posted by Raven_
Quote
Originally posted by boucher91
Along the same lines the sata drives use more power than the pata drives...
sata usually faster spin rate, pata is slower spin rate...
that is not entirly correct.
many harddrives just come with different ways to connect them.
the only sata drives i now that spins faster is western digital raptors 10k rpm.
all other is running at 7200rpm.
older drives run at 5400rpm
Yes to get the full benefit of RAID, the Raptors are the way to go.Anything else, no significant difference.

Start Up Problems with too full Mac Air

I cant restart my Mac Air after the batterie whent flat after i got message about Start Up Memory Too Full. What do i do now.

You may be able to boot in safe mode by holding down the shift key at the startup chime.
Empty the Trash if you haven't already done so.
According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation. You also need enough space left over to allow for growth of your data. There is little or no performance advantage to having more available space than the minimum Apple recommends. Available storage space that you'll never use is wasted space.
To locate large files, you can use Spotlight as described here. That method may not find large folders that contain a lot of small files.
You can also use a tool such as OmniDiskSweeper (ODS) to explore your volume and find out what's taking up the space. You can delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one.
Proceed further only if the problem hasn't been solved.
ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
Install ODS in the Applications folder as usual.
Triple-click the line of text below to select it, then copy the selected text to the Clipboard (command-C):sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means.
When you're done with ODS, quit it and also quit Terminal.

Start up problem due to full hard disk

Similar Messages

Maybe you are looking for