LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-09-2019, 07:27 AM   #16
linuxtinker
Member
 
Registered: Dec 2013
Location: NJ / USA
Distribution: Slackware 64 -Current
Posts: 208

Rep: Reputation: 93

Quote:
Originally Posted by 3rensho View Post
Update:

After doing some more checking it is looking like there may be a hardware problem.



The same happens to me I just use UUID's to take care of it.
 
Old 03-17-2019, 02:21 AM   #17
3rensho
Member
 
Registered: Mar 2008
Location: Switzerland
Distribution: Slackware64
Posts: 197

Original Poster
Rep: Reputation: 9
OK I'm back. Replaced a flakey disk, started over, created raid 1 (used metadata=1.2 this time had been using 0.90). Installed Slack64-current from Eric's 1.3.19 edition, copied over some scripts from my NAS and build latest kernel. Booted and it crapped out again, but some progress noted in that the fatal message about e2fsck not being found has changed from md127 to md0. So, some progress. Will try entering UUID in fstab to see it that works. Also noticed when building mdadm.conf that the raid is listed as /dev/md/0. Checked the last backup from my previously running -current and the mdadm.conf listed it as /dev/md/0_0. Does the metadata version make a difference in how the /dev/md is listed?

Edit: Noticed something else strange. The raid suddenly started rebuilding itself. If I do -

file -s /dev/md0

/dev/md0: Linux rev 1.0 ext4 filesystem data, UUID=318fbe83-55e7-452e-b27b-e4acfafa20e4 (needs journal recovery) (extents) (large files) (huge files)

but this UUID is very different from -

mdadm --detail --scan /dev/md0

ARRAY /dev/md0 metadata=1.2 name=slackware:0 UUID=f80a1f11:1a0802bc:7ef257d5:87f46ad2

This too is disturbing -

mdadm --examine /dev/md0 | grep UUID
mdadm: No md superblock detected on /dev/md0.

Last edited by 3rensho; 03-17-2019 at 04:42 AM. Reason: New info
 
Old 03-22-2019, 02:59 AM   #18
3rensho
Member
 
Registered: Mar 2008
Location: Switzerland
Distribution: Slackware64
Posts: 197

Original Poster
Rep: Reputation: 9
Finally got it working. Created /dev/md0 array after switching back to metadata 0.90. After rebooting everything runs fine but it still insists the array is md127. I don't care as I have the UUID entered in fstab so it can call itself what ever it wants. Thanks again to everyone for your ideas and suggestions.
 
1 members found this post helpful.
  


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
LXer: Tor becomes extra secure as .onion becomes Special-Use Domain Name LXer Syndicated Linux News 0 09-14-2015 07:00 PM
Degraded Raid 1, was md0 now md127.. need help jcmorse563 Linux - Server 5 03-25-2014 09:48 AM
Linux raid / md127 pika Linux - Server 2 11-03-2013 12:33 PM
After creating raid6 array, mkfs.jfs /dev/md0, then cannot mount /dev/md0 artagel Debian 4 12-06-2009 08:30 AM
When backspace becomes ^[[D and up arrow becomes ^[[A simonb Linux - Software 1 12-21-2008 01:04 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:23 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration