Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unformatted Disk after removing a disk

Featured Replies

Hello, my problem started after I removed disk 10 which had no data on it and needed for something else

 

Running 4.7

Parity was check with no errors yesterday

 

I first stopped the array

removed disk10 from the array on device setting page

ran initconfig

 

then rebooted and that's when disk4 show unformatted

 

I tried check file system on unmenu  but says no file system on disk

 

not sure what to do next

 

Thank You

Mike

syslog.zip

  • Author

Just a followup, I ran "reiserfsck --check /dev/sdi" and says

 

superblock  is corrupted and you need to run this utility with

--rebuild-sb.

 

Should I?

Just a followup, I ran "reiserfsck --check /dev/sdi" and says

 

superblock  is corrupted and you need to run this utility with

--rebuild-sb.

 

Should I?

NO.  The file system is on the first partition, not on /dev/sdi

 

If you do anything you would need to run

reiserfsck --check /dev/sdi1

 

(note the trailing "1" indicating you want to run it on the device representing the first partition)

Just a followup, I ran "reiserfsck --check /dev/sdi" and says

 

superblock  is corrupted and you need to run this utility with

--rebuild-sb.

 

Should I?

NO.   The file system is on the first partition, not on /dev/sdi

 

If you do anything you would need to run

reiserfsck --check /dev/sdi1

 

(note the trailing "1" indicating you want to run it on the device representing the first partition)

 

You really want to run the check on

/dev/md4

since doing it that way would fix parity as any corruption is fixed.    If you run the file system check on /dev/sdi1 you'll need to force a parity check to get parity in sync with the fixes.

 

Joe L.

The disk seems to be identified but the mount attempt fails due to the filesystem not being there.

 

You have to use a 1 after the disk identifier, ie sdi1. Make certain you get this right because trying to rebuild sdi will likely destroy your data permanently.

 

Read here, you would just use sdi1 instead of md1.

 

http://www.lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

Peter

Just a followup, I ran "reiserfsck --check /dev/sdi" and says

 

superblock  is corrupted and you need to run this utility with

--rebuild-sb.

 

Should I?

NO.   The file system is on the first partition, not on /dev/sdi

 

If you do anything you would need to run

reiserfsck --check /dev/sdi1

 

(note the trailing "1" indicating you want to run it on the device representing the first partition)

 

You really want to run the check on

/dev/md4

since doing it that way would fix parity as any corruption is fixed.    If you run the file system check on /dev/sdi1 you'll need to force a parity check to get parity in sync with the fixes.

 

Joe L.

 

He just removed a disk and ran initconfig so there is no parity to destroy right now.

 

Peter

 

  • Author

Thank you for the replys

 

when i run reiserfsck --fix-fixable /dev/md4

i get "Failed to open the device '/dev/md4': No such file or directory"

 

That is why i used sdi

 

 

 

Thank you for the replys

 

when i run reiserfsck --fix-fixable /dev/md4

i get "Failed to open the device '/dev/md4': No such file or directory"

 

That is why i used sdi

 

 

 

Well, you need to use /dev/sdi1

The array needs to be started to use md4.

 

Peter

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.