UEFI and Legacy .... tips

I was  installed ubuntu alongside windows8 but while restarting PC directly windows8 loaded, even I enabled Legacy mode. In BIOS setting it was clearly given that "In Legacy mode both UEFI and Legacy are available and UEFI has heigher priority ".
How to change the priority and how to load both operating systems and give a choice to us to select one of them while starting PC. 
" HP Pavilion g6-2202tx Notebook PC "
please provide me the details.

I found that there is no way to change the boot order priority ...,
this is the link saved my time...
http://h30434.www3.hp.com/t5/Desktop-Operating-Systems-Software-Recovery/UEFI-vs-Legacy-Boot-order/m...

Similar Messages

  • Boot UEFI or Legacy ---- tips

    If your PC or laptop supports UEFI and legacy mode then the following tips may help you. Legacy enabled:If the bios setting is legacy enabled then hard drives and USB devices will normally boot.  If you are using two independent hard drives that are not connected by boot manager then the UEFI boot hard drive will always boot first before the legacy hard drive unless the bios allows you to change the boot priority. Legacy disabled (UEFI mode):If the bios setting is legacy disabled then only UEFI devices will boot.  You may run into no hard drive selection menu, no boot option menu or Boot Device not Found followed by a message Hard Disk (3f0). USB flash drives boot considerations:If you wish to boot up a USB flash device using Windows 7 repair, Windows 8 repair, Windows 7 or Windows 8 installation media then be sure to create the flash drive formatted as FAT32.  You may notice a bootable flash drive showing twice in the boot menu, one marked UEFI and one not marked UEFI.  Both will boot up. The popular MS Windows 7 USB WIndows installation media creation tool will create a NTFS flash drive using a Windows 7/8 iso file in NTFS format which is not bootable in UEFI mode. It works fine in legacy mode.  To get around the NTFS issue, create the flash drive in NTFS then copy the contents to your hard drive, quick format the flash drive to FAT32 and then copy back the contents back to the hard drive.  There are other known methods to do the above but this method is very simple. 

    i have a HP Sleekbook 14-b035tx which came with a windows 8 OS installed already. due to some reasons, i tried to shift it back to windows 7. After many unsuccessful tries, i finally managed to install windows 7 by changing my boot sequence to Legacy Boot.
    later on, due to lack of drivers for win 7, i installed, rather upgraded to win 8 which was running on legacy boot (using MBR if im not wrong). now, i want to install a fresh copy of win 8 with UEFI but the problem is when i change my boot sequence to disable legacy boot, then during installation of win 8, i cannot see my HDD ... im using a flash drive to install win 8 which is already in UEFI (i used diskpart for that).
    also, when i use legacy boot and try to install windows, then the HDD appears and when i format the HDD and create new partitions, it creates 3 partitions (System, MSR, Reserved) and the fourth one for OS. i tried installing the windows like this but after install, when i change the boot sequence to UEFI again, it fails to boot
    now, i want to install windows to UEFI... and i really need help with this please ... i hope i have explained the scenario... if anyone would like to ask anything, please do ... as i really need to get this away... and also, i'd like to ask that how can i check if my HDD has been changed from MBR to GTP 

  • Latest uefi and legacy bios for R9 280X Gaming 3G

    By working too late with too little sleep, I'm afraid I've done something pretty stupid while trying to flash two separate R9 280X Gaming 3G cards; I've corrupted both the legacy and hybrid bios on both cards. And (wait for it) I don't have backups of the original ROMs. Fortunately, I have a third card I can run the machine off of while I flash the hosed cards, but I need the ROM files. Could someone please point me towards the proper legacy and hybrid ROM files for these cards? The serial numbers, in case it matters, are 602-V277-34SB1402014989 and 602-V277-44SB1312123180.
    I promise I'll be more responsible in the future. Thanks!

    Yes, that's the picture I was referring to. If you take it literally, it's showing that position two (the UEFI bios) is towards the side of the card with the power connectors (on the right, if you're looking at the side with the fan). However, while only one of the R9 280X cards I have is labeled on the motherboard, it shows position 2 as being towards the end of the card with the video connectors.
    To state that more simply, I suppose, the picture on the page you linked implies that the polarity of the switch shown is in relative to when you're looking at the card from the fan side. I think what's actually going on here is that the picture of the card with the fan is just intended to show where the switch is; the actual close-up of the switch is actually from the side with the motherboard visible (in other words, position 2 is towards the end of the card that is visible at the back of the computer case).

  • Clean install from a Lenovo installa. dvd: UEFI vs Legacy + Thinkpad setup acc. to Lenovo user Guide

    Machine: T520 bought Feb. 2012
    O.S. W~7 Pro 64-bit
    I want to wipe the harddrive, buy a Lenovo W~7 PRO installation DVD, and do a completely clean installation.
    Lenovo User Guide (.pdf) Ch. 8, Adv'd Config, Installing Windows 7, p. 295 (212 of 298) says:
    Start Thinkpad setup, then choose UEFI versus Legacy, then insert the installation DVD.
    This obviously does not apply when the harddrive has already been wiped (necessary to 100% eliminate all traces of irreversible damage caused by a virus, including the re-installation partition (Q-drive).
    When an intallation DVD is purchased from Lenovo, is not the first step to insert the DVD ?!! Then presumably there is an installation wizard resulting in a restored O.S. ?!!
    If not, please tell me what surprises are in store, and where I can find a reliable written resource to consult !!!
    Thank-you.
    Solved!
    Go to Solution.

    You're over-thinking this and making it harder than it needs to be.  The manual isn't helping...
    The BIOS is stored in non-volatile memory on the motherboard.  One would probably call it firmware, not software.  It is there regardless of what's on the HDD - or whether there's even an HDD installed.
    Turn your machine off.  Turn it on again.  When you see the logo screen, hit F1 - multiple times if necessary.  That gets you into the motherboard's BIOS configuration utility - what the manual is calling "Setup".
    Here's a snip below from the T520 BIOS configuration utility (actually from the on-line BIOS simulator).  In the StartUp tab you can see where UEFI/Legacy can be selected.  You can configure UEFI boot there.  Or "both".  Or - probably - just select Setup Defaults, save, and exit.
    Z.
    The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc.  The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Latest Bioses UEFI and non UEFI for R9 290 GAMING 4G?

    Please post latest bioses UEFI and non UEFI for R9 290 GAMING 4G:
    sn: 602-V308-02SB1312014791
    Thank's

    Svet provided the latest vbios which is TV308MH.131.
    Quote from: gjamie86 on 26-May-15, 22:02:09
    I found a more recent file though at techpowerup (015.044.000.005.000000) Build date 2014-02-18 00:22:00.
    You can't flash any random vbios. Even if it is offered for the same model at techpowerup. Any batch of the same card model can require a different vbios version. Only MSI or the staff here can tell you which version matches. The version informations taken from gpu-z (like 015.044.000.005.000000) are irrelevant and do not represent any real vbios version. Besides TV308MH.131 that has been provided is dated 08/13/14 (Month-Day-Year).
    Quote from: gjamie86 on 26-May-15, 22:02:09
    Last question, can I flash bios #2 as well or is that locked ?
    The card offers a UEFI/GOP and a legacy vbios to switch between. Both could be updated (if there would be later versions what is not the case).
    EDIT: gjamie86, just realized that you hijacked this thread. open an own topic and provide the S/N of card and current (original) vbios saved to file. >>Please read and comply with the Forum Rules.<<

  • Grub, UEFI, and encrypted partitions

    I followed the tutorials on the Wiki regarding setting up luks encryption over LVM which worked fine. Part of this process involved getting grub to decrypt the root partition, which also worked. However, I later went and followed instructions for getting UEFI boot to work; I created a separate /boot partition, used grub-install, etc. I'm now in a weird state, though: grub is still using (and unlocking) the root partition and using whatever is in its /boot directory when it really should be using the /boot partition. I've managed to confuse myself enough through all this that I'm not sure what config files and commands I need to mess with to get grub to load the initramfs from the actual boot partition while not also screwing up the root partition that should be unlocked/mounted by systemd.
    My common sense tells me that the latter has nothing to do with the former but it took me long enough to figure out the hack of copying everything in the boot partition to root's /boot just to get the thing booting again after a kernel update that I'd rather just ask here

    tcdavis wrote:I'm now in a weird state, though: grub is still using (and unlocking) the root partition and using whatever is in its /boot directory when it really should be using the /boot partition.
    UEFI and a dedicated /boot partition are separate things, and they are not dependent on one another. The problem is most likely coincidental.
    Make sure your "root=" and "cryptdevice=" kernel parameters are correct. Edit /etc/default/grub, and use the UUID of the LUKS container on the new /boot partition, replacing the old UUID of the root filesystem. This should be the UUID of the LUKS container itself, not the filesystem contained within it. Use `cryptsetup luksUUID /dev/sda2` substituting sda2 with your /boot partition. This only applies to the kernel and is not directly related to GRUB, so it's just a precautionary measure.
    Make sure /boot is mounted, and regenerate grub.cfg:
    mount /boot
    grub-mkconfig -o /boot/grub/grub.cfg
    Delete the contents of /boot on the root partition to prevent confusion:
    umount /boot
    rm -r /boot
    mkdir /boot
    mount /boot
    Also make sure your /boot partition is being mounted (via crypttab and a keyfile) automatically at boot, or you will run into problems later on.
    Strike0 wrote:If you, in your first attempt, installed grub to the MBR and your bios is set to dual legacy/uefi, the grub bios may take precedence now. You should boot the machine/install ISO in pure efi mode before executing the grub install for uefi and best wipe the grub bios which probably installed itself to sectors before the first partition.
    I don't know enough about the GRUB internals to say whether or not the UUID of the /boot partition is embedded in GRUB's UEFI stub, but in theory the following commands should overwrite both the BIOS boot loader and UEFI.
    mount /boot
    grub-install --target=i386-pc --recheck
    grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub_uefi --recheck
    This way GRUB should use the correct /boot no matter if it is booting in BIOS or UEFI mode.
    If these instructions don't solve your problem, please specify what stage of the boot process is failing, and what you saw prior to the boot failure (e.g. did you get a GRUB rescue shell? Did you see the GRUB menu? Did GRUB indicate an incorrect UUID?)

  • 660Ti UEFI/GOP & legacy bios request.

    Hi.
    Preparing myself for the Haswell upgrade.
    Can I please have the latest UEFI/GOP & legacy BIOS(es) for the following card?
    Card: MSI N660Ti PE 2GD5/OC 2GB.
    Serial#: 602-V284-050B1211045023.
    Original Vbios: 80.04.4B.00.16 (P2004-0001).
    Vbios image dump: (*https://www.dropbox.com/s/y6crdr9y1ti5t6u/MSI%20N660Ti%20PE%202GD5-OC%202GB%20GK104%20original%20bios.rar *)
    Thanks.
    PS.
    Which ver. of nvflash should I use for flashing?

    Thanks for the file.
    I upgraded just for the sake of being up-to-date,
    but I solved the problem earlier otherwise 
    So, I can't really comment if the newer/provided VBIOS solves the black screen problem or not.
    In my case the problem was from Nvidia driver 320.18.
    There is a supposedly acknowledged problem with Win 8 which silently installs  on the background
    an earlier Nvidia driver (311.06) from windows update,
    and *not* informing the user about the background install/need for reboot.
    If the user installs another/later driver without rebooting 1st it becomes a driver binary mess.
    In my case, when using 320.18 with Win 8 (even from a clean install and not messing with any previous driver),
    caused the monitor going to sleep after POST and when MB UEFI handed-off control to OS in 80% of the cases.
    A situation I could exit from only with a hard shutdown.
    So, for any other poor soul having similar problems,
    it might be a good idea to try an earlier Nvidia driver.

  • Switch from uefi to legacy bios

    How would you go about switching from uefi to legacy bios/boot? Would you have to reinstall windows? Can you use the hidden partitions for this? Would you need a windows install disk?

    how do I switch my partitioning scheme to MBR so I can use legacy boot/bios?
    In the System Configuration section of the UEFI, for starters, set the Boot Mode to CSM Boot. That essentially bypasses the UEFI.
    The easiest way to change the partitioning from GPT to MBR is to use old fashion tools like a Windows 7 installation DVD to delete the existing partitions and create new ones.
    -Jerry

  • Gtx 970 gaming 4g and legacy bios

    Hi all,
    As a newbie im looking for some assistance if at all possible.
    ive got a hp pavillion h8-1070uk
    8gb ddr3 ram,
    ipisb-ch board with bios version 7.12 (lastest version)
    gt545 3gb existing card installed
    be quiet 630w psu with 48a output.
    I'm trying to install a gtx970 gaming 4g and like a few others on here im getting to the bios screen then nothing further.  Ive read one post (which i cant find now) that there is a bios upgrade for the card to enable legacy bios over uefi (which I've been told is causing the problem).
    is there such an upgrade available ? and how would i install it on the card if i cant get to a boot screen ??
    Thanks in advance

    Quote from: flobelix on 16-November-14, 01:56:11
    There is no legacy vbios for a GTX970 but just hybrid vbios versions supporting legacy and UEFI booting. These vbios versions will not work on older boards with a UEFI vbios not being GOP compliant. However UEFI or legacy vbios is NOT your problem as the system would else not post at all and you would not even see the bios screen. What you experience is a compatibility issue seen on many oem machines that are not updated properly. For socket 1155 board a ME8 bios is required to run vgas of the current generation.
    I don't suppose this is a variant on the same issue as the one I've posted about elsewhere on this forum (https://forum-en.msi.com/index.php?topic=184769.0)? I have a socket-1366 i7-950 on a legacy-BIOS ASUS P6X58D motherboard, which still has perfectly decent CPU performance for everything I need of it and I'm loathe to replace.
    ASUS haven't updated the BIOS since 2012, and I'm on that version; the oddness is that whether the system boots or not depends on how I've connected my monitor and whether there's more than one.
    I do see when googling around there are people using the same card with the Rampage II and other similar X58 boards of that era, so there may be a quirk specific to this board, card and place.

  • What is the diff b/w flat file and legacy system?

    Hi everyone,
           when v say v r working on scenario FILE to FILE? which format of file r v usually working on? and what is the diff b/w flat file and legacy system?
    thanx

    Hi,
    <i>when v say v r working on scenario FILE to FILE? which format of file r v usually working on?</i>
    >>>Many a times it will be a Flat file with CSV format,Tab delimited format, fixedlength fields.
    <i>what is the diff b/w flat file and legacy system?</i>
    >>>We can not differeniate like this..
    Flat file may come from any systems, it may be live system or legacy system.
    Legacy system- is something like old, or past one. If you talk about SAP , then older versions of SAP can be  called as a legacy system.
    So it may be a file system, or any system which is old version but it doesnot mean it is not in use,
    Regards,
    Moorthy

  • What is a R/3 system, logical system, and legacy system...???

    Hi,
    Please throw some light on...What is a R/3 system, logical system, and legacy system...???

    Hi,
    R/3 system is a normal SAP system that stores data.
    A legacy system is an existing computer system or application program which continues to be used because the user does not want to replace or redesign it.
    Logical System:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/5aa2a0deb91548a1842f8485dee4a2/frameset.htm
    Technical System:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
    Regards,
    Subhasha

  • How do I remove LG Health and Smart Tips ?

    How do I remove LG Health and Smart Tips ?

    Please note that any discussion of rooting/hacking is a violation of the Verizon Wireless Terms of Service
    Message was edited by: Admin Moderator

  • What are the differences between file vault and legacy file vault?

    what are the differences between file vault and legacy file vault?

    Legacy is an encrypted disk image of your Home folder, FileVault2 is whole disk encryption

  • Dynamic Optimization and PRO tips

    Is dynamic optimization a new feature on System Center 2012 or it was included in previous versions under a different name?
    What are the main differences between dynamic optimization and PRO tips beside trigger customization?
    Can dynamic optimization work with Operations Manager Monitoring VMM only?
    Thanks!

    Hi
    Your filemaker pro database must be exported as sql in order for you to use it to create a database.
    This may not be a simple create and import into MySQL, see - http://dev.mysql.com/tech-resources/articles/filemaker_mysql_whitepaper/filemaker_to_mysql _whitepaper01.htm.
    PZ

  • Drives disappear between UEFI and Linux

    This problem has me stumped for a month, so I'm hoping someone can shed some light on this.
    Originally, I had an MSI motherboard with BIOS only, GRUB2 booting Arch and Windows 7, no problems whatsoever. I upgraded to an Asus motherboard with UEFI, and at first Arch booted fine (Windows just blue screened). Subsequent boots would randomly fail, sometimes telling me Arch couldn't find the root drive, sometimes the home drive, and other times it would boot successfully. There was no telling how many times I would need to reboot before Arch would find all the drives. I returned the Asus board and replaced it with a Gigabyte Z97-D3H, but the problem continued.
    Finally this Tuesday I reinstalled Arch in UEFI mode, and instead of a bootloader, UEFI boots Linux directly, as shown in the "Using UEFI directly" section of EFISTUB. Still, Arch randomly fails to find my drives.
    Here is my drive layout when Arch boots properly (when it doesn't, lsblk also can't see the missing drive):
    ┌── kiba ⟶ Paradise ~
    └───── lsblk -o name,fstype,size,label,mountpoint
    NAME FSTYPE SIZE LABEL MOUNTPOINT
    sda 59.6G
    ├─sda1 vfat 512M SHAMAN /boot
    ├─sda2 ext4 51.1G Hige /
    └─sda3 swap 8G swap [SWAP]
    sdb 119.2G
    └─sdb1 ext4 119.2G Kiba /home
    sdc 465.8G
    ├─sdc1 ntfs 128G Tsume
    └─sdc2 ext4 337.8G Toboe /home/kiba/Toboe
    And /etc/fstab:
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda2 UUID=67de5f82-861e-4934-94ba-9fdde2225bb1
    LABEL=Hige / ext4 rw,noatime,discard,data=ordered 0 1
    # /dev/sda1 UUID=6A35-D4DE
    LABEL=SHAMAN /boot vfat rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    # /dev/sdb1 UUID=c89186ab-c005-4598-a5b9-2be4d0d6202c
    LABEL=Kiba /home ext4 rw,noatime,discard,data=ordered 0 2
    # /dev/sda3 UUID=0ee5665b-13e3-4592-bdf1-5701636697f3
    LABEL=swap none swap defaults 0 0
    LABEL=Toboe /home/kiba/Toboe ext4 defaults 0 0

    Oops, I forgot to mention that. As far as I can tell, the SMART status is fine on all the drives, but then I could be missing something.
    Here's the output for the root drive:
    ┌── kiba ⟶ Paradise ~ 11:49:50
    └───── s smartctl -t long /dev/sda && sleep 61 && s smartctl -a /dev/sda
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.18.6-1-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
    Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
    Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
    Testing has begun.
    Please wait 1 minutes for test to complete.
    Test will complete after Sat Feb 14 11:52:27 2015
    Use smartctl -X to abort test.
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.18.6-1-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF INFORMATION SECTION ===
    Model Family: JMicron based SSDs
    Device Model: KINGSTON SV100S264G
    Serial Number: 08AAA0003175
    Firmware Version: D100811a
    User Capacity: 64,023,257,088 bytes [64.0 GB]
    Sector Size: 512 bytes logical/physical
    Rotation Rate: Solid State Device
    Form Factor: 2.5 inches
    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: Sat Feb 14 11:52:28 2015 PST
    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: ( 0) The previous self-test routine complet ed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 30) seconds.
    Offline data collection
    capabilities: (0x1b) 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.
    No 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: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 1) minutes.
    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 Unknown_Attribute 0x0007 100 100 050 Pre-fail Always - 0
    5 Reallocated_Sector_Ct 0x0013 100 100 050 Pre-fail Always - 0
    7 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0
    8 Unknown_Attribute 0x0005 100 100 050 Pre-fail Offline - 0
    9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 13005
    10 Unknown_Attribute 0x0013 100 100 050 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 3565
    168 SATA_Phy_Error_Count 0x0012 100 100 000 Old_age Always - 15
    175 Bad_Cluster_Table_Count 0x0003 100 100 010 Pre-fail Always - 0
    192 Unexpect_Power_Loss_Ct 0x0012 100 100 000 Old_age Always - 0
    194 Temperature_Celsius 0x0022 031 100 020 Old_age Always - 31 (Min/Max 23/40)
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    240 Unknown_Attribute 0x0013 100 100 050 Pre-fail Always - 0
    170 Bad_Block_Count 0x0003 100 100 010 Pre-fail Always - 0 89 0
    173 Erase_Count 0x0012 100 100 000 Old_age Always - 5 9441 7415
    SMART Error Log Version: 1
    ATA Error Count: 15 (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 15 occurred at disk power-on lifetime: 12999 hours (541 days + 15 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
    84 51 00 00 00 00 a0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 a0 08 00:11:20.100 IDENTIFY DEVICE
    b1 c1 00 00 00 00 00 ff 00:11:19.800 DEVICE CONFIGURATION FREEZE LOCK [OBS-ACS-3]
    f5 00 00 00 00 00 00 ff 00:11:19.800 SECURITY FREEZE LOCK
    ec 00 00 00 00 00 00 00 00:11:17.600 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 00 00:11:17.600 IDENTIFY DEVICE
    Error 14 occurred at disk power-on lifetime: 12999 hours (541 days + 15 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
    84 51 00 00 00 00 a0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 a0 08 00:15:36.300 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 ff 00:15:35.900 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 00 00:15:33.700 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 00 00:15:33.700 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 00 00:15:33.700 IDENTIFY DEVICE
    Error 13 occurred at disk power-on lifetime: 12986 hours (541 days + 2 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
    84 51 00 00 00 00 00
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 00 00 00:03:08.200 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 ff 00:03:02.700 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 ff 00:02:46.000 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 ff 00:02:41.400 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 ff 00:02:24.700 IDENTIFY DEVICE
    Error 12 occurred at disk power-on lifetime: 12763 hours (531 days + 19 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
    84 51 00 00 00 00 00
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 00 00 00:00:35.900 IDENTIFY DEVICE
    00 00 00 00 00 00 00 ff 00:00:29.400 NOP [Abort queued commands]
    00 00 00 00 00 00 00 ff 00:00:12.400 NOP [Abort queued commands]
    00 00 00 00 00 00 00 ff 00:00:00.000 NOP [Abort queued commands]
    Error 11 occurred at disk power-on lifetime: 12706 hours (529 days + 10 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
    84 51 00 00 00 00 00
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 00 00 00:02:30.800 IDENTIFY DEVICE
    e7 00 00 00 00 00 a0 ff 00:02:11.900 FLUSH CACHE
    e7 00 00 00 00 00 a0 08 00:01:44.500 FLUSH CACHE
    e7 00 00 00 00 00 a0 08 00:01:43.300 FLUSH CACHE
    e7 00 00 00 00 00 a0 08 00:01:40.300 FLUSH CACHE
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Completed without error 00% 13005 -
    # 2 Extended offline Completed without error 00% 13005 -
    Selective Self-tests/Logging not supported
    And for the home drive:
    ┌── kiba ⟶ Paradise ~ 11:52:28
    └───── s smartctl -t long /dev/sdb && sleep 61 && s smartctl -a /dev/sdb
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.18.6-1-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
    Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
    Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
    Testing has begun.
    Please wait 1 minutes for test to complete.
    Test will complete after Sat Feb 14 11:54:25 2015
    Use smartctl -X to abort test.
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.18.6-1-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF INFORMATION SECTION ===
    Model Family: JMicron based SSDs
    Device Model: KINGSTON SV100S2128G
    Serial Number: 08BB20039237
    Firmware Version: D110225a
    User Capacity: 128,035,676,160 bytes [128 GB]
    Sector Size: 512 bytes logical/physical
    Rotation Rate: Solid State Device
    Form Factor: 2.5 inches
    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: Sat Feb 14 11:54:26 2015 PST
    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: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 30) seconds.
    Offline data collection
    capabilities: (0x1b) 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.
    No 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: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 1) minutes.
    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 Unknown_Attribute 0x0007 100 100 050 Pre-fail Always - 0
    5 Reallocated_Sector_Ct 0x0013 100 100 050 Pre-fail Always - 0
    7 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0
    8 Unknown_Attribute 0x0005 100 100 050 Pre-fail Offline - 0
    9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 9899
    10 Unknown_Attribute 0x0013 100 100 050 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 3541
    168 SATA_Phy_Error_Count 0x0012 100 100 000 Old_age Always - 13
    175 Bad_Cluster_Table_Count 0x0003 100 100 010 Pre-fail Always - 0
    192 Unexpect_Power_Loss_Ct 0x0012 100 100 000 Old_age Always - 0
    194 Temperature_Celsius 0x0022 034 100 020 Old_age Always - 34 (Min/Max 23/40)
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    240 Unknown_Attribute 0x0013 100 100 050 Pre-fail Always - 0
    170 Bad_Block_Count 0x0003 100 100 010 Pre-fail Always - 0 135 0
    173 Erase_Count 0x0012 100 100 000 Old_age Always - 2 16503 12094
    SMART Error Log Version: 1
    ATA Error Count: 37 (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 37 occurred at disk power-on lifetime: 9893 hours (412 days + 5 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
    84 51 00 00 00 00 a0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 a0 08 00:00:09.200 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 ff 00:00:08.800 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 ff 00:00:08.800 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 00 00:00:06.600 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 00 00:00:06.600 IDENTIFY DEVICE
    Error 36 occurred at disk power-on lifetime: 9880 hours (411 days + 16 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
    84 51 00 00 00 00 00
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 00 00 00:09:55.000 IDENTIFY DEVICE
    ec 00 00 00 00 00 a0 ff 00:09:48.800 IDENTIFY DEVICE
    e7 00 00 00 00 00 a0 08 00:09:47.900 FLUSH CACHE
    ec 00 01 00 00 00 00 08 00:04:00.000 IDENTIFY DEVICE
    ec 00 01 00 00 00 00 08 00:03:56.100 IDENTIFY DEVICE
    Error 35 occurred at disk power-on lifetime: 9855 hours (410 days + 15 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
    84 51 00 00 00 00 00
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 00 00 00:03:35.400 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 ff 00:03:29.200 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 ff 00:03:24.600 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 00 00:01:00.000 IDENTIFY DEVICE
    ec 00 00 00 00 00 00 00 00:01:00.000 IDENTIFY DEVICE
    Error 34 occurred at disk power-on lifetime: 9168 hours (382 days + 0 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
    84 51 00 00 00 00 00
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 00 00 00:00:21.800 IDENTIFY DEVICE
    00 00 00 00 00 00 00 ff 00:00:21.800 NOP [Abort queued commands]
    00 00 00 00 00 00 00 ff 00:00:00.000 NOP [Abort queued commands]
    Error 33 occurred at disk power-on lifetime: 9165 hours (381 days + 21 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
    84 51 00 00 00 00 a0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    ec 00 00 00 00 00 a0 00 00:18:36.900 IDENTIFY DEVICE
    a1 00 00 00 00 00 a0 00 00:18:36.900 IDENTIFY PACKET DEVICE
    ec 00 00 00 00 00 a0 ff 00:18:36.900 IDENTIFY DEVICE
    ec 00 00 00 00 00 a0 ff 00:18:00.100 IDENTIFY DEVICE
    ec 00 00 00 00 00 a0 ff 00:17:49.100 IDENTIFY DEVICE
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Completed without error 00% 9899 -
    # 2 Extended offline Completed without error 00% 9894 -
    Selective Self-tests/Logging not supported
    They are both SSD's, while the extra drive is a HDD. I don't think I've ever had an issue with the HDD showing up, so maybe this is an SSD-specific problem?

Maybe you are looking for