Bug 13469 - install attempt left virgin HD's Win8 partition in unusable state.
Summary: install attempt left virgin HD's Win8 partition in unusable state.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-01 21:18 CEST by Pierre Fortin
Modified: 2015-04-16 21:32 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Pierre Fortin 2014-06-01 21:18:43 CEST
Description of problem:

Installer clobbered, instead of resizing Win8 OS partition on a brand new machine (Dell Inspiron 17R 5737) starting with its /dev/sda thus:
 partition/size/type/label        
  sda1 500M vfat     ESP                        2048    1026047
  sda2  40M vfat     DIAGS                   1026048    1107967
  sda3 128M                                  1107968    1370111
  sda4 490M ntfs-3g  WINRETOOLS              1370112    2373631
  sda5 918G ntfs-3g  OS                      2373632 1927780351
  sda6  12G ntfs-3g  PBR_Image            1927780352 1953523119

After the attempted install of mga4 which failed due to bug 13461
   (VERSION: Mageia 4 Official-x86_64-Download 20140601 12:41)
   Install proceeded to point where I was able to resize main Windows 8
   partition #5 such that fdisk -l now reports:
  sda1  500M EFI System                          2048    1026047
  sda2   40M unknown                          1026048    1107967
  sda3  128M Microsoft reserved               1107968    1370111
  sda4  490M Windows recovery environment     1370112    2373631
  sda6 12.3G Windows recovery environment  1927780352 1953523119
  sda7   49G Linux filesystem               310669312  413427711
  sda8   16G Linux swap                     413427712  446908415
  sda9  706G Linux filesystem               446908416 1927780351

Note that sda5 is missing and so are blocks 2373632-310669311...

After working around several other install bugs, any attempt at booting this system ends in emergency mode complaining about "media-win_*", even after commenting out all those partitions in /etc/fstab:
$ cat /etc/fstab
# Entry for /dev/sda7 :
UUID=07bfada3-fbbf-4049-abd5-e97252288e4a / ext4 acl,noatime 1 1
# Entry for /dev/sda9 :
UUID=d65ac759-6ed7-4190-a834-795543a346b6 /home ext4 noatime,acl 1 2
# Entry for /dev/sda1 :
#UUID=CCB4-A236 /media/win_ vfat umask=0,iocharset=utf8 0 0
# Entry for /dev/sda2 :
#UUID=A835-A6DD /media/win_2 vfat umask=0,iocharset=utf8 0 0
# Entry for /dev/sda4 :
#UUID=B612378512374A1F /media/win_c ntfs-3g defaults 0 0
# Entry for /dev/sda6 :
UUID=B6C29D2FC29CF539 /media/win_d ntfs-3g defaults 0 0
## Entry for /dev/sdc2 :
#UUID=877dc6c1-6916-4494-8cb5-8ac3bdc34083 /mnt/hd ext4 noatime,acl 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda8 :
UUID=5c92fbea-904a-4c50-9a9a-1e0d8d55fe5d swap swap defaults 0 0



$ cat /proc/self/mounts
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,size=8155052k,nr_inodes=2038763,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
/dev/sda7 / ext4 rw,noatime,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
tmpfs /tmp tmpfs rw 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
/dev/sda9 /home ext4 rw,noatime,data=ordered 0 0

# this entry is how I copied above files over...
/dev/sdc1 /mnt/hd vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0



This occurred, IMO as a direct result of bug 13461 which was due to a bad MD5SUM file; now fixed.  I am NOT saying this partitioning error is fixed; only stating that bug 13461 was a trigger that resulted in this one.



Version-Release number of selected component (if applicable):


How reproducible:  no way to restore HD to factory state to determine.


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Thierry Vignaud 2015-04-16 21:32:11 CEST
We don't have any details, what was the partitionning choice, neither the drakx logs.
There's nothing we can do.

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.