LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 01-01-2021, 12:18 PM   #31
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486

I cannot read the "mount" output in that form. Could you please post it as text between code tags so the text is large enough to be readable. Code tags are accessible with the # symbol on the top bar of the advanced screen.
 
Old 01-01-2021, 12:31 PM   #32
CJBIII
Member
 
Registered: Dec 2020
Location: Oak Lawn, IL
Distribution: openmediavault5, debian
Posts: 41

Original Poster
Rep: Reputation: Disabled
Sorry, these are photos of the screen attached to my server. I just realized that I can probably ssh in the server from my laptop I am on and copy it. haha Boy this getting embarrassing. Thanks for the patience
Attached Thumbnails
Click image for larger version

Name:	IMG_20210101_122537.jpg
Views:	6
Size:	279.8 KB
ID:	35118  
 
Old 01-01-2021, 12:46 PM   #33
CJBIII
Member
 
Registered: Dec 2020
Location: Oak Lawn, IL
Distribution: openmediavault5, debian
Posts: 41

Original Poster
Rep: Reputation: Disabled
Sorry, these are photos of the screen attached to my server. I just realized that I can probably ssh in the server from my laptop I am on and copy it. haha Boy this getting embarrassing. Thanks for the patience

Last edited by CJBIII; 01-01-2021 at 01:08 PM.
 
Old 01-01-2021, 01:24 PM   #34
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486
It seems you still have 5 drives sda-e (good)
You also have md127 raid array which was expected from earlier
I don't see any other devices which would relate to the raid array from the controller so it apparently is not active even though it seems so in the controller bios.
Could you also please post the output of these commands
Code:
ls /dev/mapper
sudo mdadm --detail /dev/md127
 
1 members found this post helpful.
Old 01-01-2021, 01:33 PM   #35
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486
You should be able to just mark what you want to copy with the mouse and with a right click select to copy it to the clipboard. Then you can paste it into the new message.
No need to be embarrassed. We have all been newbies and had to learn as we went. Linux is not windows. Some things are similar but there is a lot more detailed control available.
 
Old 01-01-2021, 01:33 PM   #36
CJBIII
Member
 
Registered: Dec 2020
Location: Oak Lawn, IL
Distribution: openmediavault5, debian
Posts: 41

Original Poster
Rep: Reputation: Disabled
root@openmediavault:~# ls /dev/mapper
control
root@openmediavault:~# sudo mdadm --detail /dev/md127
/dev/md127:
Version : 1.2
Raid Level : raid0
Total Devices : 1
Persistence : Superblock is persistent

State : inactive
Working Devices : 1

Name : debian:nasty
UUID : 17cc3a65:c33fc530:0d71f082:eb251149
Events : 558151

Number Major Minor RaidDevice

- 8 48 - /dev/sdd
 
Old 01-01-2021, 01:35 PM   #37
CJBIII
Member
 
Registered: Dec 2020
Location: Oak Lawn, IL
Distribution: openmediavault5, debian
Posts: 41

Original Poster
Rep: Reputation: Disabled
I had to switch machines because Windows decided to update for the last 20 minutes. I PuTTY 'ed into the server and copied. Proud just a little
 
Old 01-01-2021, 02:33 PM   #38
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486
OK, are you willing to completely nuke the existing failed array and build everything new ?

If so, what raid level do you want with those 4 disks.
The choices seem to be
raid5 ~9TB can handle 1 failed disk without data loss.
raid6 ~6TB can handle up to 2 failed disks simultaneously without data loss.
raid10 ~6TB can handle 1 failed disk without data loss.

We can work with those options, but whichever we use will be software raid using mdadm and you will need to go back into the bios and turn off raid and reset the controller to AHCI.
 
1 members found this post helpful.
Old 01-01-2021, 02:36 PM   #39
CJBIII
Member
 
Registered: Dec 2020
Location: Oak Lawn, IL
Distribution: openmediavault5, debian
Posts: 41

Original Poster
Rep: Reputation: Disabled
Will this allow me to view existing data on the two good disks with complete info or is that no longer an option?

I guess not. If the recovery is impossible then I guess a RAID10. Any recommendations about BTRFS and it's ability to grow?

I have some to research to do. I will reset the AHCI in the bios and check out the raids and the filesystems to make an intelligent choice. Will check in in the morning.

Last edited by CJBIII; 01-01-2021 at 03:01 PM.
 
Old 01-01-2021, 04:03 PM   #40
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486
Since we are unable to access the hardware array then no, the data is lost.

I have not yet worked with BTRFS, but have used LVM for many years. What I hear of BTRFS sounds promising but I have not taken that step yet. That decision is yours once the new raid device is created as you will have to partition and format it for use as any new disk.


Remember, once we start the following set of commands all hope of data recovery is gone, so please be certain before you begin.
I will provide the commands in groups with a brief explanation, so as long as you follow exactly there should be no issue. If there is any point you do not understand or if there is an error it will need to be corrected before trying to continue.

First, in bios switch the sata controller to AHCI instead of raid and reboot so we are working strictly with individual disks. (the screen shot you showed in post #20)

Next we need to remove all raid identification from the drives so the new array can be created from scratch. These commands will need to be run individually and all require sudo or run as root.

Code:
sudo mdadm -S /dev/md127
sudo mdadm /dev/md127 -r /dev/sdd
This should take care of the existing failed md127.

Now we need to erase the raid config from each drive.
This will totally erase your data if there was still any hope
Code:
sudo dd if=/dev/zero of=/dev/sda bs=1M count=1024
sudo dd if=/dev/zero of=/dev/sdb bs=1M count=1024
sudo dd if=/dev/zero of=/dev/sdc bs=1M count=1024
sudo dd if=/dev/zero of=/dev/sdd bs=1M count=1024
At this point if all the above has worked with no errors we need to check if you have an mdadm.conf file and if so remove it.
Code:
sudo rm -f /etc/mdadm/mdadm.conf
Now you should reboot before creating the new raid array.
After the reboot do "cat /proc/mdstat" to verify no traces of the raid remain. This should be empty or no file exists.

Finally we need to create the new array.
I suggest it be named md0 as in the command and this should work. If you choose raid5 or raid6 the only change would be the level number.
Code:
 sudo mdadm --create=md0 --raid-devices=4 --level=10 /dev/sda /dev/sdb /dev/sdc /dev/sdd
Once that command completes you should be able to do each of the following and see the status.
Code:
cat /proc/mdstat
sudo mdadm --detail /dev/md0
It may take some time for the array to stabilize and finish assembling so be a little patient

When /proc/mdstat shows something similar to
Code:
$  cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] 
md127 : active raid6 sdd[3] sde[1] sdc[5] sdb[4]
      5766400000 blocks super 1.2 level 6, 512k chunk, algorithm 2 [4/4] [UUUU]
      bitmap: 2/22 pages [8KB], 65536KB chunk

unused devices: <none>
then you are ready to use it as a device and can do the partitioning and formatting. At this stage you would set it up with the filesystem you choose, including BTRFS if that is your choice.

Now gparted or similar is the tool needed.

Last edited by computersavvy; 01-01-2021 at 04:05 PM.
 
1 members found this post helpful.
Old 01-02-2021, 09:52 AM   #41
CJBIII
Member
 
Registered: Dec 2020
Location: Oak Lawn, IL
Distribution: openmediavault5, debian
Posts: 41

Original Poster
Rep: Reputation: Disabled
I changed the RAID to AHCI...

root@openmediavault:~# mdadm -S /dev/md127
mdadm: stopped /dev/md127
root@openmediavault:~# mdadm /dev/md127 -r /dev/sdd
mdadm: error opening /dev/md127: No such file or directory
root@openmediavault:~#

Continue after error?
 
Old 01-02-2021, 10:37 AM   #42
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486
Repeat the "ls /dev" and see if md127 is still there. If not then continue with the next group of commands. If it is then let me know.

Also "cat /proc/mdstat" after a reboot

Last edited by computersavvy; 01-02-2021 at 11:19 AM.
 
Old 01-02-2021, 10:44 AM   #43
CJBIII
Member
 
Registered: Dec 2020
Location: Oak Lawn, IL
Distribution: openmediavault5, debian
Posts: 41

Original Poster
Rep: Reputation: Disabled
root@openmediavault:~# ls /dev
autofs log sde2 tty17 tty38 tty59 vcsa
block loop-control sde3 tty18 tty39 tty6 vcsa1
bsg mapper sg0 tty19 tty4 tty60 vcsa2
btrfs-control mem sg1 tty2 tty40 tty61 vcsa3
bus mqueue sg2 tty20 tty41 tty62 vcsa4
char net sg3 tty21 tty42 tty63 vcsa5
console null sg4 tty22 tty43 tty7 vcsa6
core nvram shm tty23 tty44 tty8 vcsu
cpu_dma_latency port snapshot tty24 tty45 tty9 vcsu1
cuse ppp snd tty25 tty46 ttyS0 vcsu2
disk psaux stderr tty26 tty47 ttyS1 vcsu3
dri ptmx stdin tty27 tty48 ttyS2 vcsu4
fb0 pts stdout tty28 tty49 ttyS3 vcsu5
fd random tty tty29 tty5 uhid vcsu6
full rfkill tty0 tty3 tty50 uinput vfio
fuse rtc tty1 tty30 tty51 urandom vga_arbiter
hpet rtc0 tty10 tty31 tty52 vcs vhci
hugepages sda tty11 tty32 tty53 vcs1 vhost-net
hwrng sdb tty12 tty33 tty54 vcs2 vhost-vsock
initctl sdc tty13 tty34 tty55 vcs3 watchdog
input sdd tty14 tty35 tty56 vcs4 watchdog0
kmsg sde tty15 tty36 tty57 vcs5 watchdog1
kvm sde1 tty16 tty37 tty58 vcs6 zero


root@openmediavault:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>
 
Old 01-02-2021, 11:04 AM   #44
CJBIII
Member
 
Registered: Dec 2020
Location: Oak Lawn, IL
Distribution: openmediavault5, debian
Posts: 41

Original Poster
Rep: Reputation: Disabled
root@openmediavault:~# dd if=/dev/zero of=/dev/sda bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 22.5201 s, 47.7 MB/s
root@openmediavault:~# dd if=/dev/zero of=/dev/sdb bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 23.0112 s, 46.7 MB/s
root@openmediavault:~# dd if=/dev/zero of=/dev/sdc bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 22.4627 s, 47.8 MB/s
root@openmediavault:~# dd if=/dev/zero of=/dev/sdd bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 22.2878 s, 48.2 MB/s
root@openmediavault:~# rm -f /etc/mdadm/mdadm.conf
root@openmediavault:~# reboot
 
Old 01-02-2021, 11:09 AM   #45
CJBIII
Member
 
Registered: Dec 2020
Location: Oak Lawn, IL
Distribution: openmediavault5, debian
Posts: 41

Original Poster
Rep: Reputation: Disabled
root@openmediavault:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>

root@openmediavault:~# mdadm --create=md0 --raid-device=4 --level=10 /dev/sda /dev/sdb /dev/sdc /dev/sdd
mdadm: option '--create' doesn't allow an argument
Usage: mdadm --help
for help
root@openmediavault:~#
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] added a couple of new disks and now /dev/sd* disks are all messed up nass Linux - Hardware 4 10-30-2012 10:16 AM
[SOLVED] RAID 5 with 4 hard disks... array started with only 3 out of 4 disks kikinovak Slackware 9 08-11-2012 06:33 AM
[SOLVED] What implications does it have now that IDE disks are seen as "scsi" disks? harryhaller Slackware 8 03-28-2011 07:54 AM
Hardware & Software Q...replaced NIC with same card but....long cbjhawks Linux - Hardware 7 02-11-2010 03:34 AM
Raid Problem Fedora Core 3, RAID LOST DISKS ALWAYS icatalan Linux - Hardware 1 09-17-2005 03:14 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 06:16 PM.

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