File system IS journaled extended

New iMac. And the file system is Mac Journaled extended, but getting the famous "wrong file system" error message when loading up iPhoto for the first time. It is the default settings, so iPhoto Library resides on my harddrive.
Any reason why I'm getting this error message and unable to use this product?

That means your original library is corrupt.
Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
Regards
TD

Similar Messages

[Solved] Favorite File System

I'm looking for file system suggestions for a data server which I'm reworking right now due to failures from my first selection.
I used Ext3 which worked for a year+ and has now degraded to the point of being unusable. I'm wondering if any one has experience with linux based data servers and could suggest a file system with journaling and tools that can be used as is.
With Ext3 you have to drop the file system back to Ext2 to work on it...or at least that is what I have read and treated as such.
Any ideas? Experience based suggestions?
(software raid will be used)
Last edited by jduped (2009-06-19 06:46:06)

Thanks for the input guys...I've never used jfs but looks like a good idea
I was reading about it in the beginners guide. and the wiki page on here.
Tryiel interesting way of laying out your partitions with all those mounts are you using lvm? or a few separate drives?
To further on my issue.
The drives are accessible, but read times are unacceptable and with media files they often freeze and lock. The info I found said to degrade ext3 to ext2 then run some of the tools on it. I got an external drive 1TB that I'm dumping all the drives off with then I'm going to rebuild with fresh formats and os. I just didn't want to run into this again.
I think in the long run ext4 has some promise.
Thanks again

Format Error : mkfs.ocfs2 1.2.7 file system too small for a journal

Hi All,
I am trying to implement Oracle 10g RAC on my laptop using vmware and openfiler software . But while executing the command
#mkfs.ocfs2 -b 4K -C 32K -N 4 -L oracrsfiles /dev/iscsi/crs11/part1
I am getting the error
Format Error : mkfs.ocfs2 1.2.7 file system too small for a journal
Please anybody can help me to resolve this problem.
Thanks in Advance.

How large is the device that you are formatting?
The default journal size depends on the type specified. If none specified,
then it assumes "mail" which sets the default journal per slot to 256M.
If database type, default is 64M.
Use "-T database" to specify database type, etc.
BTW, one can always override the defaults. Say "-J size=16M" to make
a smaller journal.
man mkfs.ocfs2 and the user's guide has more.

Extending RAID file system with larger disk

Hi,
I have a Mac pro running 10.7.5.
I used to have two 1TB disks in the internal bays configured as a raid 1 set with a single 1TB file system. One of the disks failed and I replaced it with a 2TB disk which seems to be working ok. However, I'm running out of space in the file system and thought to switch to 2TB.
I just got another 2TB disk and thought to replace the 1TB disk with this one. Then I would have two 2TB disks but I guess after the rebuild the file system is still 1TB. Is there any way to extend the file system and underlying raid set on the go or do I need to disband the raid set to two independent disks first, then repartition one of them, copy data from the remaining half to this now 2TB file system and add the source disk to the raid set afterwards?
Hannu

I too have a 1,1 and continue to "do things" and upgrade it.
Sonnet Tempo Pro SSD PCIe is perfect for Aperture having it on another bus controller with SATA III 6G and 550MB/sec.
$400 was never too much to spend for SCSI or for my first couple 160MB disk drive for perspective.
Mavericks (cannot run normally on ours) was suppose to offer more advantages in RAID features but even that seems to be MIA.
PS: A Sonnet Allegro USB3 PCIe $54 is a nice way to interface instead of using USB2.
I have used mirror but AFTER having a couple good backups and strategy.
So just buy a new set of 2TB or larger drives.
We have had people with iTunes library alone that needed their own 2TB volume when the largest drives were 1TB.
Done right a stripe RAID is fine, and one way I always used to have larger volumes.
"Extended volume support" is more a Windows thing, not a Mac feature.
As you found, Apple mirror RAIDs cannot 'grow' and you can't add a 2TB and suddenly have larger mirror w/o delete and create a new set.
You may be lucky that you never had a disaster. A 3-way mirror is really preferable, take one of the drives out while rebuild and you still have two in a mirror set. AND clone your volume or use something besides or in addition to TimeMachine.
A backup is only as good as your ability to restore and have a recovery plan - hopefully one that you have practiced doing but never need to.

Journaled file system for startup volume only?

I have been told that the advantage of a journaled file system is only realized on the startup volume. Surely, protecting the critical startup files is first priority for most users, but does the advantage of a journaled file system apply to other drive volumes, too? Please explain why this is or is not true. Thanks.

Moof666 wrote:
I have been told that the advantage of a journaled file system is only realized on the startup volume. Surely, protecting the critical startup files is first priority for most users, but does the advantage of a journaled file system apply to other drive volumes, too? Please explain why this is or is not true. Thanks.
it applies to all drives but it's much less relevant for non startup drives. startup drives are being written to constantly and other drives are not. the likelihood of an external drive being written to at the moment of say a power outage is much smaller than that for the startup drive. therefore having journaling on on nonstartup drives is not as crucial. you can still do it though if you want to.
Message was edited by: V.K.

Solaris 7/8 - journaled file systems?

Do I need to do anything to enable this feature? I don't see any references to file system journaling on any man pages. Can I convert ufs file systems?, etc, etc ...

Yes, you have to mount the filesystems with option 'logging', see the
mount_ufs(1M) man page. Using the 'remount' option in combination
with 'logging' or 'nologging' you can turn it on/off on a mounted
filesystem. To enable it across a reboot, add the 'logging' option
into the last (= mount options) column for the relevant line in
/etc/vfstab.

HELP!!! i formated a external hdd to MAC os Extended file system

HELP!!! i formated a external hdd to MAC os Extended file system in disk utility and now i need it formated back to work on pc. i have tried ms-dos file system under the erase tab and it doesnt work, on my pc all it has under my computer is black, but if you go down by the time you can "safely remove hardware" but it dosent give a drive location (ex: e:/)....
the external hdd is a seagate go 250gb usb

Use the PC to reformat the drive.

How to extend the file system?

hello experts,
how to check wether file system is full?and how to extend the file system?

Hi,
You can check whether your file system occupancy using Unix level command df -k.
how to extend the file system?
Whats the OS platform you working upon and need to extend the file system. Based on individual OS platform commands may vary.
Regards,
Deepak Kori

Print dialog options in case sensitive file system

Since changing the file system running Lion and Mountain Lion from Mac OS Extended (Journaled) to Mac OS Extended (Case-sensitive, Journaled), certain features in print dialogs have disappeared.
Particularly the option to print notes with slides in Microsoft Powerpoint are gone. Also, when choosing to print only 1 (or more, but not all) of multiple pages in Microsoft Word, the printer will nevertheless print all pages.
This problem occurs on printers of different brands, i.e. HP, Lexmark, Brother.
I was able to determine this problem by reproducing the issue on a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Case-sensitive, Journaled) vs a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Journaled), not Case-sensitive.
Has anyone else had the same problem and maybe a solution?

I just fixed this on my Mac. It is a bug in Microsoft Office... the Printer Dialog Extension (PDE) for Powerpoint is located in a directory named "Plugins", but PowerPoint is looking for it in "PlugIns". This obviously does not work in a case-sensitive filesystem.
Here are the steps to fix the issue:
http://apple.stackexchange.com/a/119974/69562

IPhoto9: "library could not be opened because the file system of the library's volume is unsupported."

Can please anyone help me with this issue.
After upgrading from iPhoto8 to iPhoto9 my library won't open anymore. I have stored all my pictures on a NAS (Buffalo Link Station Duo). It all worked fine but since upgrading to iPhoto9 I do have the following problem:
When opening iPhoto I receive a message that the library needs to be updated. I assume that iPhoto should just do this sort of automatically in order to upgrade to iPhoto9.However, next message I receive then is
"The library could not be opened because the file system of the library's volume is unsupported."
Apple support so far does not seem to be able to solve my issue. Anyone else having had the same issue and having a solution to this?
Thanks a lot for your help.

There is no solution.
IPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos.While you have been lucky to date, many folks with a library on a NAS found that it worked for a while and then the problems started.
Workaround: Put the Library on a Disk Image formatted Mac OS Extended (Journaled) and store that on the NAS. But the real solution is to use a properly formatted disk for the Library.
Regards
TD

Among the available file systems for formatting that can be found in Disc Utility, which gives the best transfer performance?

I have a HDD under MS-DOS, which claims transfer speeds above and beyond of 480MB/s, but the actual speeds I have been getting are closer to 300kB/s. Is there a way to improve this merely by reformatting volume to another file system?

If you don't need to use it with PCs, copy any data you want to keep off and reformat it as Mac OS Extended (Journaled). Also, since it seems to be connected through USB 2.0, unplug all unnecessary devices when transferring data to improve performance.
(62387)

Every boot requires fsck. Makes file system read-only

Suddenly when I booted my Arch I got a message saying that there was a corruption in my /home and /var directories. The same message suggested to pass fsck as solution. The booting process hanged there without entering to the emergency login. I took a live cd an executed a fsck in all my ext4 file system and “repaired” the problem.
When I could log into the system if, for example, I want to write a file o do any operation (sudo for example) I get the message:
sudo: unable to open /var/db/sudo/lola/0: Read-only file system
If I reboot the PC again, the cycle begins again, this is: errors, asking for fsck, then, read-only FS.
Some info that you may find useful:
fstab
/dev/sda3 / ext4 defaults 0 1
/dev/sda5 /var ext4 defaults 0 1
/dev/sda6 swap swap defaults 0 0
/dev/sda7 /home ext4 defaults,user_xattr 0 1
df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 15G 7.2G 6.6G 52% /
dev 1.9G 0 1.9G 0% /dev
run 1.9G 740K 1.9G 1% /run
/dev/sda3 15G 7.2G 6.6G 52% /
tmpfs 1.9G 536K 1.9G 1% /dev/shm
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
tmpfs 1.9G 80K 1.9G 1% /tmp
/dev/sda7 80G 39G 37G 52% /home
/dev/sda5 6.8G 3.7G 2.8G 58% /var
/dev/sda2 358G 334G 25G 94% /media/windows
systemctl
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys-fs-binfmt_misc.automount loaded active running Arbitrary Executable File Formats File System Au
sys-devices-pci...000:00:1b.0-sound-card0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1b.0/sound/card0
sys-devices-pci...0-0000:02:00.0-net-eth0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.
sys-devices-pci...-0000:03:00.0-net-wlan0.device loaded active plugged /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.
sys-devices-pci...-1:0:0:0-block-sda-sda1.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda2.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda3.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda4.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda5.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda6.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda7.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...1:0:0-1:0:0:0-block-sda.device loaded active plugged TOSHIBA_MK5055GSX
sys-devices-pci...5:0:0-5:0:0:0-block-sr0.device loaded active plugged TSSTcorp_CDDVDW_TS-L633C
sys-devices-platform-serial8250-tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devices-platform-serial8250-tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
tail -100 /var/log/errors.log
Jan 23 14:43:52 localhost kernel: [ 283.449542] ata2.00: error: { UNC }
Jan 23 14:43:52 localhost kernel: [ 283.451224] end_request: I/O error, dev sda, sector 513442820
Jan 23 14:43:52 localhost kernel: [ 283.451228] Buffer I/O error on device sda2, logical block 63796096
Jan 23 14:43:56 localhost kernel: [ 287.394421] ata2.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x0
Jan 23 14:43:56 localhost kernel: [ 287.394426] ata2.00: irq_stat 0x40000001
Jan 23 14:43:56 localhost kernel: [ 287.394430] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [ 287.394435] ata2.00: cmd 60/08:00:00:84:9a/00:00:1e:00:00/40 tag 0 ncq 4096 in
Jan 23 14:43:56 localhost kernel: [ 287.394435] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 14:43:56 localhost kernel: [ 287.394438] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [ 287.394440] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [ 287.394442] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [ 287.394447] ata2.00: cmd 60/00:08:1f:53:4d/01:00:2d:00:00/40 tag 1 ncq 131072 in
Jan 23 14:43:56 localhost kernel: [ 287.394447] res 41/40:02:04:84:9a/00:00:1e:00:00/4e Emask 0x9 (media error)
Jan 23 14:43:56 localhost kernel: [ 287.394449] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [ 287.394451] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [ 287.394453] ata2.00: failed command: WRITE FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [ 287.394458] ata2.00: cmd 61/08:10:7f:6e:b7/00:00:30:00:00/40 tag 2 ncq 4096 out
Jan 23 14:43:56 localhost kernel: [ 287.394458] res 41/40:02:04:84:9a/00:00:1e:00:00/4e Emask 0x9 (media error)
Jan 23 14:43:56 localhost kernel: [ 287.394460] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [ 287.394462] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [ 287.394464] ata2.00: failed command: WRITE FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [ 287.394468] ata2.00: cmd 61/90:18:37:42:31/00:00:35:00:00/40 tag 3 ncq 73728 out
Jan 23 14:43:56 localhost kernel: [ 287.394468] res 41/40:02:04:84:9a/00:00:1e:00:00/4e Emask 0x9 (media error)
Jan 23 14:43:56 localhost kernel: [ 287.394471] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [ 287.394472] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [ 287.396122] end_request: I/O error, dev sda, sector 513442820
Jan 23 14:43:56 localhost kernel: [ 287.396125] Buffer I/O error on device sda2, logical block 63796096
Jan 23 14:43:56 localhost kernel: [ 287.396179] end_request: I/O error, dev sda, sector 760042271
Jan 23 14:43:56 localhost kernel: [ 287.396232] end_request: I/O error, dev sda, sector 817327743
Jan 23 14:43:56 localhost kernel: [ 287.396235] Buffer I/O error on device sda7, logical block 1133175
Jan 23 14:43:56 localhost kernel: [ 287.396282] end_request: I/O error, dev sda, sector 892420663
Jan 23 14:44:01 localhost kernel: [ 291.317005] ata2.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
Jan 23 14:44:01 localhost kernel: [ 291.317010] ata2.00: irq_stat 0x40000008
Jan 23 14:44:01 localhost kernel: [ 291.317014] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 14:44:01 localhost kernel: [ 291.317019] ata2.00: cmd 60/08:08:00:84:9a/00:00:1e:00:00/40 tag 1 ncq 4096 in
Jan 23 14:44:01 localhost kernel: [ 291.317019] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 14:44:01 localhost kernel: [ 291.317022] ata2.00: status: { DRDY ERR }
Jan 23 14:44:01 localhost kernel: [ 291.317024] ata2.00: error: { UNC }
Jan 23 14:44:01 localhost kernel: [ 291.318643] end_request: I/O error, dev sda, sector 513442820
Jan 23 14:44:01 localhost kernel: [ 291.318647] Buffer I/O error on device sda2, logical block 63796096
Jan 23 14:44:01 localhost kernel: [ 291.546162] Aborting journal on device sda7-8.
Jan 23 14:54:20 localhost [ 7.837917] systemd[1]: Socket service syslog.service not loaded, refusing.
Jan 23 14:54:20 localhost [ 7.838515] systemd[1]: Failed to listen on Syslog Socket.
Jan 23 14:54:21 localhost kernel: [ 10.930157] [drm:intel_panel_setup_backlight] *ERROR* Failed to get maximum backlight value
Jan 23 14:54:34 localhost dhcpcd[564]: dhcpcd not running
Jan 23 14:54:35 localhost dhcpcd[649]: dhcpcd not running
Jan 23 14:54:35 localhost dhcpcd[662]: dhcpcd not running
Jan 23 14:58:04 localhost su: pam_unix(su:auth): conversation failed
Jan 23 17:00:38 localhost systemd[1]: Failed to start Netcfg multi-profile daemon.
Jan 23 17:00:39 localhost [ 7.790297] systemd[1]: Socket service syslog.service not loaded, refusing.
Jan 23 17:00:39 localhost [ 7.790891] systemd[1]: Failed to listen on Syslog Socket.
Jan 23 17:00:39 localhost kernel: [ 11.363432] [drm:intel_panel_setup_backlight] *ERROR* Failed to get maximum backlight value
Jan 23 17:00:55 localhost dhcpcd[612]: dhcpcd not running
Jan 23 17:00:55 localhost dhcpcd[618]: dhcpcd not running
Jan 23 17:00:55 localhost dhcpcd[626]: dhcpcd not running
Jan 23 17:01:23 localhost su: pam_unix(su:auth): conversation failed
Jan 23 17:04:55 localhost kernel: [ 274.346016] ata2.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x0
Jan 23 17:04:55 localhost kernel: [ 274.346022] ata2.00: irq_stat 0x40000008
Jan 23 17:04:55 localhost kernel: [ 274.346025] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:04:55 localhost kernel: [ 274.346031] ata2.00: cmd 60/70:08:e8:83:9a/00:00:1e:00:00/40 tag 1 ncq 57344 in
Jan 23 17:04:55 localhost kernel: [ 274.346031] res 41/40:70:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:04:55 localhost kernel: [ 274.346034] ata2.00: status: { DRDY ERR }
Jan 23 17:04:55 localhost kernel: [ 274.346035] ata2.00: error: { UNC }
Jan 23 17:04:55 localhost kernel: [ 274.348151] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:04:55 localhost kernel: [ 274.348154] Buffer I/O error on device sda2, logical block 63796096
Jan 23 17:04:55 localhost kernel: [ 274.348159] Buffer I/O error on device sda2, logical block 63796097
Jan 23 17:04:55 localhost kernel: [ 274.348162] Buffer I/O error on device sda2, logical block 63796098
Jan 23 17:04:55 localhost kernel: [ 274.348164] Buffer I/O error on device sda2, logical block 63796099
Jan 23 17:04:55 localhost kernel: [ 274.348166] Buffer I/O error on device sda2, logical block 63796100
Jan 23 17:04:55 localhost kernel: [ 274.348168] Buffer I/O error on device sda2, logical block 63796101
Jan 23 17:04:55 localhost kernel: [ 274.348171] Buffer I/O error on device sda2, logical block 63796102
Jan 23 17:04:55 localhost kernel: [ 274.348173] Buffer I/O error on device sda2, logical block 63796103
Jan 23 17:04:55 localhost kernel: [ 274.348176] Buffer I/O error on device sda2, logical block 63796104
Jan 23 17:04:55 localhost kernel: [ 274.348178] Buffer I/O error on device sda2, logical block 63796105
Jan 23 17:04:59 localhost kernel: [ 278.257533] ata2.00: exception Emask 0x0 SAct 0x84 SErr 0x0 action 0x0
Jan 23 17:04:59 localhost kernel: [ 278.257539] ata2.00: irq_stat 0x40000008
Jan 23 17:04:59 localhost kernel: [ 278.257543] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:04:59 localhost kernel: [ 278.257549] ata2.00: cmd 60/08:38:00:84:9a/00:00:1e:00:00/40 tag 7 ncq 4096 in
Jan 23 17:04:59 localhost kernel: [ 278.257549] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:04:59 localhost kernel: [ 278.257551] ata2.00: status: { DRDY ERR }
Jan 23 17:04:59 localhost kernel: [ 278.257553] ata2.00: error: { UNC }
Jan 23 17:04:59 localhost kernel: [ 278.259233] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:05:03 localhost kernel: [ 282.157929] ata2.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
Jan 23 17:05:03 localhost kernel: [ 282.157934] ata2.00: irq_stat 0x40000008
Jan 23 17:05:03 localhost kernel: [ 282.157938] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:05:03 localhost kernel: [ 282.157943] ata2.00: cmd 60/08:10:00:84:9a/00:00:1e:00:00/40 tag 2 ncq 4096 in
Jan 23 17:05:03 localhost kernel: [ 282.157943] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:05:03 localhost kernel: [ 282.157946] ata2.00: status: { DRDY ERR }
Jan 23 17:05:03 localhost kernel: [ 282.157947] ata2.00: error: { UNC }
Jan 23 17:05:03 localhost kernel: [ 282.159582] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:05:03 localhost kernel: [ 282.159588] Buffer I/O error on device sda2, logical block 63796096
Jan 23 17:05:07 localhost kernel: [ 286.069482] ata2.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
Jan 23 17:05:07 localhost kernel: [ 286.069487] ata2.00: irq_stat 0x40000008
Jan 23 17:05:07 localhost kernel: [ 286.069491] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:05:07 localhost kernel: [ 286.069496] ata2.00: cmd 60/08:30:00:84:9a/00:00:1e:00:00/40 tag 6 ncq 4096 in
Jan 23 17:05:07 localhost kernel: [ 286.069496] res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:05:07 localhost kernel: [ 286.069499] ata2.00: status: { DRDY ERR }
Jan 23 17:05:07 localhost kernel: [ 286.069501] ata2.00: error: { UNC }
Jan 23 17:05:07 localhost kernel: [ 286.071955] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:05:07 localhost kernel: [ 286.071959] Buffer I/O error on device sda2, logical block 63796096
Waiting for your help.
Thank you.

oh god, if my HD dies I will kill myself.
I did the SMART, short and long (following the ArchWiki) and got (will post the long as soon it ends):
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 7967 -
With more details:
smartctl -a /dev/sda
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.6.9-1-ARCH] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MK..55GSX
Device Model: TOSHIBA MK5055GSX
Serial Number: 897JC07RT
LU WWN Device Id: 5 000039 1f3c01f05
Firmware Version: FG001M
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Wed Jan 23 13:46:24 2013 PYST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 249) Self-test routine in progress...
90% of test remaining.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 183) minutes.
SCT capabilities: (0x0039) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1320
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1807
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 7
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 7967
10 Spin_Retry_Count 0x0033 136 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1789
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 97
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 33
193 Load_Cycle_Count 0x0032 082 082 000 Old_age Always - 189405
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 39 (Min/Max 9/50)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 1
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 9
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 87
222 Loaded_Hours 0x0032 085 085 000 Old_age Always - 6001
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 320
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 634 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 634 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 04 84 9a 6e Error: UNC at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 00 84 9a 40 08 03:31:25.735 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 03:31:25.714 FLUSH CACHE EXT
61 18 08 07 82 b1 40 08 03:31:25.714 WRITE FPDMA QUEUED
61 08 00 0f 7d 31 40 08 03:31:25.714 WRITE FPDMA QUEUED
ea 00 00 00 00 00 a0 00 03:31:25.682 FLUSH CACHE EXT
Error 633 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 04 84 9a 6e Error: UNC at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 00 84 9a 40 08 03:31:21.832 READ FPDMA QUEUED
61 18 00 27 81 b1 40 08 03:31:21.451 WRITE FPDMA QUEUED
61 18 00 27 77 b1 40 08 03:31:20.425 WRITE FPDMA QUEUED
61 18 00 2f 8c b1 40 08 03:31:19.451 WRITE FPDMA QUEUED
61 18 00 ef 81 b1 40 08 03:31:18.445 WRITE FPDMA QUEUED
Error 632 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 0a 04 84 9a 6e Error: UNC at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 07 7f 09 40 08 03:16:43.581 READ FPDMA QUEUED
60 08 08 00 84 9a 40 08 03:16:43.559 READ FPDMA QUEUED
60 00 00 a7 5b 09 40 08 03:16:43.552 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 03:16:43.551 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 03:16:43.551 READ NATIVE MAX ADDRESS EXT
Error 631 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 0a 04 84 9a 6e Error: UNC at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 a7 5b 09 40 08 03:16:39.713 READ FPDMA QUEUED
60 08 00 87 b5 25 40 08 03:16:39.705 READ FPDMA QUEUED
60 00 00 8f 60 05 40 08 03:16:39.693 READ FPDMA QUEUED
60 08 00 e7 d4 54 40 08 03:16:39.692 READ FPDMA QUEUED
60 08 08 00 84 9a 40 08 03:16:39.678 READ FPDMA QUEUED
Error 630 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 12 04 84 9a 6e Error: WP at LBA = 0x0e9a8404 = 245007364
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
61 08 08 0e 4c b6 40 08 03:16:35.710 WRITE FPDMA QUEUED
61 08 08 0e 4c b6 40 08 03:16:35.710 WRITE FPDMA QUEUED
61 08 08 0e 4c b6 40 08 03:16:35.709 WRITE FPDMA QUEUED
61 98 18 8f 41 31 40 08 03:16:35.709 WRITE FPDMA QUEUED
61 08 08 0e 4c b6 40 08 03:16:35.708 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 7967 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Is there an equivalent to Solaris iostat -En in Linux? Havent found any. Remember that I can't install anything: read-only FS
Last edited by gromlok (2013-01-23 16:47:35)

Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.a

So I am new to the forum and would like some helpful (non-snobbery) advice regarding my iMac. I am currently working on an iMac G5 - 1.8 GHz PowerPD G5, equipped with 1.5 GB DDR SDRAM. I've just cleaned up the hard disk and installed Leopard. Here is my dilemma:
The machine has been performing VERY SLUGGISH. Even with 1.5 GB RAM. It has been used in the past to run some CAD software (Lightwave), but I've since uninstalled it. I primarily use this computer for print design and run CS2 on it. For the most part, I work primarily in Photoshop, Illustrator and InDesign and occasionally work with large (150 - 500 MB) image files for large format applications. I understand this will hog a considerable amount of RAM and it typically does. However, even with smaller image and graphic files (10 - 100 MB), the machine creeps along at snail speed.
I cleaned up an almost exhausted Hard Disk, installed the new OS, and have done all my current software updates. Additionally, I've ran the Disk Utility and Repaired Disk Permissions to find only one real issue. Here is the log from that scan:
+Verifying volume “Macintosh HD”+
+Performing live verification.+
+Checking Journaled HFS Plus volume.+
+Checking Extents Overflow file.+
+Checking Catalog file.+
+Checking multi-linked files.+
+Checking Catalog hierarchy.+
+Checking Extended Attributes file.+
+Checking volume bitmap.+
+Checking volume information.+
+The volume Macintosh HD appears to be OK.+
+Verify permissions for “Macintosh HD”+
*+Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.+*
+Group differs on "private/etc/cups/cupsd.conf", should be 26, group is 4294967294.+
+Group differs on "private/etc/cups/ppd", should be 26, group is 4294967294.+
+Group differs on "private/var/spool/cups/cache", should be 26, group is 4294967294.+
+Group differs on "private/var/spool/cups/tmp", should be 26, group is 4294967294.+
+Group differs on "private/var/spool/cups", should be 26, group is 4294967294.+
+User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/jvm.cfg", should be 0, user is 95.+
+User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/classlist" , should be 0, user is 95.+
+Group differs on "private/etc/cups", should be 26, group is 4294967294.+
+Permissions verification complete+
+Repairing permissions for “Macintosh HD”+
*+Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.+*
+Group differs on "private/etc/cups/cupsd.conf", should be 26, group is 4294967294.+
+Group differs on "private/etc/cups/ppd", should be 26, group is 4294967294.+
+Group differs on "private/var/spool/cups/cache", should be 26, group is 4294967294.+
+Group differs on "private/var/spool/cups/tmp", should be 26, group is 4294967294.+
+Group differs on "private/var/spool/cups", should be 26, group is 4294967294.+
+User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/jvm.cfg", should be 0, user is 95.+
+User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/classlist" , should be 0, user is 95.+
+Group differs on "private/etc/cups", should be 26, group is 4294967294.+
+Permissions repair complete+
So in conclusion, I am at a loss as to why the machine is so **** slow. Anyone have any ideas? I'm not much of an IT dude, so I've pretty much exhausted my knowledge of this issue. Thanks!
~Macincrotch

I have no suggestions but like you I would love answers. Phone support gets me nowhere except 75 minute hold times. I am so disappointed with Apple. In one year, on a single machine, I have had 2 logic boards replaced (as part of the lower RAM slot recall), a hard drive replaced, an optical drive replaced, two batteries replaced (as part of another recall) and a power cord replacement... now my computer is running worse than it has ever run before - thanks to the terrible Beta version of leopard that crapple crappled on us.
I too am getting the same error messages while running disc utility (which takes about an hour now - as applecare described to me, it is because the machine is having a hard time indexing the spotlight feature (??)). But I think they are benign messages and not to be worried about. I wonder if errors related to these messages are really why our machines are performing at the level of the Apple IIGS. What troubles me is the tremendously slow performance - applecare had no ideas and said its best to wait until the update is released. it seems they are still in information gathering phase using suckers like me who ponied up 150 dollars to be unknowing apple product testers. It takes about 30 minutes to edit an album in itunes with color wheels spinning incessantly. I did a clean install before upgrading. System preferences crashes, wireless network access spotty to nonfunctional, and the computer has at times spontaneously gone to sleep. I feel foolish for believing the applecare specialist when he told me 3 weeks ago that my broken HFS volumes, invalid leaf structures and a disc management tool that could not be located would be sorted out by installing leopard. maybe they should rename 10.5 from leopard to turtle.
The last year has been tiresome and costly because apple does not create or adequately support their products; I wont be recommending apple products to my students or have my students learn using them in my classrooms ever again.
if only my rant could fix my machine...

Windows 8.1 File System Performance Down Compared to Windows 7

I have a good workstation and a fast SSD array as my boot volume.
Ever since installing Windows 8.1 I have found the file system performance to be somewhat slower than that of Windows 7.
There's nothing wrong with my setup - in fact it runs as stably as it did under Windows 7 on the same hardware with a similar configuration.
The NTFS file system simply isn't quite as responsive on Windows 8.1.
For example, under Windows 7 I could open Windows Explorer, navigate to the root folder of C:, select all the files and folders, then choose
Properties. The system would count up all the files in all the folders at a rate of about
30,000 files per second
the first time, then about 50,000 files per second the next time, when all the file system data was already cached in RAM.
Windows 8.1 will enumerate roughly
10,000 files per second the first time, and around
18,000 files per second the second time -
a roughly 1 to 3 slowdown.  The reduced speed once the data is cached in RAM implies that something in the operating system is the bottleneck.
Not every operation is slower. I've benchmarked raw disk I/O, and Windows 8.1 can sustain almost the same data rate, though the top speed is a little lower. For example, Windows 7 vs. 8 comparisons using the ATTO speed benchmark:
Windows 7:
Windows 8:
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

No worries, and thanks for your response.
The problem can be characterized most quickly by the slowdown in enumerating files in folders. Unfortunately, besides some benchmarks that show only an incremental degradation in file read/write performance, I don't have any good before/after
measurements of other actual file operations.
Since posting the above I have verified:
My system has 8dot3 support disbled (same as my Windows 7 setup did).
Core Parking is disabled; CPU benchmarks are roughly equivalent to what they were.
File system caching is configured the same.
CHKDSK reports no problems
C:\TEMP>fsutil fsinfo ntfsInfo C:
NTFS Volume Serial Number :       0xdc00eddf00edc11e
NTFS Version   :                  3.1
LFS Version    :                  2.0
Number Sectors :                  0x00000000df846fff
Total Clusters :                  0x000000001bf08dff
Free Clusters :                  0x000000000c9c57c5
Total Reserved :                  0x0000000000001020
Bytes Per Sector :               512
Bytes Per Physical Sector :       512
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length :           0x0000000053f00000
Mft Start Lcn :                  0x00000000000c0000
Mft2 Start Lcn :                  0x0000000000000002
Mft Zone Start :                  0x0000000008ad8180
Mft Zone End   :                  0x0000000008ade6a0
Resource Manager Identifier :     2AFD1794-8CEE-11E1-90F4-005056C00008
C:\TEMP>fsutil fsinfo volumeinfo c:
Volume Name : C - NoelC4 SSD
Volume Serial Number : 0xedc11e
Max Component Length : 255
File System Name : NTFS
Is ReadWrite
Supports Case-sensitive filenames
Preserves Case of filenames
Supports Unicode in filenames
Preserves & Enforces ACL's
Supports file-based Compression
Supports Disk Quotas
Supports Sparse files
Supports Reparse Points
Supports Object Identifiers
Supports Encrypted File System
Supports Named Streams
Supports Transactions
Supports Hard Links
Supports Extended Attributes
Supports Open By FileID
Supports USN Journal
I am continuing to investigate:
Whether file system fragmentation could be an issue. I think not, since I measured the slowdown immediately after installing Windows 8.1.
All of the settings in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
Thank you in advance for any and all suggestions.
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

PSE 6.0 on Mac: File system not supported

Downloaded PSE 6.0 as root on 10.5.6, PPC G5 w/ Mac OS Extended (Case-sensitive Journaled) FS. When I began install, got "file system not supported." Any ideas? Thanks.

Ah, yes, then you're one of the few people who come here who've done that who have a reason. The average person who has trouble resulting from this just randomly chose that option when formatting (lots of people think they won't be able to use capital letters in file names if they don't). Unfortunately, just for future reference, I believe this is a problem with all adobe products. I know it's the same with Photoshop.

File system IS journaled extended

Similar Messages

Maybe you are looking for