-
Unmountable: unsupported or no file system
Yes it is mounted!
-
Unmountable: unsupported or no file system
@JorgeB I believe we are good now, thanks again! ipefs /dev/md8p1 DEVICE OFFSET TYPE UUID LABEL md8p1 0x0 xfs 5c05104a-0a7d-4477-b56a-293fc29435df
-
Unmountable: unsupported or no file system
cat /proc/mdstat sbName=/boot/config/super.dat sbVersion=2.9.27 sbCreated=1719958472 sbUpdated=1757030496 sbEvents=143 sbState=1 sbNumDisks=10 sbLabel=090C-1000-0370-423100000190 sbSynced=1757030496 sbSynced2=0 sbSyncErrs=0 sbSyncExit=0 mdVersion=2.9.35 mdState=STARTED mdNumDisks=9 mdNumDisabled=1 mdNumReplaced=0 mdNumInvalid=2 mdNumMissing=0 mdNumWrong=0 mdNumNew=0 mdSwapP=0 mdSwapQ=0 mdResyncAction=recon D8 mdResyncSize=17578328012 mdResyncCorr=1 mdResync=17578328012 mdResyncPos=17167986392 mdResyncDt=31 mdResyncDb=3686536 diskNumber.0=0 diskName.0= diskSize.0=19531825100 diskState.0=7 diskId.0=ST20000NM004E-3HR103_ZX213CM2 rdevNumber.0=0 rdevStatus.0=DISK_OK rdevName.0=sdk rdevOffset.0=64 rdevSize.0=19531825100 rdevId.0=ST20000NM004E-3HR103_ZX213CM2 rdevReads.0=4293934077 rdevWrites.0=1939279 rdevNumErrors.0=0 diskNumber.1=1 diskName.1=md1p1 diskSize.1=17578328012 diskState.1=7 diskId.1=ST18000NM000J-2TV103_ZR50LQTA rdevNumber.1=1 rdevStatus.1=DISK_OK rdevName.1=sdd rdevOffset.1=64 rdevSize.1=17578328012 rdevId.1=ST18000NM000J-2TV103_ZR50LQTA rdevReads.1=4292533033 rdevWrites.1=522 rdevNumErrors.1=0 diskNumber.2=2 diskName.2=md2p1 diskSize.2=17578328012 diskState.2=7 diskId.2=ST18000NM000J-2TV103_ZR51F7Y3 rdevNumber.2=2 rdevStatus.2=DISK_OK rdevName.2=sdf rdevOffset.2=64 rdevSize.2=17578328012 rdevId.2=ST18000NM000J-2TV103_ZR51F7Y3 rdevReads.2=4292133229 rdevWrites.2=522 rdevNumErrors.2=0 diskNumber.3=3 diskName.3=md3p1 diskSize.3=17578328012 diskState.3=7 diskId.3=ST18000NM000J-2TV103_ZR58W9FF rdevNumber.3=3 rdevStatus.3=DISK_OK rdevName.3=sdg rdevOffset.3=64 rdevSize.3=17578328012 rdevId.3=ST18000NM000J-2TV103_ZR58W9FF rdevReads.3=4428485691 rdevWrites.3=1936143 rdevNumErrors.3=0 diskNumber.4=4 diskName.4=md4p1 diskSize.4=17578328012 diskState.4=7 diskId.4=ST18000NM000J-2TV103_ZR51ALH8 rdevNumber.4=4 rdevStatus.4=DISK_OK rdevName.4=sdl rdevOffset.4=64 rdevSize.4=17578328012 rdevId.4=ST18000NM000J-2TV103_ZR51ALH8 rdevReads.4=4291998477 rdevWrites.4=523 rdevNumErrors.4=0 diskNumber.5=5 diskName.5=md5p1 diskSize.5=9766436812 diskState.5=7 diskId.5=HGST_HUH721010ALE600_7PGVSM3C rdevNumber.5=5 rdevStatus.5=DISK_OK rdevName.5=sde rdevOffset.5=64 rdevSize.5=9766436812 rdevId.5=HGST_HUH721010ALE600_7PGVSM3C rdevReads.5=2441609974 rdevWrites.5=523 rdevNumErrors.5=0 diskNumber.6=6 diskName.6=md6p1 diskSize.6=9766436812 diskState.6=7 diskId.6=HGST_HUH721010ALE600_7PGRN7BG rdevNumber.6=6 rdevStatus.6=DISK_OK rdevName.6=sdj rdevOffset.6=64 rdevSize.6=9766436812 rdevId.6=HGST_HUH721010ALE600_7PGRN7BG rdevReads.6=2441609974 rdevWrites.6=523 rdevNumErrors.6=0 diskNumber.7=7 diskName.7=md7p1 diskSize.7=19531825100 diskState.7=7 diskId.7=ST20000NM004E-3HR103_ZX212P46 rdevNumber.7=7 rdevStatus.7=DISK_OK rdevName.7=sdi rdevOffset.7=64 rdevSize.7=19531825100 rdevId.7=ST20000NM004E-3HR103_ZX212P46 rdevReads.7=4291998551 rdevWrites.7=523 rdevNumErrors.7=0 diskNumber.8=8 diskName.8=md8p1 diskSize.8=17578328012 diskState.8=6 diskId.8=ST18000NM003D-3DL103_ZVT7BXT7 rdevNumber.8=8 rdevStatus.8=DISK_INVALID rdevName.8=sdh rdevOffset.8=64 rdevSize.8=17578328012 rdevId.8=ST18000NM003D-3DL103_ZVT7BXT7 rdevReads.8=97 rdevWrites.8=4291996738 rdevNumErrors.8=0 diskNumber.9=9 diskName.9= diskSize.9=0 diskState.9=0 diskId.9= rdevNumber.9=9 rdevStatus.9=DISK_NP rdevName.9= rdevOffset.9=0 rdevSize.9=0 rdevId.9= rdevReads.9=0 rdevWrites.9=0 rdevNumErrors.9=0 diskNumber.10=10 diskName.10= diskSize.10=0 diskState.10=0 diskId.10= rdevNumber.10=10 rdevStatus.10=DISK_NP rdevName.10= rdevOffset.10=0 rdevSize.10=0 rdevId.10= rdevReads.10=0 rdevWrites.10=0 rdevNumErrors.10=0 diskNumber.11=11 diskName.11= diskSize.11=0 diskState.11=0 diskId.11= rdevNumber.11=11 rdevStatus.11=DISK_NP rdevName.11= rdevOffset.11=0 rdevSize.11=0 rdevId.11= rdevReads.11=0 rdevWrites.11=0 rdevNumErrors.11=0 diskNumber.12=12 diskName.12= diskSize.12=0 diskState.12=0 diskId.12= rdevNumber.12=12 rdevStatus.12=DISK_NP rdevName.12= rdevOffset.12=0 rdevSize.12=0 rdevId.12= rdevReads.12=0 rdevWrites.12=0 rdevNumErrors.12=0 diskNumber.13=13 diskName.13= diskSize.13=0 diskState.13=0 diskId.13= rdevNumber.13=13 rdevStatus.13=DISK_NP rdevName.13= rdevOffset.13=0 rdevSize.13=0 rdevId.13= rdevReads.13=0 rdevWrites.13=0 rdevNumErrors.13=0 diskNumber.14=14 diskName.14= diskSize.14=0 diskState.14=0 diskId.14= rdevNumber.14=14 rdevStatus.14=DISK_NP rdevName.14= rdevOffset.14=0 rdevSize.14=0 rdevId.14= rdevReads.14=0 rdevWrites.14=0 rdevNumErrors.14=0 diskNumber.15=15 diskName.15= diskSize.15=0 diskState.15=0 diskId.15= rdevNumber.15=15 rdevStatus.15=DISK_NP rdevName.15= rdevOffset.15=0 rdevSize.15=0 rdevId.15= rdevReads.15=0 rdevWrites.15=0 rdevNumErrors.15=0 diskNumber.16=16 diskName.16= diskSize.16=0 diskState.16=0 diskId.16= rdevNumber.16=16 rdevStatus.16=DISK_NP rdevName.16= rdevOffset.16=0 rdevSize.16=0 rdevId.16= rdevReads.16=0 rdevWrites.16=0 rdevNumErrors.16=0 diskNumber.17=17 diskName.17= diskSize.17=0 diskState.17=0 diskId.17= rdevNumber.17=17 rdevStatus.17=DISK_NP rdevName.17= rdevOffset.17=0 rdevSize.17=0 rdevId.17= rdevReads.17=0 rdevWrites.17=0 rdevNumErrors.17=0 diskNumber.18=18 diskName.18= diskSize.18=0 diskState.18=0 diskId.18= rdevNumber.18=18 rdevStatus.18=DISK_NP rdevName.18= rdevOffset.18=0 rdevSize.18=0 rdevId.18= rdevReads.18=0 rdevWrites.18=0 rdevNumErrors.18=0 diskNumber.19=19 diskName.19= diskSize.19=0 diskState.19=0 diskId.19= rdevNumber.19=19 rdevStatus.19=DISK_NP rdevName.19= rdevOffset.19=0 rdevSize.19=0 rdevId.19= rdevReads.19=0 rdevWrites.19=0 rdevNumErrors.19=0 diskNumber.20=20 diskName.20= diskSize.20=0 diskState.20=0 diskId.20= rdevNumber.20=20 rdevStatus.20=DISK_NP rdevName.20= rdevOffset.20=0 rdevSize.20=0 rdevId.20= rdevReads.20=0 rdevWrites.20=0 rdevNumErrors.20=0 diskNumber.21=21 diskName.21= diskSize.21=0 diskState.21=0 diskId.21= rdevNumber.21=21 rdevStatus.21=DISK_NP rdevName.21= rdevOffset.21=0 rdevSize.21=0 rdevId.21= rdevReads.21=0 rdevWrites.21=0 rdevNumErrors.21=0 diskNumber.22=22 diskName.22= diskSize.22=0 diskState.22=0 diskId.22= rdevNumber.22=22 rdevStatus.22=DISK_NP rdevName.22= rdevOffset.22=0 rdevSize.22=0 rdevId.22= rdevReads.22=0 rdevWrites.22=0 rdevNumErrors.22=0 diskNumber.23=23 diskName.23= diskSize.23=0 diskState.23=0 diskId.23= rdevNumber.23=23 rdevStatus.23=DISK_NP rdevName.23= rdevOffset.23=0 rdevSize.23=0 rdevId.23= rdevReads.23=0 rdevWrites.23=0 rdevNumErrors.23=0 diskNumber.24=24 diskName.24= diskSize.24=0 diskState.24=0 diskId.24= rdevNumber.24=24 rdevStatus.24=DISK_NP rdevName.24= rdevOffset.24=0 rdevSize.24=0 rdevId.24= rdevReads.24=0 rdevWrites.24=0 rdevNumErrors.24=0 diskNumber.25=25 diskName.25= diskSize.25=0 diskState.25=0 diskId.25= rdevNumber.25=25 rdevStatus.25=DISK_NP rdevName.25= rdevOffset.25=0 rdevSize.25=0 rdevId.25= rdevReads.25=0 rdevWrites.25=0 rdevNumErrors.25=0 diskNumber.26=26 diskName.26= diskSize.26=0 diskState.26=0 diskId.26= rdevNumber.26=26 rdevStatus.26=DISK_NP rdevName.26= rdevOffset.26=0 rdevSize.26=0 rdevId.26= rdevReads.26=0 rdevWrites.26=0 rdevNumErrors.26=0 diskNumber.27=27 diskName.27= diskSize.27=0 diskState.27=0 diskId.27= rdevNumber.27=27 rdevStatus.27=DISK_NP rdevName.27= rdevOffset.27=0 rdevSize.27=0 rdevId.27= rdevReads.27=0 rdevWrites.27=0 rdevNumErrors.27=0 diskNumber.28=28 diskName.28= diskSize.28=0 diskState.28=0 diskId.28= rdevNumber.28=28 rdevStatus.28=DISK_NP rdevName.28= rdevOffset.28=0 rdevSize.28=0 rdevId.28= rdevReads.28=0 rdevWrites.28=0 rdevNumErrors.28=0 diskNumber.29=29 diskName.29= diskSize.29=0 diskState.29=4 diskId.29= rdevNumber.29=29 rdevStatus.29=DISK_NP_DSBL rdevName.29= rdevOffset.29=0 rdevSize.29=0 rdevId.29= rdevReads.29=0 rdevWrites.29=0 rdevNumErrors.29=0
-
Unmountable: unsupported or no file system
tail -f /var/log/syslog Sep 4 21:54:32 SITHLORD shfs: share cache full Sep 4 21:54:33 SITHLORD shfs: share cache full Sep 4 21:54:33 SITHLORD shfs: share cache full Sep 4 22:49:15 SITHLORD emhttpd: spinning down /dev/sdj Sep 4 22:49:15 SITHLORD emhttpd: spinning down /dev/sde Sep 4 23:28:26 SITHLORD shfs: share cache full Sep 5 00:46:21 SITHLORD shfs: share cache full Sep 5 00:46:21 SITHLORD shfs: share cache full Sep 5 00:54:13 SITHLORD shfs: share cache full Sep 5 00:56:31 SITHLORD shfs: share cache full
-
Unmountable: unsupported or no file system
Sorry @JorgeB for the late reply.... I was sick yesterday and the drive is still rebuilding... it is at 96% done. I did buy a new 20 TB drive in the event this one fails
-
Unmountable: unsupported or no file system
So far we are looking good: tail -f /var/log/syslog Sep 3 18:37:28 SITHLORD rc.docker: binhex-radarr-cartoons: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: binhex-radarr4k: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: binhex-sonarr: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: SonnarAnime: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: binhex-lidarr: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: Containers started. Sep 3 18:37:28 SITHLORD rc.docker: firefox: started successfully! Sep 3 18:51:42 SITHLORD Parity Check Tuning: Parity Sync/Data Rebuild detected Sep 3 18:52:01 SITHLORD emhttpd: spinning down /dev/sdc Sep 3 18:52:01 SITHLORD emhttpd: spinning down /dev/sda
-
Unmountable: unsupported or no file system
I did some digging and went down this path and it seems to be working... xfs_repair -n /dev/md8 /dev/md8: No such file or directory fatal error -- couldn't initialize XFS library lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINT NAME SIZE FSTYPE MOUNTPOINT loop0 579.8M squashfs /usr loop1 169.8M squashfs /lib loop2 64G btrfs /var/lib/docker sda 14.6T ├─sda1 200M vfat └─sda2 14.6T ntfs sdb 119.5G └─sdb1 119.5G vfat /boot sdc 14.6T ├─sdc1 200M vfat └─sdc2 14.6T ntfs sdd 16.4T └─sdd1 16.4T xfs sde 9.1T └─sde1 9.1T xfs sdf 16.4T └─sdf1 16.4T xfs sdg 16.4T └─sdg1 16.4T xfs sdh 16.4T └─sdh1 16.4T sdi 18.2T └─sdi1 18.2T xfs sdj 9.1T └─sdj1 9.1T xfs sdk 18.2T └─sdk1 18.2T xfs sdl 16.4T └─sdl1 16.4T xfs md1p1 16.4T /mnt/disk1 md2p1 16.4T /mnt/disk2 md3p1 16.4T /mnt/disk3 md4p1 16.4T /mnt/disk4 md5p1 9.1T /mnt/disk5 md6p1 9.1T /mnt/disk6 md7p1 18.2T /mnt/disk7 md8p1 16.4T nvme1n1 3.6T └─nvme1n1p1 3.6T btrfs /mnt/fetching nvme2n1 1.8T └─nvme2n1p1 1.8T btrfs /mnt/cache nvme0n1 476.9G └─nvme0n1p1 476.9G btrfs /mnt/vmdisk xfs_repair -n /dev/sdh1 /dev/sdh1: No such file or directory fatal error -- couldn't initialize XFS library wipefs -a /dev/sdh1 wipefs: error: /dev/sdh1: probing initialization failed: No such file or directory Parted /dev/sdh print Model: ATA ST18000NM003D-3D (scsi) Disk /dev/sdh: 18.0TB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 32.8kB 18.0TB 18.0TB At this point, I decicded to try to rebuild... I think I see what happened... the system crashed ad casued this system to act up... I have set the disk to no device and then selected this... Start will disable the missing disk and then bring the array on-line. Install a replacement disk as soon as possible. Yes, I want to do this Reassign Disk 8 and Trigger Rebuild Stop the array again. Go back to the Disk 8 dropdown and reassign your drive: ST18000NM003D-3DL103_ZVT7BXT7 (sdh) Scroll down and click Start. Unraid should now detect that Disk 8 is “wrong” and offer to rebuild it from parity. As soon as I set the drive to ST18000NM003D-3DL103_ZVT7BXT7 (sdh) It now says: "All existing data on this device will be OVERWRITTEN when array is Started" When I started it, I see "Started Stop will take the array off-line. Disabled -- Parity operation is running Unmountable disk present: Disk 8 • ST18000NM003D-3DL103_ZVT7BXT7 (sdh) Format will create a file system in all Unmountable disks. Yes, I want to do this Data-Rebuild in progress." I see this... tail -f /var/log/syslog Sep 3 18:36:57 SITHLORD kernel: docker0: port 4(vethd3c2eb8) entered blocking state Sep 3 18:36:57 SITHLORD kernel: docker0: port 4(vethd3c2eb8) entered forwarding state Sep 3 18:36:57 SITHLORD rc.docker: tautulli: started successfully! Sep 3 18:36:57 SITHLORD rc.docker: tautulli: wait 30 seconds Sep 3 18:36:58 SITHLORD Parity Check Tuning: No restart information present Sep 3 18:36:58 SITHLORD tips.and.tweaks: Tweaks Applied Sep 3 18:36:58 SITHLORD unassigned.devices: Mounting 'Auto Mount' Remote Shares... Sep 3 18:36:58 SITHLORD unassigned.devices: Using Gateway '10.1.1.1' for Remote Shares. Sep 3 18:36:58 SITHLORD unassigned.devices: Waiting 5 secs before mounting Remote Shares... Sep 3 18:37:06 SITHLORD reload_services: execute queued job 18 Sep 3 18:37:27 SITHLORD rc.docker: binhex-jackett: started successfully! Sep 3 18:37:27 SITHLORD rc.docker: binhex-radarr: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: binhex-radarr-cartoons: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: binhex-radarr4k: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: binhex-sonarr: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: SonnarAnime: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: binhex-lidarr: started successfully! Sep 3 18:37:28 SITHLORD rc.docker: Containers started. Sep 3 18:37:28 SITHLORD rc.docker: firefox: started successfully! I am seeing the data being rebuilt. If this fails then I know what to do next... again thank you for you help @JorgeB I really appreciate it
-
Unmountable: unsupported or no file system
It did not work, so since this is a single disk failure, I think I will just attempt to rebuild the drive after formatting it, @JorgeB is that ok?
-
Unmountable: unsupported or no file system
Wish me luck! xfs_repair /dev/md8p1 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... ............................................... will check when I get back home!
-
Unmountable: unsupported or no file system
Thank you so much!
-
Unmountable: unsupported or no file system
I assume that I will need to stop the array and then start it in maintenance mode first before I run xfs_repair /dev/md8p1 Is that correct? Also, what is the difference between /dev/md8p1 and /dev/sdh? Is sdh the ind disk and md8p1 the array?
-
Unmountable: unsupported or no file system
Thank you for looking into this concern for me. This was an exisiting disk that had data on it and was working. It stopped sometime over the weekend and displayed that error. (Unmountable: unsupported or no file system") I have not done a rebuild and I did a smart test and it passed
-
Unmountable: unsupported or no file system
wipefs /dev/md8p1 listed no output with array started should I have used wipefs /dev/sdh? (Disk 8 is issue and it is 18 TB not 20 sorry) Parity ST20000NM004E-3HR103_ZX213CM2 - 20 TB (sdk) 33 °C 83.2 MB/s 83.2 MB/s 0 Disk 1 ST18000NM000J-2TV103_ZR50LQTA - 18 TB (sdd) 32 °C 0.0 B/s 0.0 B/s 0 xfs 18 TB 8.87 TB 9.13 TB Disk 2 ST18000NM000J-2TV103_ZR51F7Y3 - 18 TB (sdf) 31 °C 0.0 B/s 0.0 B/s 0 xfs 18 TB 8.75 TB 9.25 TB Disk 3 ST18000NM000J-2TV103_ZR58W9FF - 18 TB (sdg) 32 °C 83.4 MB/s 82.2 MB/s 0 xfs 18 TB 5.13 TB 12.9 TB Disk 4 ST18000NM000J-2TV103_ZR51ALH8 - 18 TB (sdl) 32 °C 0.0 B/s 0.0 B/s 0 xfs 18 TB 126 GB 17.9 TB Disk 5 HGST_HUH721010ALE600_7PGVSM3C - 10 TB (sde) 30 °C 0.0 B/s 0.0 B/s 0 xfs 10 TB 69.7 GB 9.93 TB Disk 6 HGST_HUH721010ALE600_7PGRN7BG - 10 TB (sdj) 30 °C 0.0 B/s 0.0 B/s 0 xfs 10 TB 69.7 GB 9.93 TB Disk 7 ST20000NM004E-3HR103_ZX212P46 - 20 TB (sdi) 34 °C 0.0 B/s 0.0 B/s 0 xfs 20 TB 139 GB 19.9 TB Disk 8 ST18000NM003D-3DL103_ZVT7BXT7 - 18 TB (sdh) 37 °C 0.0 B/s 0.0 B/s 0 auto Unmountable: unsupported or no file system Here is the diag filesithlord-diagnostics-20250903-0657.zip
-
Unmountable: unsupported or no file system
What (and how) command should I have run from the GUI? Could you provide a step by step detail, please?
-
StangSCT69 started following Unmountable: unsupported or no file system
-
Unmountable: unsupported or no file system
I have attached my logs to this topic and have ran this command: dd if=/dev/sdh bs=512 count=1 | od -Ax -x 1+0 records in 1+0 records out 000000 0000 0000 0000 0000 0000 0000 0000 0000 512 bytes copied, 1.1198e-05 s, 45.7 MB/s* 0001c0 0002 ffee ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 I am currently have been running this command, after stopping my array and putting it in maintenance mode. I ahve been running this command, for the past 8 hours: xfs_repair -v /dev/sdh (20 TB drive) It talked about finding a secondary superblock... and all I see this... over and over sithlord-syslog-20250903-1228.zip
StangSCT69
Members
-
Joined
-
Last visited