Super noob here,
I attempted to grow an xfs raid 6 through the webUI, and it appeared to be reshaping fine all of yesterday. Woke up this morning with a missing file system and an email from omv saying the new drive I was using had an offline_uncorrectable error. I restarted but nothing's working. No raid device, no file system. All drives are present and accounted for.
blkid shows all drives as linux_raid_member
Please help.
What does the SMART data for that drive look like?
cat /proc/mdstat returns:
Personalities : [raid6] [raid5] [raid4]
md126 : inactive sde[15](S)
1953512536 blocks super 1.2
md127 : inactive sdl[0] sdi[12] sdm[10] sdd[11] sdo[9] sdf[13] sdg[7] sda[14] sdk[5] sdb[4] sdn[3] sdh[2] sdj[1]
25395672086 blocks super 1.2
sde is the problem drive that has the uncorrectable errors:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 100 253 051 - 0
3 Spin_Up_Time POS--K 214 214 021 - 4291
4 Start_Stop_Count -O--CK 100 100 000 - 6
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 200 200 000 - 0
9 Power_On_Hours -O--CK 100 100 000 - 45
10 Spin_Retry_Count -O--CK 100 253 000 - 0
11 Calibration_Retry_Count -O--CK 100 253 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 6
192 Power-Off_Retract_Count -O--CK 200 200 000 - 2
193 Load_Cycle_Count -O--CK 200 200 000 - 26
194 Temperature_Celsius -O---K 113 108 000 - 37
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 1
198 Offline_Uncorrectable ----CK 200 200 000 - 1
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 1have you tried re-assembling the array in a degraded state?
How do I do that? Do you have any handy magic cli commands?
Up until today, I've not really had to manage the system outside of the webUI, and the web ui currently does not even show the degraded RAID device. I'm pretty much a linux noob.
Thanks!
first, let me see your mdadm.conf too please.
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# definitions of existing MD arrays
ARRAY /dev/md/Raid6 metadata=1.2 name=RacoonCity:Raid6 UUID=6516c9a0:e9232a78
76f99b:0caaa0fd
# instruct the monitoring daemon where to send mail alerts
MAILADDR xxx@gmail.com
MAILFROM rootwhen you built this array i assume you used
sdl sdi sdm sdd sdo sdf sdg sda sdk sdb sdn sdh sdj sde
to comprise the array. correct?
Everything but sde. That was the drive I was using to attempt to grow the array size because I was running out of space.
what happens if you "mdadm --assemble --scan -v" then "cat /proc/mdstat"
mdadm: looking for devices for /dev/md/Raid6
mdadm: /dev/sdo is busy - skipping
mdadm: /dev/sdm is busy - skipping
mdadm: /dev/sdl is busy - skipping
mdadm: /dev/sdn is busy - skipping
mdadm: /dev/sdk is busy - skipping
mdadm: /dev/sdi is busy - skipping
mdadm: /dev/sdj is busy - skipping
mdadm: /dev/sdh is busy - skipping
mdadm: /dev/sdg is busy - skipping
mdadm: /dev/sdb is busy - skipping
mdadm: /dev/sda is busy - skipping
mdadm: /dev/sdd is busy - skipping
mdadm: /dev/sde is busy - skipping
mdadm: no RAID superblock on /dev/sdc5
mdadm: no RAID superblock on /dev/sdc2
mdadm: no RAID superblock on /dev/sdc1
mdadm: no RAID superblock on /dev/sdc
mdadm: /dev/sdf is busy - skippingcat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md126 : inactive sde[15](S)
1953512536 blocks super 1.2
md127 : inactive sdl[0] sdi[12] sdm[10] sdd[11] sdo[9] sdf[13] sdg[7] sda[14] sdk[5] sdb[4] sdn[3] sdh[2] sdj[1]
25395672086 blocks super 1.2
Here's some more information I got out of dmesg:
Any ideas?
[ 7.202620] md: md127 stopped.
[ 7.214610] md: bind<sdj>
[ 7.258791] md: bind<sdh>
[ 7.258901] md: bind<sdn>
[ 7.259198] md: bind<sdb>
[ 7.259281] md: bind<sdk>
[ 7.259581] md: bind<sda>
[ 7.259678] md: bind<sdg>
[ 7.259776] md: bind<sdf>
[ 7.259872] md: bind<sdo>
[ 7.260169] md: bind<sdd>
[ 7.260259] md: bind<sdm>
[ 7.260350] md: bind<sdi>
[ 7.260443] md: bind<sde>
[ 7.261002] md: bind<sdl>
[ 7.261021] md: kicking non-fresh sde from array!
[ 7.261023] md: unbind<sde>
[ 7.274464] md: export_rdev(sde)
[ 7.342428] raid6: int64x1 3818 MB/s
[ 7.410408] raid6: int64x2 3576 MB/s
[ 7.478377] raid6: int64x4 3243 MB/s
[ 7.546354] raid6: int64x8 2822 MB/s
[ 7.614325] raid6: sse2x1 9578 MB/s
[ 7.682301] raid6: sse2x2 12145 MB/s
[ 7.750276] raid6: sse2x4 14026 MB/s
[ 7.750277] raid6: using algorithm sse2x4 (14026 MB/s)
[ 7.750403] async_tx: api initialized (async)
[ 7.750529] xor: automatically using best checksumming function: generic_s se
[ 7.770280] generic_sse: 15352.000 MB/sec
[ 7.770281] xor: using function: generic_sse (15352.000 MB/sec)
[ 7.770900] md: raid6 personality registered for level 6
[ 7.770902] md: raid5 personality registered for level 5
[ 7.770903] md: raid4 personality registered for level 4
[ 7.771120] bio: create slab <bio-1> at 1
[ 7.771125] md/raid:md127: not clean -- starting background reconstruction
[ 7.771126] md/raid:md127: reshape will continue
[ 7.771131] md/raid:md127: device sdl operational as raid disk 0
[ 7.771133] md/raid:md127: device sdi operational as raid disk 12
[ 7.771134] md/raid:md127: device sdm operational as raid disk 11
[ 7.771135] md/raid:md127: device sdd operational as raid disk 10
[ 7.771136] md/raid:md127: device sdo operational as raid disk 9
[ 7.771138] md/raid:md127: device sdf operational as raid disk 8
[ 7.771139] md/raid:md127: device sdg operational as raid disk 7
[ 7.771140] md/raid:md127: device sda operational as raid disk 6
[ 7.771141] md/raid:md127: device sdk operational as raid disk 5
[ 7.771142] md/raid:md127: device sdb operational as raid disk 4
[ 7.771143] md/raid:md127: device sdn operational as raid disk 3
[ 7.771145] md/raid:md127: device sdh operational as raid disk 2
[ 7.771146] md/raid:md127: device sdj operational as raid disk 1
[ 7.771611] md/raid:md127: allocated 14800kB
[ 7.771627] md/raid:md127: cannot start dirty degraded array.
[ 7.771679] RAID conf printout:
[ 7.771680] --- level:6 rd:14 wd:13
[ 7.771681] disk 0, o:1, dev:sdl
[ 7.771682] disk 1, o:1, dev:sdj
[ 7.771683] disk 2, o:1, dev:sdh
[ 7.771684] disk 3, o:1, dev:sdn
[ 7.771685] disk 4, o:1, dev:sdb
[ 7.771686] disk 5, o:1, dev:sdk
[ 7.771687] disk 6, o:1, dev:sda
[ 7.771688] disk 7, o:1, dev:sdg
[ 7.771689] disk 8, o:1, dev:sdf
[ 7.771690] disk 9, o:1, dev:sdo
[ 7.771691] disk 10, o:1, dev:sdd
[ 7.771692] disk 11, o:1, dev:sdm
[ 7.771693] disk 12, o:1, dev:sdi
[ 7.772181] md/raid:md127: failed to run raid set.
[ 7.772226] md: pers->run() failed ...As a recommendation I would return that disk. You cannot have a disk with 45 hours on an already having bad sectors. I assuming is new.
Oh definitely! But the problem for now is that I still have an array that's not working. Any suggestions on how I can get the system restored?
I don't have raid arrays now. So you better follow @cjohnson19401 lead
Yup, still waiting on a solution because I'm pretty much out of ideas. Thank you both for your help!
how are you using the r6 volume? you format it as xfs then what? share that xfs over nfs or smb?
what does the output of "mount" look like?
Yup, it's just a simple network volume that's smb shared on a home server with multiple directories. It's accessible through the typical windows network.
we can't really work on the md device while something is using it. we just have to figure out what. disable smb via the webui then let's see where it's mounted with "mount". let's also see what your fstab looks like too please.
I've disabled both smb, and plex. Not sure how to use fstab though ^_^;
mount gives the following:
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=1011539,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=810952k,mode=755)
/dev/disk/by-uuid/19f98116-457d-41ea-856a-1797b616ccfa on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=4158540k)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!