LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
Reload this Page using LiveUSB to detect partitions. no luck, need help
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 12-14-2014, 02:07 PM   #1
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
using LiveUSB to detect partitions. no luck, need help

My system, 100% my fault, has some encrypted partitions that ive lost the password to. i am attempting to use the CentOS v7 LiveUSB as that is the OS running on the system to detect the partitions that are encrypted so that I can reformat them, re-add them to the fstab and thus get the server to boot without loosing data on the unencrypted partitions.

it is using the xfs file system as well as software raid6. running fdisk does not seem to provide me with the data i require. in need of further guidance. many thanks in advance:

Code:
[root@localhost ~]# fdisk -l

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sde: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1   *           1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sda: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *           1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1   *           1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sdg: 8103 MB, 8103395328 bytes, 15826944 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00012f08

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1   *        2048    15822847     7910400   83  Linux

Disk /dev/mapper/live-rw: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/live-base: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/live-osimg-min: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
all i can gleam from this is that /dev/sdg is the liveUSB im running from and that all of the others are only displaying a single partition. I know that to not be true as there is at least / /boot /home /exports /swap in the raid.

i know 100% that swap and /home are encrypted im hoping i didnt encrypt / as well. /exports is not encrypted and that is the data i do not want to destroy. to much data to recover at about 11TB worth of media files.
 
Old 12-14-2014, 02:13 PM   #2
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
additional information to add: sfdisk -l provides a bit more information, but concerns me is that it is showing 0 size for the extra partitions:

Code:
[root@localhost ~]# sfdisk -l

Disk /dev/sdc: 364801 cylinders, 255 heads, 63 sectors/track
Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdc1   *      0+ 267349- 267350- 2147483647+  ee  GPT
sfdisk: 		start: (c,h,s) expected (0,0,2) found (0,0,1)

/dev/sdc2          0       -       0          0    0  Empty
/dev/sdc3          0       -       0          0    0  Empty
/dev/sdc4          0       -       0          0    0  Empty

Disk /dev/sde: 364801 cylinders, 255 heads, 63 sectors/track
Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sde1   *      0+ 267349- 267350- 2147483647+  ee  GPT
sfdisk: 		start: (c,h,s) expected (0,0,2) found (0,0,1)

/dev/sde2          0       -       0          0    0  Empty
/dev/sde3          0       -       0          0    0  Empty
/dev/sde4          0       -       0          0    0  Empty

Disk /dev/sda: 364801 cylinders, 255 heads, 63 sectors/track
Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sda1   *      0+ 267349- 267350- 2147483647+  ee  GPT
sfdisk: 		start: (c,h,s) expected (0,0,2) found (0,0,1)

/dev/sda2          0       -       0          0    0  Empty
/dev/sda3          0       -       0          0    0  Empty
/dev/sda4          0       -       0          0    0  Empty

Disk /dev/sdf: 364801 cylinders, 255 heads, 63 sectors/track
Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdf1   *      0+ 267349- 267350- 2147483647+  ee  GPT
sfdisk: 		start: (c,h,s) expected (0,0,2) found (0,0,1)

/dev/sdf2          0       -       0          0    0  Empty
/dev/sdf3          0       -       0          0    0  Empty
/dev/sdf4          0       -       0          0    0  Empty

Disk /dev/sdb: 364801 cylinders, 255 heads, 63 sectors/track
Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdb1   *      0+ 267349- 267350- 2147483647+  ee  GPT
sfdisk: 		start: (c,h,s) expected (0,0,2) found (0,0,1)

/dev/sdb2          0       -       0          0    0  Empty
/dev/sdb3          0       -       0          0    0  Empty
/dev/sdb4          0       -       0          0    0  Empty

Disk /dev/sdd: 364801 cylinders, 255 heads, 63 sectors/track
Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdd1   *      0+ 267349- 267350- 2147483647+  ee  GPT
sfdisk: 		start: (c,h,s) expected (0,0,2) found (0,0,1)

/dev/sdd2          0       -       0          0    0  Empty
/dev/sdd3          0       -       0          0    0  Empty
/dev/sdd4          0       -       0          0    0  Empty

Disk /dev/sdg: 1021 cylinders, 250 heads, 62 sectors/track
sfdisk: Warning: The partition table looks like it was made
  for C/H/S=*/237/20 (instead of 1021/250/62).
For this listing I'll assume that geometry.

Units: cylinders of 2426880 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdg1   *      0+   3338-   3338-   7910400   83  Linux
sfdisk: 		start: (c,h,s) expected (0,102,9) found (0,32,33)

sfdisk: 		end: (c,h,s) expected (1023,236,20) found (984,236,20)

/dev/sdg2          0       -       0          0    0  Empty
/dev/sdg3          0       -       0          0    0  Empty
/dev/sdg4          0       -       0          0    0  Empty

Disk /dev/mapper/live-rw: 1044 cylinders, 255 heads, 63 sectors/track

Disk /dev/mapper/live-base: 1044 cylinders, 255 heads, 63 sectors/track

Disk /dev/mapper/live-osimg-min: 1044 cylinders, 255 heads, 63 sectors/track
i hope that helps you help me.
 
Old 12-14-2014, 02:19 PM   #3
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
finding more good news, still at a bit of a loss, but slowly getting there i hope:

Code:
[root@localhost ~]# mdadm --examine --scan /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4
ARRAY /dev/md/exports  metadata=1.2 UUID=2cbe871c:7f44d2ac:0b152090:ef209fcf name=exports
ARRAY /dev/md/swap  metadata=1.2 UUID=f26a5a28:42b8611f:b4938ebb:8f7c017e name=jackknife.ssmahome.local:swap
ARRAY /dev/md/root  metadata=1.2 UUID=9169cd8d:f746698e:5a163032:70fe5f84 name=jackknife.ssmahome.local:root
ARRAY /dev/md/home  metadata=1.2 UUID=dc3e1a5b:434e5e46:18f84041:8d2a7542 name=jackknife.ssmahome.local:home
from this link: http://www.linuxjournal.com/article/8874?page=0,1

it should be showing the raid level, but im not seeing that. im hoping that the document is just to old to count both raid6 and xfs file systems as it is from 2009.

the good news is my partitions are there, now to figure out how to gain access to them.
 
Old 12-14-2014, 02:41 PM   #4
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
found more info that might help some of you help me:

Code:
(parted) print                                                            
Model: ATA WDC WD30EZRX-00D (scsi)
Disk /dev/sda: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: pmbr_boot

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  134GB   134GB                      raid
 2      134GB   147GB   13.1GB                     raid
 3      147GB   150GB   2098MB                     raid
 4      150GB   3000GB  2850GB                     raid

(parted) quit                                                             
[root@localhost ~]# mdadm --examine --scan /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4
ARRAY /dev/md/exports  metadata=1.2 UUID=2cbe871c:7f44d2ac:0b152090:ef209fcf name=exports
ARRAY /dev/md/swap  metadata=1.2 UUID=f26a5a28:42b8611f:b4938ebb:8f7c017e name=jackknife.ssmahome.local:swap
ARRAY /dev/md/root  metadata=1.2 UUID=9169cd8d:f746698e:5a163032:70fe5f84 name=jackknife.ssmahome.local:root
ARRAY /dev/md/home  metadata=1.2 UUID=dc3e1a5b:434e5e46:18f84041:8d2a7542 name=jackknife.ssmahome.local:home
[root@localhost ~]# mdadm --examine --scan /dev/sda1
ARRAY /dev/md/home  metadata=1.2 UUID=dc3e1a5b:434e5e46:18f84041:8d2a7542 name=jackknife.ssmahome.local:home
[root@localhost ~]# mdadm --examine --scan /dev/sda2
ARRAY /dev/md/root  metadata=1.2 UUID=9169cd8d:f746698e:5a163032:70fe5f84 name=jackknife.ssmahome.local:root
[root@localhost ~]# mdadm --examine --scan /dev/sda3
ARRAY /dev/md/swap  metadata=1.2 UUID=f26a5a28:42b8611f:b4938ebb:8f7c017e name=jackknife.ssmahome.local:swap
[root@localhost ~]# mdadm --examine --scan /dev/sda4
ARRAY /dev/md/exports  metadata=1.2 UUID=2cbe871c:7f44d2ac:0b152090:ef209fcf name=exports
this indicates that the link above is just out of data and the mdadm command no longer is capable of detecting the raid level of a xfs file system, if it ever was.
 
Old 12-14-2014, 03:01 PM   #5
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
is this going to be a problem???

Code:
[root@localhost ~]# mdadm --examine --scan /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4 /dev/sdc1 /dev/sdc2 /dev/sdc3 /dev/sdc4 /dev/sdd1 /dev/sdd2 /dev/sdd3 /dev/sdd4 /dev/sde1 /dev/sde2 /dev/sde3 /dev/sde4 /dev/sdf1 /dev/sdf2 /dev/sdf3 /dev/sdf4
ARRAY /dev/md/exports  metadata=1.2 UUID=2cbe871c:7f44d2ac:0b152090:ef209fcf name=exports
ARRAY /dev/md/swap  metadata=1.2 UUID=f26a5a28:42b8611f:b4938ebb:8f7c017e name=jackknife.ssmahome.local:swap
ARRAY /dev/md/root  metadata=1.2 UUID=9169cd8d:f746698e:5a163032:70fe5f84 name=jackknife.ssmahome.local:root
ARRAY /dev/md/home  metadata=1.2 UUID=dc3e1a5b:434e5e46:18f84041:8d2a7542 name=jackknife.ssmahome.local:home
[root@localhost ~]# mdadm --examine --scan /dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4 
ARRAY /dev/md/exports  metadata=1.2 UUID=2cbe871c:7f44d2ac:0b152090:ef209fcf name=exports
ARRAY /dev/md/swap  metadata=1.2 UUID=f26a5a28:42b8611f:b4938ebb:8f7c017e name=jackknife.ssmahome.local:swap
ARRAY /dev/md/root  metadata=1.2 UUID=9169cd8d:f746698e:5a163032:70fe5f84 name=jackknife.ssmahome.local:root
ARRAY /dev/md/home  metadata=1.2 UUID=dc3e1a5b:434e5e46:18f84041:8d2a7542 name=jackknife.ssmahome.local:home
[root@localhost ~]# mdadm --examine --scan /dev/sdc1 /dev/sdc2 /dev/sdc3 /dev/sdc4
ARRAY /dev/md/exports  metadata=1.2 UUID=2cbe871c:7f44d2ac:0b152090:ef209fcf name=exports
ARRAY /dev/md/swap  metadata=1.2 UUID=f26a5a28:42b8611f:b4938ebb:8f7c017e name=jackknife.ssmahome.local:swap
ARRAY /dev/md/root  metadata=1.2 UUID=9169cd8d:f746698e:5a163032:70fe5f84 name=jackknife.ssmahome.local:root
ARRAY /dev/md/home  metadata=1.2 UUID=dc3e1a5b:434e5e46:18f84041:8d2a7542 name=jackknife.ssmahome.local:home
[root@localhost ~]# mdadm --examine --scan /dev/sdd1 /dev/sdd2 /dev/sdd3 /dev/sdd4
ARRAY /dev/md/exports  metadata=1.2 UUID=2cbe871c:7f44d2ac:0b152090:ef209fcf name=exports
ARRAY /dev/md/swap  metadata=1.2 UUID=f26a5a28:42b8611f:b4938ebb:8f7c017e name=jackknife.ssmahome.local:swap
ARRAY /dev/md/root  metadata=1.2 UUID=9169cd8d:f746698e:5a163032:70fe5f84 name=jackknife.ssmahome.local:root
ARRAY /dev/md/home  metadata=1.2 UUID=dc3e1a5b:434e5e46:18f84041:8d2a7542 name=jackknife.ssmahome.local:home
[root@localhost ~]# mdadm --examine --scan /dev/sde1 /dev/sde2 /dev/sde3 /dev/sde4
ARRAY /dev/md/root  metadata=1.2 UUID=9169cd8d:f746698e:5a163032:70fe5f84 name=jackknife.ssmahome.local:root
ARRAY /dev/md/home  metadata=1.2 UUID=dc3e1a5b:434e5e46:18f84041:8d2a7542 name=jackknife.ssmahome.local:home
[root@localhost ~]# mdadm --examine --scan /dev/sdf1 /dev/sdf2 /dev/sdf3 /dev/sdf4
ARRAY /dev/md/exports  metadata=1.2 UUID=2cbe871c:7f44d2ac:0b152090:ef209fcf name=exports
ARRAY /dev/md/swap  metadata=1.2 UUID=f26a5a28:42b8611f:b4938ebb:8f7c017e name=jackknife.ssmahome.local:swap
ARRAY /dev/md/root  metadata=1.2 UUID=9169cd8d:f746698e:5a163032:70fe5f84 name=jackknife.ssmahome.local:root
ARRAY /dev/md/home  metadata=1.2 UUID=dc3e1a5b:434e5e46:18f84041:8d2a7542 name=jackknife.ssmahome.local:home
[root@localhost ~]# mdadm --assemble --scan
mdadm: /dev/md/exports_1 assembled from 2 drives - not enough to start the array.
mdadm: /dev/md/jackknife.ssmahome.local:swap_0 assembled from 2 drives - not enough to start the array.
mdadm: /dev/md/jackknife.ssmahome.local:root_0 assembled from 2 drives - not enough to start the array.
mdadm: /dev/md/jackknife.ssmahome.local:home_0 assembled from 2 drives - not enough to start the array.
mdadm: No arrays found in config file or automatically
all 6 of the drives are detected, all 6 show the exact same partitions with the exact same UUID and name. this is good, i hope.

why is mdadm --assemble --scan only trying to use 2 disks instead of all 6?
 
Old 12-14-2014, 03:47 PM   #6
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
how to activate:

Code:
[root@localhost ~]# /proc/mdstat
-bash: /proc/mdstat: Permission denied
[root@localhost ~]# cat /proc/mdstat 
Personalities : 
md124 : inactive sdd3[5](S) sda3[2](S) sdc3[4](S) sdb3[3](S)
      8192000 blocks super 1.2
       
md125 : inactive sdb1[3](S) sdd1[5](S) sda1[2](S) sdc1[4](S)
      524537856 blocks super 1.2
       
md126 : inactive sdd4[5](S) sdc4[4](S) sdb4[3](S) sda4[2](S)
      11134119936 blocks super 1.2
       
md127 : inactive sda2[2](S) sdb2[3](S) sdc2[4](S) sdd2[5](S)
      51290112 blocks super 1.2
       
unused devices: <none>
whats going on with mdstat:

Code:
# /proc/mdstat 
/proc/mdstat: line 1: Personalities: command not found
/proc/mdstat: line 2: syntax error near unexpected token `('
/proc/mdstat: line 2: `md124 : inactive sdd3[5](S) sda3[2](S) sdc3[4](S) sdb3[3](S)'
how can i activate the rest of the array so i can attempt the recovery?
 
Old 12-14-2014, 03:54 PM   #7
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
also im unable to create /etc/mdadm/mdadm.conf to assist with activating the array portions that are currently inactive as this is a live environment. surprised i can not write to the live as it should be erased on boot.
 
Old 12-14-2014, 03:57 PM   #8
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
found out what im supposed to do, but how can some of the array be busy and others not be there:

Code:
# mdadm --assemble /dev/md0 /dev/sd[abcdef]1
mdadm: /dev/sda1 is busy - skipping
mdadm: /dev/sdb1 is busy - skipping
mdadm: /dev/sdc1 is busy - skipping
mdadm: /dev/sdd1 is busy - skipping
mdadm: no recogniseable superblock on /dev/sde1
mdadm: /dev/sde1 has no superblock - assembly aborted
[root@localhost ~]# df -Th
Filesystem          Type      Size  Used Avail Use% Mounted on
/dev/mapper/live-rw ext4      7.8G  3.6G  4.2G  47% /
devtmpfs            devtmpfs  7.8G     0  7.8G   0% /dev
tmpfs               tmpfs     7.8G  144K  7.8G   1% /dev/shm
tmpfs               tmpfs     7.8G   18M  7.8G   1% /run
tmpfs               tmpfs     7.8G     0  7.8G   0% /sys/fs/cgroup
/dev/sdg1           ext4      7.4G  1.1G  5.9G  16% /run/initramfs/live
tmpfs               tmpfs     7.8G  348K  7.8G   1% /tmp
varcacheyum         tmpfs     7.8G  468M  7.4G   6% /var/cache/yum
vartmp              tmpfs     7.8G  292K  7.8G   1% /var/tmp
/dev/loop2          squashfs  988M  988M     0 100% /run/media/liveuser/disk
/dev/loop0          squashfs  128K  128K     0 100% /run/media/liveuser/disk1
they are not mounted, therefore can not be busy. also if you scroll up sde is listing correctly.
 
Old 12-15-2014, 01:51 PM   #9
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
really lost, could use some expert guidance from the gang around here...

would it be easier if i attempted this from single user mode?
 
Old 12-16-2014, 03:05 PM   #10
jefro
Moderator
 
Registered: Mar 2008
Posts: 21,993

Rep: Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628
I see why no one is helping buddy. You keep adding to your thread. Looks like someone is helping you.


I think at this point maybe create a new thread on this to get better attention. It has become complex in the process. I know you are not suppose to but this has sat there a while. Edit any posts to keep zero thread on top of action list.
 
Old 12-16-2014, 06:50 PM   #11
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
in the end i borked my arrays and had to start over from scratch. several days work down the drain, several more to come.
 
Old 12-16-2014, 10:17 PM   #12
jefro
Moderator
 
Registered: Mar 2008
Posts: 21,993

Rep: Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628
Sorry buddy. Thanks for the update.
 
Old 12-19-2014, 05:37 PM   #13
lleb
Senior Member
 
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983

Original Poster
Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Quote:
Originally Posted by jefro View Post
I see why no one is helping buddy. You keep adding to your thread. Looks like someone is helping you.


I think at this point maybe create a new thread on this to get better attention. It has become complex in the process. I know you are not suppose to but this has sat there a while. Edit any posts to keep zero thread on top of action list.
ahh yeah just to answer the constant updates. that was me reading many links found via google ... server is back up and running. ripping the DVDs back to the server now that were not on the older drives.
 
Old 12-19-2014, 09:56 PM   #14
jefro
Moderator
 
Registered: Mar 2008
Posts: 21,993

Rep: Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628
Thanks for the update.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to edit initrd to fit your liveUSB - liveUSB preparation (openSUSE and others) deckoff Linux - General 7 01-08-2012 02:58 AM
how to detect solaris partitions on linux nagaraju.k Linux - Newbie 1 01-13-2010 07:32 AM
Gparted does not detect partitions... jmite Linux - Newbie 2 04-12-2009 06:51 PM
Ubuntu won't detect partitions... john8775 Ubuntu 1 10-25-2007 05:40 PM
cfdisk wont detect my partitions r350 Slackware - Installation 1 01-30-2004 05:35 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 04:14 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration