my 1 harddrive Lost its File System (unmountable)


Recommended Posts

ya i got some backups...  ya didnt help this time.. what is a backup super?  since it said to use it in the error above  as i thought root was the highest?

 

so i got a spare drive  in the 4 bay case...  i added the drive as a cache pool..  reason is my sister not home to swap drives  in hot swap

 

so i set it to a xfs  file system...    so hopefully its more flexable it doesnt happen again..  but be nice like  i mentioned if they did offer a notification for these type of errors  that doesnt show up in the regular notification options

Link to comment

oh so a superblock is like a backup of a file or something that a super backup does..

 

does this also happen possible for the array too? 

right now its a 8tb set to btrfs... can it fall to this same scenario that the download pool happened

and should i switch to xfs   or shove a 8tb drive in for parity    and than that solves it?

Edited by comet424
Link to comment
1 hour ago, comet424 said:

r shove a 8tb drive in for parity 

Parity does not stop a file system getting corrupted.   Parity has no knowledge of file or file systems and will simply mirror any file system corruption that does occur.

BTRFS is very good when it is working well but is more prone to corruption in the event of hardware errors

XFS is more forgiving and you are more likely to be able to repair file system corruption if it occurs.

Link to comment

ah ok..  so if you have say 5 disks and a parity  and btrfs  fs corrupts on disk2..   doesnt the parity fix that fs corruption? or does it corrupt everything.. reason i wondering if i should go to  xfs  instead of btrfs for all my arrays?    i noticed  if you do 2 drives for a pool  you cant do xfs  it only allows btrfs...

 

and so  i just checked my sisters server.. she not home to pull the drive or swap it but i did a reboot and its showsing  UNC errors etc..  is this also still saying its a power/connector  or is it saying a drive is failing....  i re set up my sisters download drive pool with a spare drive that she had in her 4 bay server.. so its using that.. not issues for that ..

 

and is there a plugin  to tell ya  that a FS has corrupted  from the system logs?  i find the notifications doesnt seem to show  when FS corrupts on the sys logs are saying ata5  failure  be nice to know its happening   that i wouldnt keep writting to it etc.. and i bet if i hadnt rebooted the unraid  since the download drive  was mounted  i guess if i had know htere was a drive failure i could have ran  a btrfs repair and it would have fixed things since i was able to use it at the time

 

here some of the errors  it just repeats

 

 

so if you have 2 ssds say for a cache pool and you can only do btrfs.. and if one of the ssds fs corrupts  does the 2nd  ssd fs  also corrupt.

Jul  3 13:31:48 mitchsserver kernel: ACPI: Early table checksum verification disabled
Jul  3 13:31:48 mitchsserver kernel: floppy0: no floppy controllers found
Jul  3 13:31:48 mitchsserver kernel: ata5.00: exception Emask 0x50 SAct 0x2000 SErr 0x30802 action 0xe frozen
Jul  3 13:31:48 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:48 mitchsserver kernel: ata5: hard resetting link
Jul  3 13:31:48 mitchsserver kernel: ata5: softreset failed (device not ready)
Jul  3 13:31:48 mitchsserver kernel: ata5: hard resetting link
Jul  3 13:31:48 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 3907026080 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x40000000 SErr 0x0 action 0x0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:48 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:31:48 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:48 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:31:48 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:31:48 mitchsserver kernel: Buffer I/O error on dev sdc, logical block 18, async page read
Jul  3 13:31:48 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:48 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:31:48 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:31:48 mitchsserver kernel: Buffer I/O error on dev sdc, logical block 18, async page read
Jul  3 13:31:48 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:48 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:31:48 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:31:48 mitchsserver kernel: Buffer I/O error on dev sdc, logical block 18, async page read
Jul  3 13:31:48 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:48 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:31:48 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:48 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:31:48 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:31:48 mitchsserver kernel: Buffer I/O error on dev sdc1, logical block 10, async page read
Jul  3 13:31:48 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:48 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:31:48 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:31:48 mitchsserver kernel: Buffer I/O error on dev sdc1, logical block 10, async page read
Jul  3 13:31:48 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x0
Jul  3 13:31:48 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:48 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:31:48 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:31:48 mitchsserver kernel: Buffer I/O error on dev sdc1, logical block 10, async page read
Jul  3 13:31:51 mitchsserver kernel: ata5.00: exception Emask 0x50 SAct 0x100000 SErr 0x30802 action 0xe frozen
Jul  3 13:31:51 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:31:51 mitchsserver kernel: ata5: hard resetting link
Jul  3 13:31:59 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 136 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0
Jul  3 13:32:02 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
Jul  3 13:32:02 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:02 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:02 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:32:02 mitchsserver kernel: Buffer I/O error on dev sdc, logical block 18, async page read
Jul  3 13:32:05 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x40000000 SErr 0x0 action 0x0
Jul  3 13:32:05 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:05 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:05 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:32:05 mitchsserver kernel: Buffer I/O error on dev sdc, logical block 18, async page read
Jul  3 13:32:08 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x0
Jul  3 13:32:08 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:08 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:08 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:32:08 mitchsserver kernel: Buffer I/O error on dev sdc, logical block 18, async page read
Jul  3 13:32:10 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x0
Jul  3 13:32:10 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:10 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:10 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Jul  3 13:32:13 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x80000000 SErr 0x0 action 0x0
Jul  3 13:32:13 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:13 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:13 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:32:13 mitchsserver kernel: Buffer I/O error on dev sdc1, logical block 10, async page read
Jul  3 13:32:16 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
Jul  3 13:32:16 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:16 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:16 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:32:16 mitchsserver kernel: Buffer I/O error on dev sdc1, logical block 10, async page read
Jul  3 13:32:19 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x800 SErr 0x0 action 0x0
Jul  3 13:32:19 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:19 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:19 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:32:19 mitchsserver kernel: Buffer I/O error on dev sdc1, logical block 10, async page read
Jul  3 13:32:22 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0
Jul  3 13:32:22 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:22 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:22 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x80700 phys_seg 12 prio class 0
Jul  3 13:32:25 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x0
Jul  3 13:32:25 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:25 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:25 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:32:25 mitchsserver kernel: Buffer I/O error on dev sdc, logical block 18, async page read
Jul  3 13:32:28 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0
Jul  3 13:32:28 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:28 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:28 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:32:28 mitchsserver kernel: Buffer I/O error on dev sdc, logical block 18, async page read
Jul  3 13:32:30 mitchsserver kernel: ata5.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0
Jul  3 13:32:30 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED
Jul  3 13:32:30 mitchsserver kernel: ata5.00: error: { UNC }
Jul  3 13:32:30 mitchsserver kernel: blk_update_request: I/O error, dev sdc, sector 144 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul  3 13:32:30 mitchsserver kernel: Buffer I/O error on dev sdc, logical block 18, async page read
Jul  3 13:32:30 mitchsserver mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor.  Please use the edac_mce_amd module instead.

 

Link to comment

on top of what i said above.. i dont understand  why  the cache drive i using   is also in the un assigned drives?  its part of the array    the one that says mount is the bad drive the ata5 issues

is that normal for the pool drives to show up in the unassigned devices section?

 

array.PNG

Link to comment
4 minutes ago, comet424 said:

so if you have say 5 disks and a parity  and btrfs  fs corrupts on disk2..   doesnt the parity fix that fs corruption? or does it corrupt everything.. reason i wondering if i should go to  xfs  instead of btrfs for all my arrays?

Parity does cannot fix file system corruption, however it is only that drive that is affected if it happens - the other drives are unaffected,

 

6 minutes ago, comet424 said:

i noticed  if you do 2 drives for a pool  you cant do xfs  it only allows btrfs

That is because Unraid utilise the built in btrfs specific version of RAID in such a case.   XFS has no equivalent functionality.

Link to comment

ah ok and how ofte does a whole btrfs go down... so then i should be safe then using btrfs  on my main server.. 76tb 7 data disks 1 party  set to btrfs..  as i mentioned i have set all my unraids to btrfs as what i read  btrfs  is more supperior ...

 

so if 1 drive btrfs fails on 2 cache drive  the fs  does the other one compensate?    which raid is it i remember reading 

 

if you have 2 disks mirrored or something   and if the 1 drive fails the 2nd one dies too.. and i dont think it was stripe

maybe its mirror?  when you write to disk one and it corrupts and it mirrors the corrupt to disk 2  making both drives fs go down

Edited by comet424
Link to comment
48 minutes ago, comet424 said:

tell ya  that a FS has corrupted  from the system logs?  i find the notifications doesnt seem to show  when FS corrupts on the sys logs are saying ata5  failure  be nice to know its happening   that i wouldnt keep writting to it

Often you can't write to a corrupted drive even if you want to because it isn't mounted for read or write (unmountable filesystem)

 

You can write to a disabled (emulated) drive.

Link to comment

oh ok  ya the drive was working or was currently  working.. but when i was using krusader to copy off the drive to the array..  krusader was spitting back there was an error didnt say .. and i have had errors ususally i fix it running new permissions  and that fixes things... cuz i was still able to download to the drive..   as i was able to move some files off the drive  some i couldnt... and when i went to reboot it.. thats when it was unmountable..  

 

but i also ment  since i was using the server.. and the server didnt spit out error sayin   download drive  has gone corrupt...  ud only ever know if you regullary check system logs  or when ur moving files... other then that ud never know and ud keep copying.... 

 

but i going to have my sister swap the drive  when she gets home this way ill know if the drive is failing or if its the slot  in the 4 hotswap bay

 

Link to comment

so something going wrong with her server.  the download drive went into read only...  the shares page  says no exportable shares... but the array shows one drive shows files

 

before i do a reboot.. i downloaed the diagnostics... i dont wanna reboot.. but does it say  the array is in trouble..

 

it has to be  either power supply or back plain of the board...   cuz it was just idling and stuff.. was re setting it up..

 

think its time to change case  and not use it till i fix it i think

 

so it has to be power supply or backplaine as it not hard drive.. if its affecting the other hard drive...  but maybe you understand the error codes better then me

so i know what i need to do

 

unraid.PNG

mitchsserver-diagnostics-20220703-1620.zip

Link to comment

Looks like your download_drive was sdc when array started but disconnected and reconnected as sde, so it isn't assigned.

 

It also has 22 pending sectors. You should see SMART warnings for that disk on the Dashboard page, and you should have gotten notifications for it.

 

You should replace the drive, doesn't look like it has much if anything on it.

Link to comment

ya i just made the drive today   i couldnt fix the old drive and my sister wasnt around to unplug it.. so  in the 4 bay server there was a empty 2TB drive  i  added the drive  i switched drives as the download_Drive   and i also rebooted...  it was downloading i did some testing was working...    then  i checked a couple hours later or so  and thats when it i checked logs  saying read only   and the shares showing   no shares    which it should be be there

 

and the showing in unassigned devices.. happens right after reboot...

 

SMART isnt working  its showing blank info when i either click    "sde"  or "download_drive"  so ill give the computer another rebooted

 

 

so if it was sdc  at bootup and array starting    then disconnected and reconnected  would that be a backplain  or power issue?  or could be both.... going to reboot it.. 

 

starts off with 1 issue  then 2nd hard drive having this issue..   just waiting for the 3rd thing to go lol

 

 

 

Link to comment

shares are back after a reboot..

the download_drive   does say 31 sector count

smart  shows

197Current pending sector0x0032200200000Old ageAlwaysNever30

 

and says overall health Smart Passed

 

but i going to try to get her some new hard drives...

probably needs a new case or power supply.. and now cases harder to come by  4 bay

 

 

Edited by comet424
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.