N95-1 what is format file system microSD

Hi all!
I'am got formating my microSD external card in my N95, but if i try use the my microSD in Windows XP on desctop PC, Windows say "Memory card is not formated" and request formate my microSD card?
1) What is format file system on my microSD after formating in N95???
2) And N95 be able read microSD after formating in Windows with FAT16 or FAT32???
Thanks...
Nokia! Take a care for me and we real say THANK YOU NOKIA and you can collect a more money

Big Thanks!!! If right understand i can format on Windows and it's don't make some problems in read on phone...
Thanks for all!!!
Nokia! Take a care for me and we real say THANK YOU NOKIA and you can collect a more money

Similar Messages

  • What is virtual file system in sharepoint, where are the site pages stored?

    I came across this paragraph in Inside Microsoft SharePoint 2010; page 126 :-
    When SharePoint Foundation provisions the Proposals document library,it creates a folder named Proposals at the root of the site and then it creates a child folder named Forms.
    Inside the Forms folder, it creates a set of site pages with names such as DispForm.aspx, EditForm.aspx, AllItems.aspx, and Upload.aspx. The reason that SharePoint Foundation creates site pages inside the Forms folder for each
    new list and document library is that these site pages will provide users with the forms they will use to add and manage content.
    My question is that:-
    1) What us the root of the site means? 
    2) Are the pages for edit/add/allitems created in filesystem OR in the content database?
    3)Suppose we create new sitepages, then where are they stored? In filesystem or in content db?

    Hi,
    For All above queries the data and site pages are stored in content database
    Root folder: A folder created for the document library under the web (sub site) and another folder created as child folder named Forms. Site pages are created in SharePoint content database
    SitePages(Add/display/edit): These pages are created in SharePoint content database
    Note: The SharePoint will not create any physical aspx page OR folder in the file system while creating document library.
    Hope this will help you.
    Senthilrajan Kaliyaperumal
    But the book mentions that:-
    When SharePoint Foundation provisions the Proposals document library,it
    creates a folder named Proposals at the root of the site and then it creates a child folder named Forms. 
    Is
    this wrong? Are the folders created in filesystem or content db? If the files are not supposed to go into the filesystem, then why are the folders created?

  • What about these file systems: ext4, reiserfs, and jfs?

    I use ext3 as my file system now.
    It said that these three file systems are better than ext3.
    Ext4 is a successor to ext3. I think it must be better.
    Reiserfs is very fast.
    And jfs is effective(low usage of CPU).
    Could anyone talk about the experiences of using these FSs?

    EXT4: should mature into an awesome FS: faster than JFS, and more fault-tolerant. I'll try it one of these months.
    XFS: nice. By design, it throws away files on an unclean mount, though. I never had FS corruption, but it would just up and get rid of critical files, like fstab, if I had just edited them and then had a nasty shutdown. Maybe it's a good /tmp FS?
    RFS3: it used to be fast with all but large (hundreds of MB) files. IME, the maturing of the 2.6 CFQ and deadline schedulers took care of that. Fsck was never a strong point.
    RFS4: what happens to a jet airplane if a bird gets sucked in an engine? It was kind of like that.
    EXT3 (as a preface to JFS): from early 1998 up to late 2007, moving from 6.4 to 8.4 to 2x6.4+8.4 to 10 to 20 to 120GB, and well over 100 2000 and XP boxes serviced...I had significant corruption of NTFS FS or files all of three times, and none rendered the system unusable (it took a Win98 low-level FAT32 working trojan to do that...friggin' thing had a low threat level according to Semantic, but ate almost all my C: drive). Since moving to Linux in late '07, I've now had at least six partitions made FUBAR, and a handful that went to read-only at the slightest provocation (to give credit where it's due: I could get data off of those before wiping the partition). I've been working with itty computers lately, and EXT3 has been nothing but trouble (many hard-locks, kernel panics, app crashes while writing, etc.--a little hard on the FS). It seems to be fine on machines running all the time, that do their writing sparsely.
    JFS: fast as EXT3, and seems to always recover on an unclean mount. On very slow hardware, it is definitely faster than EXT3...but I mean hardware competitive with Pentium MMXs, where EXT3 regularly maxes out the CPU. Cons? You'd best have your data backed up (but, if you trust any single copy of your data, you're asking for trouble, regardless of FS). It generally can bring your FS back to an old good state. But if not, it will happily throw files away, to make the FS itself clean quicker. So far the worst I've lost were Firefox cookies and other such goodies (never my session, luckily), but it's enough to show the possibilities.
    Last edited by cerbie (2009-02-22 10:50:35)

  • File System Case Sensitive - breaks Write-Once

    I don't find a System property that denotes if the file system is case sensitive.
    If I want a FileFilter to behave as the user is expecting - it must know if the file system that it is running on is case sensitive. For example: On a DOS system the file apple.txt should be returned with the file PEACH.TXT by a FileFilter that is accepting *.TXT files. But on a Unix system only the PEACH.TXT would be returned (case sensitive).
    How would I make my FileFilter a true write-once-run-anywhere class?
    What am I missing?
    David

    For a file filter,
    you can get the file name and convert it to lowercase,
    then compare to a lowercase extension. It's not like
    that will rename the file, the file will still have
    whatever name the file has. However for a FileFilter that is case sensitive - there is a difference in what a File.listFiles(new ExtensionFilter("txt")) returns. And one can not just decide that it doesn't matter.
    Here's a specfic example. On a case insensitive system what is the next file in the sequence of:
    File.001, File.002, File.003, file.004
    Answer: fILE.005 - is valid
    But on a case sensitive system if one uses a FileFilter to find all the files that match "File".* then the answer is "File.004" - ONLY ONE answer, and creating this file will not (should not) overwrite the file.004!
    Seems to me one needs to match the FileFilter to the underling OS - because chances are the user is expecting OS file system naming conventions. If the user doesn't know what file system (and can't know - like on a web server app) then the system better be smart enough to not mess up and clober files.
    So it appears to me that a programmer needs to be able to ask the System what it's file system convention is. And sure I could guess based on some other properties (System.os.name or as Sun did based on file.separator) - but I was hopeful that I didn't need to GUESS.

  • 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)

  • Cluster file system and BDB - does it work ?

    Hi,
    I've read in the reference guide that:
    " No commercial remote filesystem of which we're aware supports
    coherent, distributed shared memory for remote-mounted files"
    What about cluster file systems like veritas cluster file system ?
    Can I use this file system with BDB ?
    I'm trying to find a solution for having one database visible from two computers.
    Reader and writer exist on each machine. Any clue how to do that ?
    best regards
    Moris

    Award points, level up, and earn new privileges
    Level/Points/Privilege
    1 - 0-149 - Reputation level displayed
    2 - 150-499 - Ability to report posts to Apple Support Community Hosts
    3 - 500-999 - Ability to set a custom avatar
    4 - 1000-4999 - Invitation to community conference calls
    5 - 5000-7999 - Regional Meet-up invitations
    6 - 8000-19999 - Access to The Lounge, Apple Support Communities T-Shirt
    7 - 20,000-34,999 - Coming Soon
    8 - 35,000-49,999 - Coming Soon
    9 - 50,000-79,999 - Coming Soon
    10 - 80,000+ - Coming Soon

  • [Solved] Canot format MicroSD. File system is read-only

    I formatted it for my special needs some time ago using fdisk.
    Don't remember the partition table, but there was 1 fat32 and 1 ext4 partition.
    Now I want to format it fat32 clean, but I get the errors.
    When I open GParted, it says
    GParted wrote:/dev/sdb contains GPT signatures, indicating that it has a GPT table.  However, it does not have a valid fake msdos partition table, as it should.  Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables.  Or perhaps you deleted the GPT table, and are now using an msdos partition table.  Is this a GPT partition table?
    If I click yes - it shows partitions, but creating new partition table fails, as it is read-only.
    If I click no - it does not show up in the device list.
    Here's a picture of the structure of the device.
    What also strange, I remember making 1 GiB ext4, and rest fat32. But it shows the opposite.
    So I tried formatting it with fdisk
    $ fdisk /dev/sdb
    o
    n
    w
    fdisk: cannot write disk label: Bad file descriptor
    I made sure they are unmounted
    umount: /dev/sdb1: not mounted
    umount: /dev/sdb2: not mounted
    Then I checked the filesystems. The second one appears to be read-only
    # fsck /dev/sdb1
    fsck from util-linux 2.23.2
    fsck.fat 3.0.22 (2013-07-19)
    /dev/sdb1: 18 files, 96978/698280 clusters
    # fsck /dev/sdb2
    fsck from util-linux 2.23.2
    e2fsck 1.42.8 (20-Jun-2013)
    fsck.ext4: Read-only file system while trying to open /dev/sdb2
    Disk write-protected; use the -n option to do a read-only
    check of the device.
    # fsck -n /dev/sdb2
    fsck from util-linux 2.23.2
    e2fsck 1.42.8 (20-Jun-2013)
    /dev/sdb2: clean, 860/65664 files, 56633/262144 blocks
    Tried the zero trick, but failed as well.
    # dd if=/dev/zero of=/dev/sdb
    dd: failed to open ‘/dev/sdb’: Read-only file system
    # dd if=/dev/zero of=/dev/sdb2
    dd: failed to open ‘/dev/sdb2’: Read-only file system
    Tried to disable the write-protection
    # hdparm -r0 /dev/sdb
    /dev/sdb:
    setting readonly to 0 (off)
    readonly = 0 (off)
    After that, fdisk still fails to format.
    In Windows 8, it mounts only the fat32 part.
    diskpart can't erase partition table as well.
    Last edited by Doctor Drive (2013-10-09 08:28:13)

    Finally I found the solution
    MicroSD adapter has a "lock" feature.
    When I inserted the adapter, the lock always triggered to locked state.
    So I fixed it in unlocked state using the ducktape.
    http://kb.sandisk.com/app/answers/detai … -or-locked

  • What is the FAT file system and how can I format my LEXAR flash drive with it?

    Recently, Apple support helped me download my songs form iTunes to a LEXAR flash drive. I connected it to the USB connector in my car. My car's display said
    "unsupported". My other LEXAR usb plays music perfectly. What is wrong? My car's manual says that my audio system reads and plays audio files on the USB flash memory device in MP3, WMA, AAC formats. (AAC format files recorded with iTunes only.)  How do I correct this problem?

    Reformatting the drive will completely erase it so make sure you have copies of the files.
    FAT format is an older non-Mac format but is still found on plenty of things such as flash drives.  It's the one format that both Macs and Windows computers can fully use but it has limitations outside small-scale use.  Your Apple person must have reformatted your drive to Mac format which wasn't very smart of the person since almost nothing except Apple products can work with Mac format.  Are you sure you explained how you intended to use the drive, or did you just ask the person how to put files on there?

  • What is the next step after editing or triming a video ? What type of file format to save and what to do after that ?

    what is the next step after editing or triming a video?
    what type of file format should be save and what to do after that?

    In the early days of digital video editing, an export render could take hours!  Not many applications are as hard on system resources as video editing, and rendering the final edit is probably the most system intense action of all.  
    Head on over to the Premiere Pro Hardware forum to see what sort of computer hardware the pros use for NLE (non linear editing), or to the PPBM5 site for a better look.
    PPBM5 Benchmark
    Also check out the specs on the Video Guys website

  • What is the best way to copy aperture library on to external hard drive? I am getting a message that say's "There was an error opening the database. The library could not be opened because the file system of the library's volume is unsupported".

    What is the best way to copy aperture library on to external hard drive? I am getting a message that say's "There was an error opening the database. The library could not be opened because the file system of the library's volume is unsupported". What does that mean? I am trying to drag libraries (with metadata) to external HD...wondering what the best way to do that is?

    Kirby Krieger wrote:
    Hi Shane.  Not much in the way of thoughts - - but fwiw:
    How is the drive attached?
    Can you open large files on the drive with other programs?
    Are you running any drive compression or acceleration programs (some drives arrive with these installed)?
    Can you reformat the drive and try again?
    Hi Kirby,
    I attached the UltraMax Plus with a USB cable. The UltraMax powers the cable so power is not an issue. I can open other files. Also, there is 500GB of files on the drive so I cannot re-format it. Although, I noted I could import the entire Aperture Library. However, I do not want to create a duplicate on my machine because that would be defeating the purpose of the external drive.
    Thanks,
    Shane

  • File System (formatting, partitioning)

    I have a question about the HFS+ (HFS Plus) file system...
    I recently purchased a 17 inch Macbook Pro along with a LaCie d2 Extreme External Hard Drive. I am dual-booting on my Macbook Pro using Bootcamp and want to be able to use the external hard drive in both work environments and also be able to access files from each OS. What would be the best and most reliable way to go about doing this.
    I was going to format the entire drive as FAT32 since both operating systems can write and read to this file system... but I wanted other opinions on this. Should I partition the drive and have an NTFS partition for Windows XP, a FAT32 partition for both OSes and an HFS+ partition for Mac OSX??
    All help is greatly appreciated.

    "So, if I understand correctly, Mac Drive would allow me to read and write to an HFS+ volume from both Windows XP and Mac OSX."
    Yes and no. MacDrive is a file system driver for Windows. Mac OS X supports HFS+ natively.
    "Therefore, I would not have to partition the drive at all and I could have the whole drive formatted as HFS+??"
    Nope. Windows XP needs a FAT32 or NTFS drive to boot from, MacDrive will be loaded during the boot process.
    "How does Mac Drive work... do I install it on XP?"
    Yep. After you installed it, you can see any HFS+ partition in the Windows Explorer as a separate drive.
    "Also, does it slow down the drive at all or require emulation or anything like that?"
    No.

  • IPod formatted to UNIX File System (UFS)

    Hello all, I had an old 15G iPod (the generation with the 4 button above the wheel) and I decided to reformat it and use it as a firewire drive, it's not used for music anymore. Anyway, I was about half way through the format and I noticed I had accidently sellected UNIX File System (UFS) instead of Mac OS Extended. Well I let lt finish and thought I'd just reformat it again to Mac OS Extended, only now the iPods not even being recognized by OSX? I looked in Disk Utility and nothing there either. iPod restore does nothing either, just says connect an iPod. There's an Apple on the screen and that's it? What gives? Will I be able to get this thing running again?

    Thanks but no thanks! I got it going using info at this link:
    http://ipodlinux.org/Installation
    Got it in Disk Mode!!!

  • I am trying to download EndnoteX4 but keep getting the message 'no mountable file systems'.  What does this mean and how do I fix it?

    I am trying to download EndNoteX4 but keep getting the message 'no mountable file systems'.  What does this mean and how do fix it?

    jenitsallgood wrote:
    I am really unsure as to what I am doing wrong.
    Maybe you are doing nothing wrong and the problem is with the disk.
    Use SuperDuper or CarbonCopy Cloner
    to clone your system to an external drive.
    Then boot from your DVD go to Disk Utility and choose your entire drive > top icon in DIsk Utility.
    Go to Erase tab. Choose format: Mac OS Extended (Journaled). Click on erase. Now, install Lion and when you get to setup assistant choose to migrate from your external drive.
    This is slightly different than baltwo described and slighly longer but if there is any corruption on your disk a more through way to go, IMO.
    What baltwo is saying is to clone your volume over to an external hard drive with CCC reformat and clone it back. This will defragment the files and make them all contiguous but will not address any directory problems.
    Your choice. You can do it one way, then the other if it doesn't work out for you.

  • QCOW LVM What would be the best file system ?

    I would like to put my kvm instances (iso + qcow2 file) in separate logical volumes (I am using LVM).
    I am just wondering if there is a better file system to handle just these two particular files.
    Just ext2 ?
    Thanks for any hints.

    Hi,
    Please check the article below
    http://sharepoint.nauplius.net/2013/01/supported-file-formats-in-the-sharepoint-2013-media-web-part/
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/9c9eb5a4-89c2-4550-af32-e23e568849e7/what-file-type-is-the-best-video-format-to-house-in-sharepoint?forum=sharepointgenerallegacy
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • Can one network hard drive back up both a Mac and a PC?  What file system?

    We have both a Mac and a PC on our home network. I would like to use a network external drive to back them both up, instead of connecting each to its own external drive for backups. Iomega makes one, for example.
    The external drives I see advertised say that they are both Mac and PC compatible, but don't explicitly say that you can connect both at the same time. Can you?
    If so, what file system does the network drive use? Does it have a partition, one side with HFS for Mac and the other with NTFS for Windows? Is this really workable?
    And most importantly, will such a network drive work with TM?
    Confused,
    Barb

    I have a late 08 MackBook Pro and several Vista & XP machines. I currently backup the MBP and the primary Vista machine to a 1 TB drive attached via USB to an Airport Extreme router. No problems backing both up through the APE to the USB drive.
    The one thing I read when getting ready to set this up is that I should format the drive with the Apple file system, not one of the Microsoft file systems. I did (did it as an external drive off the MBP), and had no subsequent problems with Time Machine backups or Vista backups (using Acronis True Image).

Maybe you are looking for