Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 38

Thread: Cannot install Leap 42.1 after disk issues

  1. #21
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,802
    Blog Entries
    14

    Default Re: Cannot install Leap 42.1 after disk issues

    I should have been more precise, I meant "all partitions on the disk".
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  2. #22
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default Re: Cannot install Leap 42.1 after disk issues

    Quote Originally Posted by gogalthorp View Post
    Run smarctl against that disk to see how broken it is.

    Also this drive shows as sdG so are you sure you look at the right drive in the installer?????
    I can understand your question, but yes, it is /dev/sdg. I have a lot of disks in my Tumbleweed system, on which I hooked the faulty drive to analyze.

    When installing, the disk is hooked to the original system, which has only one disk, this one. But then I can't do analysis, of course.

    For as far as I can see, smartclt reveals no problems:

    Code:
    smartctl -a /dev/sdg
    smartctl 6.4 2016-01-06 r4199 [x86_64-linux-4.7.6-1-default] (SUSE RPM)
    Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Family:     Western Digital Green
    Device Model:     WDC WD10EZRX-00A8LB0
    Serial Number:    WD-WCC1U0227681
    LU WWN Device Id: 5 0014ee 207d3129f
    Firmware Version: 01.01A01
    User Capacity:    1,000,204,886,016 bytes [1,00 TB]
    Sector Sizes:     512 bytes logical, 4096 bytes physical
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ATA8-ACS (minor revision not indicated)
    SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
    Local Time is:    Sun Oct 16 19:30:43 2016 CEST
    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:  (0x82) Offline data collection activity
                                            was completed without error.
                                            Auto Offline Data Collection: Enabled.
    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:                (13200) seconds.
    Offline data collection
    capabilities:                    (0x7b) SMART execute Offline immediate.
                                            Auto Offline data collection on/off support.
                                            Suspend Offline collection upon new
                                            command.
                                            Offline surface scan supported.
                                            Self-test supported.
                                            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:        ( 151) minutes.
    Conveyance self-test routine
    recommended polling time:        (   5) minutes.
    SCT capabilities:              (0x30b5) SCT Status 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     0x002f   200   200   051    Pre-fail  Always       -       0
      3 Spin_Up_Time            0x0027   139   128   021    Pre-fail  Always       -       4025
      4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       411
      5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
      9 Power_On_Hours          0x0032   069   069   000    Old_age   Always       -       23134
     10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
     11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       411
    192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       444
    193 Load_Cycle_Count        0x0032   131   131   000    Old_age   Always       -       207178
    194 Temperature_Celsius     0x0022   115   103   000    Old_age   Always       -       28
    196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
    197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
    198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
    199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
    200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0
    
    SMART Error Log Version: 1
    No Errors Logged
    
    SMART Self-test log structure revision number 1
    No self-tests have been logged.  [To run self-tests, use: smartctl -t]
    
    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.

  3. #23
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default Re: Cannot install Leap 42.1 after disk issues

    Quote Originally Posted by Knurpht View Post
    I should have been more precise, I meant "all partitions on the disk".
    Well, I should have known that filesystemcheck means file system check....
    Last edited by jehojakim; 17-Oct-2016 at 06:17. Reason: typo

  4. #24
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default Re: Cannot install Leap 42.1 after disk issues

    Quote Originally Posted by Knurpht View Post
    Visible in GRUB.
    According to the grup-files on the installation media (which is the standard opensuse distro Leap 42.1) it boots in efi-mode.

  5. #25
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default Re: Cannot install Leap 42.1 after disk issues

    Hi @knurpht and @gogalthorp,

    I'm afraid I'll have to re-install the system somehow soon today, because my friend cannot do without it any longer.

    On one question I posed in this thread I've got no answer for as far as I can see:
    would is be wise to let gdisk write a partition scheme to the disk? Would that be anything better than what's apparently now on the disk?

    Otherwise I'll have to let the installer repartition the disk, deleting the partitions it now sees, and create new ones.
    After that I can restore the user data from the backup.

    But then we won't know what causes the different visions on the disk partitioning by the 42.1 installer, and by hooking it to a Tumbleweed system.
    Where the last one is correct, and 42.1 is faulty.

    Thanks a lot for thinking with me so far!

  6. #26
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,703

    Default Re: Cannot install Leap 42.1 after disk issues

    If efi boot there must be a small FAT format partition for the efi boot files. not so for MBR boot

    Your gdisk and fdisk output shows DOS partitioning and no indication of EFI boot or GPT partition tables. I suspect that you booted the install in EFI mode and the installer wanted to change things to EFI set up.

    Be sure to boot installer in legacy mode grub should be set to grub2 not grub2-efi for a legacy set up.

    In any case you can always override the installers recommendation if it does not fit the situation.

    Also be sure you select upgrade even if same version or the installer will want to install a second OS not change the existing

  7. #27
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default Re: Cannot install Leap 42.1 after disk issues

    To be honest, I have no idea how to change the boot procedure to legacy mode.
    If I look at the contents of the install scripts on the USB-stick for 42.1, I only see grub-efi, no grub-2 whatsoever.

    Next thing I'll do is try to install 13.2, hoping that that uses grub2, and recognizes the disk properly.

    Rather off topic, but why doesn't the installer look at the disk, see if it's EFI or not, and start the install procedure accordingly?
    During install, maybe (but I have no knowledge here) the partitioning could bee transferred to EFI, without touching user data.

  8. #28
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,670
    Blog Entries
    15

    Default Re: Cannot install Leap 42.1 after disk issues

    Quote Originally Posted by jehojakim View Post
    To be honest, I have no idea how to change the boot procedure to legacy mode.
    If I look at the contents of the install scripts on the USB-stick for 42.1, I only see grub-efi, no grub-2 whatsoever.

    Next thing I'll do is try to install 13.2, hoping that that uses grub2, and recognizes the disk properly.

    Rather off topic, but why doesn't the installer look at the disk, see if it's EFI or not, and start the install procedure accordingly?
    During install, maybe (but I have no knowledge here) the partitioning could bee transferred to EFI, without touching user data.
    Hi
    The installer does know whether to boot in Legacy or UEFI, it checks your system BIOS, so you need to check via perssing F2, esc key, F12 or whatever is required on the system to check. If you boot into rescue mode from the install medium and login (root is the user, no password) and run the command efibootmgr if that works then it's booted in UEFI mode.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  9. #29
    Join Date
    Jun 2008
    Location
    Akkrum, Netherlands
    Posts
    139

    Default Re: Cannot install Leap 42.1 after disk issues

    It's in EFI-mode (bios had "EFI and Legacy" selected) and installer).
    I can change bios to Legacy only, but then it does not see the installer stick anymore.

    13.2 boots also in EFI-mode, so I'll have to go to even older versions I think.

  10. #30
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,670
    Blog Entries
    15

    Default Re: Cannot install Leap 42.1 after disk issues

    Quote Originally Posted by jehojakim View Post
    It's in EFI-mode (bios had "EFI and Legacy" selected) and installer).
    I can change bios to Legacy only, but then it does not see the installer stick anymore.

    13.2 boots also in EFI-mode, so I'll have to go to even older versions I think.
    Hi
    I wopuld stick with EFI, boot into rescue mode and I think you will find a small partition set to type ef00;
    Code:
    lsblk
    gdisk -l /dev/sda
    It won't work if the disk is gpt (Unless it's configured as hybrid mbr maybe)

    For example here is one of my systems (openSUSE 42.1 tvheadend server);

    Code:
    efibootmgr 
    
    BootCurrent: 0000
    Timeout: 2 seconds
    BootOrder: 0000,3000,0002,2001,2002,2003
    Boot0000* opensuse-secureboot
    Boot0002* EFI HDD Device (TOSHIBA MK1637GSX)
    Boot2001* USB Drive (UEFI)
    Boot3000* Internal Hard Disk or Solid State Disk
    Boot3001* Internal Hard Disk or Solid State Disk
    Boot3002* Internal Hard Disk or Solid State Disk
    Boot3003* Internal Hard Disk or Solid State Disk
    
    lsblk
    
    NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    sda      8:0    0 149.1G  0 disk 
    ├─sda1   8:1    0   260M  0 part /boot/efi
    ├─sda2   8:2    0     2G  0 part [SWAP]
    ├─sda3   8:3    0    40G  0 part /
    └─sda4   8:4    0 106.8G  0 part /home
    
    gdisk -l /dev/sda
    
    GPT fdisk (gdisk) version 0.8.8
    
    Partition table scan:
      MBR: protective
      BSD: not present
      APM: not present
      GPT: present
    
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sda: 312581808 sectors, 149.1 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): DAECF3FC-A514-46F2-879A-9210E3FA972A
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 312581774
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2016 sectors (1008.0 KiB)
    
    Number  Start (sector)    End (sector)  Size       Code  Name
       1            2048          534527   260.0 MiB   EF00  EFI System
       2          534528         4728831   2.0 GiB     8200  Linux swap
       3         4728832        88614911   40.0 GiB    8300  Linux filesystem
       4        88614912       312581772   106.8 GiB   8300  Linux filesystem
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

Page 3 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •