openSUSE 13.1 installation - Thumb Drive Installation and Hard disk partition issue

English Install/Boot/Login
#1

Hello,

I hope somebody can assist me in this thumb drive, partitioning issues for the installation of openSUSE 13.1.

I have been trying to install openSUSE 13.1 for the past few days(4 I think) into its own hard disk, one for Windows and one for openSUSE (500GB), and have just succeeded but ran into partitioning issue. My system as follows:-

Processor: AMD A10-5800K APU with Radeon HD Graphics 3.8GHz
RAM : 8GB
System : 64-bit OS, x64-based processor.
Motherboard: GIGA F2A85X-D3H (With EFI / Legacy BIOS)
Current OS : Windows 8.1

I down loaded the openSUSE13.1 dvd iso and burn to dvd using image burn software but I believed that the dvd is corrupted as the checksum does not match that of the iso image thus the install was not successful. I tried with unetbootin to create a bootable thumb drive, not successful. Finally tried with imagewriter, created a bootable thumb drive and manage to install openSUSE 13.1 and this is where the partition(default partition by the installer) issue crop up:-

**Device Size F Enc Type FS Type Label Mount Point Start End
/dev/sda 465.76GB WDC-WD50000AAKX-0 0 60800
/dev/sda1 7.00GB Linux swap Swap Swap 0 914
/dev/sda2 10.00GB Linux native Ext4 914 2218
/dev/sda3 438.76GB Linux native Ext4 3525 60800
/dev/sda4 157.00MB EFI boot FAT /boot/efi 2218 2238
/dev/sda5 5.00GB Linux native Ext4 / 2238 2892
/dev/sda6 4.85GB Linux native Ext4 /home 2892 3525
/dev/sdb 7.21GB USB FLASH DRIVE 0 7387
/dev/sdb1 4.00MB EFI(FAT-12/16) FAT BOOT 1 5
/dev/sdb2 4.25GB Hidden HPFS/NTFS 5 4360
**
Note that the thumb drive, /dev/sdb, became part of the system, thus I cannot boot up openSUSE without the thumb drive.

Any assistant on the following is greatly appreciated:-

  1. How to setup/edit the partitions during the installation? What partition do I need? Do I need 100GB or more for the ‘/’ partition as I believe this is where any program installed is where the files are loaded/written. The 5GB was all used up and now I can’t boot up the system any more.

  2. Do I need to install openSUSE 13.1 with /boot/EFI partition or without? Which is better? Or is openSUSE the next upgrade will only have EFI boot?( I think if I boot in Legacy mode the installation will be without the /boot/EFI partition. I am getting the /boot/EFI is because I booted the installation thumb drive using the EFI mode via the bios, I think )

OR

  1. How to install openSUSE 13.1 by using a bootable thumb drive without the thumb drive becoming part of the system…not so sure about the default hard disk partition going to be though…

Thank you.

#2

No, I don’t see that. Rather, I see that it is listed as a disk with partitions, but not assigned to any use.
I am seeing, from your output:


/dev/sda5     5G  ext4      mounted as /
/dev/sda4   157M  fat       mounted as /boot/efi
/dev/sda1     7G   swap     used as swap
/dev/sda6   4.8G  ext4      mounted as /home

and the other partitions are not assigned for this install.

#3

It is unclear if that list is the proposed partitioning or if you accepted this and instilled in which case Windows is gone. If you planned to dual boot you need to start over installing Windows first. If it is the proposed scheme then do not accept it The partitioning indicated is totally wrong adn in any case needs to be redone.

What you need:
You need a swap partition 1-2 X memory (do you hibernate or plan to. that makes a difference) If you plan to hibernate you want at least swap = memeory
You need root (mounted as /) 15-40 gig. depends on how much huge software you plan to install and also if you use BTRFS file system or not

Optional by highly recommended home mounted as /home. This is where you will store all your personal data and configuration. How much depends on how much you intend to store in Linux or the space available. Note that if you do not define a home partition then /home will be on the root partition so you need to increase the size of root for your anticipated usage.

Just because you see the USB thumb in the list of partitions does not mean it will be mounted or used. It all depends on if you define a mount point for it which you should not.

Just be sure that any of the new partitions live on the hard drive and not installed back to the USB. Just pay attention.

If you have managed to do the above and mount the USB partition then you will have to remove it from the boot list. You can (as root see below*) edit the file /etc/fstab and remove the line pointing to the USB But before removing the line note where it is mounted. If it an important directory you need to check. If you are unsure check here first.

  • become root.
    Open a console window (exact name depends on which desktop) type
    su -
    Note minus
    enter root password at prompt. not the password does no echo to the screen so you must type this blind
    you are now root
    joe /etc/fstab

note joe is a simple text editor and should be installed by default

#4

I have a 500GB hd for windows and I intend to install openSUSE 13.1 into another 500GB hd by itself.

What I’ve typed is as per what was shown on installation screen(don’t know how to insert a pic here), nrickert, there are some sda that have no Mount Point…hmmm, maybe should have taken the picture after this before it went into installation process.

No, gogalthorp, I don’t plan for hibernation or suspend state, so I’ll just use the default swap partition. Will pay attention to the thumb drive.

Will do another installation with the following partitioning all linux partition using Ext4:-

sda1 2.0GB(default I think) swap
sda2 250GB(root) /
sda3 157MB(FAT) /boot/efi
sda4 248GB(balance) /home

Is there anything that I missed? Oh, is there any significant to the numbering-to-Mount Point of the sda? E.g. sda6 must be /home or sda4 must be /boot/efi?

Where does the installation of programs goes? This has always confuse me, the root partition or the home partition?
gogalthorp, you state that ‘… /home. This is where you will store all your personal data and configuration.’ Does this means that whatever program that I install will go to the /home partition as defined and not to the root partition?

Will do a update after the installation(6th). Now I have to unplug my windows hd…

#5

The numbering is not significant.

Unless you have unusual needs, 250G for “/” is way too much.

Depending on the BIOS, you might do better to use the same EFI partition as Windows. Just make sure that the install won’t format it.

Typically, software in installed in the root partition. If it is not from the opensuse repos, then the most usual places to install are under “/usr/local” or under “/opt”. If you plan on a lot of such software, you might prefer a separate
partition for either “/usr/local” or “/opt” (or both).

#6

Update on the installation(EFI mode).

  1. Installation with the mentioned partition in my earlier post (sda1 - sda4) - Fail. The system reboots and the progress bar goes until about 80% done then starts again, then round and round it goes. Had to use the ‘on’ button on my computer to stop it.

  2. Tried again but using the default partition by the installer. However got some additional choices when booting up(boot up without the USB) and the USB installer became part of the system.

  • The booting screen have 4 choices: a) openSUSE 13.1 b) Advanced options for openSUSE 13.1 c) openSUSE 13.1 (x86_64) (on /dev/sda3/) d) Advanced options for openSUSE 13.1 (x86_64) (on/dev/…the last part is off screen.

  • When I did an update without the USB plugged in, the response:-**
    Empty destination in URIO hd:///?devic=/dev/disk/by-id/scsi-1USB_DISK_2.0-part2**
    Abort, retry, ignore?..so on and so forth.

- fstab
/dev/disk/by-id/ata-WDC_WD5000AAKX-001CA0_WD-WMAYUD936016-part1 swap
swap defaults 0 0

/dev/disk/by-id/ata-WDC_WD5000AAKX-001CA0_WD-WMAYUD936016-part1 swap
ext4 acl,user_xattr 1 1

/dev/disk/by-id/ata-WDC_WD5000AAKX-001CA0_WD-WMAYUD936016-part1 swap
vfat umask=0002, utf8=true 0 0

/dev/disk/by-id/ata-WDC_WD5000AAKX-001CA0_WD-WMAYUD936016-part1 swap
ext4 acl, user_xattr 1 2

The partition as follows:-

/dev/sda 465.76GB WDC-WD50000AAKX-0
/dev/sda1 8.00GB Linux swap FS Type Swap Mount Point swap
/dev/sda2 157.00MB Win95 FAT32 LBA FS Type FAT Mount Point
/dev/sda3 200.00GB Linux native FS Type Ext4 Mount Point
/dev/sda4 164.00MB EFI boot FS Type FAT Mount Point /boot/efi
/dev/sda5 20.00GB Linux native FS Type Ext4 Mount Point /
/dev/sda6 237.45GB Linux native FS Type Ext4 Mount Point /home

Display from terminal command df -h:-

**Filesystem Size Used Avail Use% Mounted on
/dev/sda5 20G 4.8G 14G 26% /
devtmpfs 3.5G 32K 3.5G 1% /dev
tmpfs 3.5G 84K 3.5G 1% /dev/shm
tmpfs 3.5G 4.6M 3.5G 1% /run
tmpfs 3.5G 0 3.5G 0% /sys/fs/cgroup
tmpfs 3.5G 4.6M 3.5G 1% /var/run
tmpfs 3.5G 4.6M 3.5G 1% /var/lock
/dev/sda4 164M 128K 164M 1% /boot/efi
/dev/sda6 234G 106M 233G 1% /home
**

I wonder why the other sda (1, 2 and 3) are not shown? However note that /dev/sda5, the root partition. I think that whatever update or program that I install will be witten there, thus this current installation will not last long.

I still have no idea what I did incorrect during the installation or there might be something wrong with my bootable USB. But checksum for the openSUSE 13.1 DVD iso is correct, sha1 and md5.

Will try one or twice more to install openSUSE 13.1 before calling it a day…hoping to use this as my alternative desktop system from windows.

#7

This is not actually a serious problem.

Simply fire up Yast Software Repositories, and remove the “enable” check from the repo that begins “hd:///”.

I usually leave it enabled for a short while, while adding some more software from online. Once I have a near-final set of installed software, I disable the USB repo.

#8

Finally got openSUSE installed and running but run into this:-

Configuration file “/home/law/.kde4/share/config/kdesurc” not writable.
Please contact your system administrator.

Configuration file “/home/law/.kde4/share/config/klipperrc” not writable.
Please contact your system administrator.

Configuration file “/home/law/.kde4/share/config/kmixrc” not writable.
Please contact your system administrator.

Configuration file “/home/law/.kde4/share/config/nepomekstoragerc” not writable.
Please contact your system administrator.

Configuration file “/home/law/.kde4/share/config/krunnerrc” not writable.
Please contact your system administrator.

I did a search and found that ‘KDE programmes are not designed to run as root’? Anyway I tried "sudo chmod law,law /home/law/.kde4/" but it returned **chown: changing ownership of **** ‘/home/law/.kde4/’ : Read-only file system
**
Any advise please.

#9

Of course you can run KDE programs as root. Whether that’s advisable or not is a different question of course.
But in your case they try to access /home/law/.kde4/, so they are in fact not running as root, but as user “law”.

If you’re logged in as root, they should use /root/… instead, which normally is on the / partition, even if you have a separate /home.
So maybe try to log in as root to be able to fix your system.

Anyway I tried "sudo chmod law,law /home/law/.kde4/" but it returned **chown: changing ownership of ****’/home/law/.kde4/’ : Read-only file system
**

Well, the message says it all, doesn’t it?
Your /home partition is mounted read-only apparently.

Please post your /etc/fstab and the output of “mount”.

#10

The requested information:-

/etc/fstab

/dev/disk/by-id/ata-WDC_WD5000AAKX-001CA0_WD-WMAYUD936016-part2 swap            
     swap       defaults              0 0
/dev/disk/by-id/ata-WDC_WD5000AAKX-001CA0_WD-WMAYUD936016-part3 /               
     ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-WDC_WD5000AAKX-001CA0_WD-WMAYUD936016-part1 /boot/efi       
     vfat       umask=0002,utf8=true  0 0
/dev/disk/by-id/ata-WDC_WD5000AAKX-001CA0_WD-WMAYUD936016-part6 /home           
     ext4       acl,user_xattr        1 2

output of ‘mount’

linux-0mi4:/dev # mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=3634864k,nr_inodes=908716,mode=755)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sda3 on / type ext4 (rw,relatime,data=ordered)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/sda6 on /home type ext4 (ro,relatime,data=ordered)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
gvfsd-fuse on /var/run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
#11

Well, it is indeed mounted read-only (“ro”).
Your fstab looks ok, so apparently there’s an error when trying to mount it read-write.

Try to run fsck on it to check/fix the filesystem.

Try to remount it read-write before you login as user:

sudo mount /home -o rw,remount

Maybe this will give more hints to what’s wrong.

And probably this would contain a clue as well:

sudo systemctl status /home
#12

I did the following(logged in as root, console):-

unmounted sda6

umount -l '/dev/sda6'

then

linux-0mi4:~ # mount /home -o rw,remount
mount: /home not mounted or bad option

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

then

linux-0mi4:~ # dmesg | tail
[14259.297757] sd 2:0:0:0: [sda]  
[14259.297761] Add. Sense: Unrecovered read error - auto reallocate failed
[14259.297764] sd 2:0:0:0: [sda] CDB: 
[14259.297766] Read(10): 28 00 0a 09 d5 e8 00 00 08 00
[14259.297777] end_request: I/O error, dev sda, sector 168416746
[14259.297818] ata3: EH complete
[14330.696988] ISO 9660 Extensions: Microsoft Joliet Level 3
[14330.701235] ISO 9660 Extensions: RRIP_1991A
[14545.497129] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[14545.497132] EDD information not available.

then

linux-0mi4:~ # mount -rw /dev/sda6 /home
mount: /dev/sda6 is already mounted or /home busy

then

linux-0mi4:~ # df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda3       198G  4.7G  193G   3% /
devtmpfs        3.5G   32K  3.5G   1% /dev
tmpfs           3.5G     0  3.5G   0% /dev/shm
tmpfs           3.5G  4.8M  3.5G   1% /run
tmpfs           3.5G     0  3.5G   0% /sys/fs/cgroup
tmpfs           3.5G  4.8M  3.5G   1% /var/run
tmpfs           3.5G  4.8M  3.5G   1% /var/lock
/dev/sda1       156M  128K  156M   1% /boot/efi

then

linux-0mi4:~ # mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=3634864k,nr_inodes=908716,mode=755)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sda3 on / type ext4 (rw,relatime,data=ordered)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
gvfsd-fuse on /run/user/0/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
gvfsd-fuse on /var/run/user/0/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0)

My /dev/sda6 /home partition seems to be…nowhere…

#13

Well, the option “remount” only works if it is mounted already (hence the name). The point of that option is to change the mount options without having to unmount it first.
So either do not unmount it, or omit the “remount” option.

linux-0mi4:~ # dmesg | tail
[14259.297757] sd 2:0:0:0: [sda]  
[14259.297761] Add. Sense: Unrecovered read error - auto reallocate failed

That doesn’t look good. Apparently your disk has bad sectors and no spare place to reallocate them any more.
IOW, your hard disk is dying. Make a backup of your important data immediately!

Then replace it.
Or have a look at the SMART data and decide yourself whether it’s worth the risk to continue using it:

sudo /usr/sbin/smartctl -a /dev/sda

then

linux-0mi4:~ # mount -rw /dev/sda6 /home
mount: /dev/sda6 is already mounted or /home busy

“-rw” should not be necessary because “rw” is the default anyway.

Apparently something is still using /home. Were you logged in at user before? Or did you login as root immediately after boot?

You could use lsof to find out what is using /home, and maybe kill it:

lsof | grep /home
#14

The system crashed not long after my last reply and I reinstalled, again the 14th ant 15th time. The first install fail, same thing again the /dev/sda6 /home read-only so I reinstalled again.

The second installation first round, it was fine, the /dev/sda6 /home was read-write, everything looks good then after Apper updated the system, reboot the problem came back, I rebooted the system and now it is working fine. Go figure.

Any thank you all, wolfi323, for sticking with me and your advise. Learn a few new items.

Hopefully this install is stable.

#15

Did you perhaps use a Windows formatted partition as home that would explain the R/O status???

You can not use any Windows formatted partition as home

#16

The /boot/efi partition is FAT format, the rest are Ext4.

#17

Not sure how you managed R/O then by default NTFS is mounted R/O

#18

I suspect the bootable thumb drive.

Initially I burned the openSUSE 13.1 DVD x86_64.iso to a blank DVD using imageburn software but installation failed possibly due to padding by the software itself, the md5 checksum was different from that of the iso image, thus I suspect the bootable thumb drive too might have some problem or possibly the ‘new’ systemd way of handling the partitioning. Whatever it is, it is all guesses, I guess. :slight_smile:

#19

Hmmm When I installed 12.3 from a USB I noticed that the installer wanted to install to the thumb becuse I assume it was set as boot and looked like a real drive not a DVD. So I had to manually change that. It is always good to double check the partition scheme and not assume that the installer can read your mind LOL

#20

That’s not quite true.
NTFS partitions are in fact mounted read-write, but with YaST’s default mount options only root has write access, i.e. the files/directories are owned by root and have rw-r–r-- permissions. NTFS doesn’t support Linux file permissions of course, so they are determined by the mount options.

In the OP’s case, the filesystem itself is mounted read-only.
As there is no “ro” in the fstab, this is most likely caused by errors on the disk. The system remounts a filesystem read-only when read/write errors occur.
See “man mount”:

       **errors**={**continue**|**remount-ro**|**panic**}
              Define the behaviour when an error is encountered.  (Either  ignore
              errors  and  just  mark  the  filesystem erroneous and continue, or
              remount the filesystem read-only, or panic and  halt  the  system.)
              The default is set in the filesystem superblock, and can be changed
              using **tune2fs**(8).

I think the default when creating a new filesystem is “remount-ro”.

As a workaround, you could try to add the mount option “errors=continue”, but if the disk is bad you will get problems and lose data even then.

But again, I would really recommend you make a backup of important data and check the state of the drive.
If in doubt, post the output of “sudo /usr/sbin/smartctl -a /dev/sda”.